WinMX isn't working correct

[PilotinCommand]

Hi,

I was always a fan of WinMX untill the 3.* versions. At the moment I have WinMX version 3.22 installed. Every time I'm getting VXD messages after 5 minutes or so, or sometimes my system reboots suddenly. I don't know what the problem is. I have my virus scanner up to date and I'm 98% sure I have no virus.
I'm using the program on a PII 350 MHz 128 MB RAM connected via a cable modem (SMC network card). I use Windows Me and Norton Internet Security 2001 btw.

Can somebody help me with this problem? I really don't have a clue.

PiC

[smokealotapotimus]

I have alot of stability issues with WinMX myself.

If you have Zone Alarm running in the backround, try disabling it. Zone Alarm and WinMX don't play very well I have noticed, on my system anyways. That helped the the major slowdowns I was having, though not entirely.

About your VXD error, I would try disabling Zone Alarm also, though probably won't fix it. I have yet to figure out why WinMX gives me a fatal error when using OpenNAP servers.

[PilotinCommand]

I don't have zonealarm installed, I have Norton 2001. Maybe it's a common conflict between the two programs, I don't know. I only know that it's not working the way it should.
By the way; disabling norton doesn't work either. Next to that I don't want to risk virusses and hackers hacking my system or something.

PiC

[Kubie]

PilotinCommand,
I run Winmx with ZA and Trend A/V with no problems. The version I use is Winmx 2.? as I tried the 3.2 version and had the problems you are.
When I was looking for a song to d/l, I would set ZA to allow Winmx access to the net and when I'm done, I set it back to disallow.
Carl

[PilotinCommand]

I do something similar with Norton but no effect. So what version do you use?

PiC

[DilLy]

Kubie:
Can't you just set it to ask? Either way works I guess.

Anyway, I know with WinMX and Firewalls of any brand you need to set up your UDP and TCP ports correctly for the program to perform optimally through it. I am using ZAPro (latest version) and WinMX 3.22 (or whatever the latest version is). Since day one I have had no problems. The interface for WinMX needs a little cleaning up though, as it is a little cluttered and confusing at first.

[PilotinCommand]

Maybe I should take a look at those tings, those UDP and TCP ports. However I'm not really familiar with UDP and TCP settings. Can you provide me wih some information or a link to a usefull source?

PiC

[Trinity]

Ever since moving to WINMX I've had trouble dl songs - always seems that none of the connections hit. didn't happen with M or Klite. i'm behind a firewall (network router) at home - does this have something to do with it?

[DilLy]

Okay first go into your WinMX settings, click the plus sign next to "Internet Connection". You should see four lines underneath it now. One for Outgoing TCP, one for Incoming TCP, one for In/Out UDP, and one more for Host Name Resolution.

click on Incoming TCP, and set your port number. Click on the first radio button and put the number in the field. For now just use 6699, this is what I am using. You may need to change it though. It needs to be within a certain number range but I forget what that range is, but it is a huge range. Stay between 6000 and 10,000 and I think you will be alright. Read the explanations between the two choices on that page, so you know the difference. I don't know your computer so I don't know for sure which one you should pick, but I am pretty sure you should pick the first radio button (as long as you are on a Broadband connection with a firewall).

Next, click on In/Out UDP packets in the menu on the left. Mine already had a number inside the field for the FIRST radio button when I first installed WinMX, and that is the number that I used. That number is 6257.

That is all you nee to do for incoming TCP and In/Out UDP in WinMX. Now you must go into your firewall and set the exact same numbers in the exact same categories and make sure they are set to be active when using WinMX. So go to your Firewall settings, and set incoming TCP to the same number as in WinMX, and also set your firewall's In and Out to the same number you used in WinMX. Make sure they are set to be open ports.

Fire up WinMX, see if that helps.

If it doesn't work right still, then there are different setting in WinMX you need to choose and make sure your firewall is also cnifgured properly again. make sure WinMX has full access permission too. You shouldn't need to let it act as a server though.

Just read all the different settings explanations in WinMX to find out what they do. Then tell us the outcome you have, I am really interested if you get it working or not.

Make sure to tell us the type of connection you are using and also the version of WinMX and what Firewall you have.

PEACE

[DilLy]

Trinity: A router might have everything to do with it.

[Cheryl]

I use a router, WINMX 3.22 & haven't had problems d/ling or sharing...

I make a secondary connection in networks, & I changed my incoming TCP connections to "unable to accept".

Cheryl

[DilLy]

yeah, I used to use that "unable to accept incomeing TCP" as well. But I noticed slow searches and downloads. So I set up my ports and, Wha-lah! I get super fast connections and tons of search results.

I guess it depends on your connection type and how you wish to connect through WinMX.

[Cheryl]

DilLy

I get mixed results on searches & d/loads...sometimes real fast other times real sloooow (I have cable). Is it consistently faster? Maybe I'll try playing with the settings for the tcp thing.

Thanks.

Cheryl

[PilotinCommand]

I'm not able to work with it now cause I'm kind of busy but when I have time in the weekend I'll see what I can do.
I'll try to let you know what happened.

PiC