Author Topic: Waiting For Incoming Connection (Read 5334 times)

TDog44137 · « **on:** February 08, 2007, 01:50:02 am »

Since a big part of the fun is giving things to other folks....

In a nut shell: I'm using XP Service pack 2. WinMX 3.54 Beta. A Linksys WRT 54GC Router. Windows Firewall is off. Zone Alarm 6.5.737 Suite is on. I am configured for TCP 6699 and UDP 6257. I have also set up a static ip address courtesy of the Port Forward help page (excellent resource, btw!) Still I'm unable to upload.

Previously, before the Zone Alarm install I had no problems with uploads. Obviously, I'm missing something...anyone have any ideas? With a couple thousand files I'm bummed every time I see countless requests being rejected...so, in a word.....HELP! Thanks in advance...T.

reef · « **Reply #1 on:** February 08, 2007, 03:28:17 am »

Try Shutting WinMX down.... open ZoneAlarm firewall..... and remove
the winmx application rule.... close ZoneAlarm and restart WinMX....
when ZoneAlarm asks you if you want WinMX to access the internet
click yes.... if asked if winmx is attempting to act as a server,also
click yes

Tdog525 · « **Reply #2 on:** February 08, 2007, 07:01:27 pm »

Thanks for the idea but that didn't do it.

KM · « **Reply #3 on:** February 08, 2007, 07:46:48 pm »

try it without zonealarm enabled, that will confirm if it's a zonealarm configuration issue or elsewhere

Tdog525 · « **Reply #4 on:** February 08, 2007, 08:35:15 pm »

My, my...when I miss an obvious trouble shoot like that I should slap myself....and hard. Thank you.
So....Zone Alarm now off, problem still there...any insights?

Me Here · « **Reply #5 on:** February 08, 2007, 09:00:52 pm »

Tdog do you happen to have any antispam or email protections installed and running? We have see alot of these cause issues with ports and traffic.

As of now your 6699 and 6257 ports are showing blocked. I might suggest you go back through the Router configs since the ZA doesnt seem to be the cause. Sometimes even changing ports to something like 16699 or 16257 and try those.

You can test those ports as I have here:

http://winmx.dnsalias.com:801/scan.py

Let us know how this goes please

Tdog525 · « **Reply #6 on:** February 08, 2007, 11:28:18 pm »

Tried alternate ports and still no go on the TCP although the UDP is open. Stupid question but what am I looking for in the router configs?

Me Here · « **Reply #7 on:** February 09, 2007, 12:45:14 am »

What Id like you to do is this:

First make sure your Staic IP is still ok and its the one being used on the router, by doing the
Start > Run > type cmd then OK
Then type ipconfig and hit Enter key.

Now you have the IP address listed

Go Back into the router config pages to the Applications & Gaming > Port Range Forwarding

There you should have two rules that look like this:

Service: WinMX1 Start ~ End Port: 6699 - 6699 Protocol: TCP To IP Address: 192.168.1.xxx (use your IP Address listed on the above DOS Box, a common mistake is to use your Gateway IP (192.168.1.1) and that will not work here.) Tick Enabled

Service: WinMX2 Start ~ End Port: 6257 - 6257 Protocol: UDP To IP Address: Same as above Tick Enabled.

Just double check those for me and post back if you could.

Tdog525 · « **Reply #8 on:** February 09, 2007, 01:45:30 am »

OK....I'm the AxxHole. I really do know better but somewhere in my frustration "192.168.1.1" looked real good to me. Amazing how well it all works when you do it right!

Thanks a million for all your help on this and my apologies to the long list of folks who tried to download over the last few days...but, at least, the shops open now!

Your professionalism and courtesy were much appreciated and certainly a big part of what make this such a great community.

All the Best....Tdog.

Me Here · « **Reply #9 on:** February 09, 2007, 05:23:50 am »

Yay... and Thanks

You wouldn't believe how common that is Tdog and luckily quite easy to fix for all those folks linning up for your files..

Happy WinMXing

Lagerlout666 · « **Reply #10 on:** February 09, 2007, 09:39:04 pm »

Quote

Your professionalism and courtesy were much appreciated and certainly a big part of what make this such a great community.

that should be put as a quote on the front page or sumit, always nice to be appreciated and good bit of advertising.

Tdog525 · « **Reply #11 on:** February 10, 2007, 12:31:18 am »

Yeah well, as a broadcast producer I know the "niceties" so lemme make it clear....if you'd like to use it, go ahead. It's yours for free and in perpetuity. Tom Ciula

Lagerlout666 · « **Reply #12 on:** February 10, 2007, 12:33:28 am »

Thank-you Tom i shall put it to the powers that be glad your a happy user; happy winmxing and dont forget to tell everyone you know

paul99 · « **Reply #13 on:** February 13, 2007, 08:45:18 pm »

I have read this thread with great care, because I am having problems very similar to the one described here. I cannot make a connection at all. I have WinMx 3.54 beta, which I just downloaded from the site given on your tutorials page.
I disabled Zone Alarm, so it's not that. I disabled Avast, and it's not that. I did use the guidance on portforward to set the ports in my router.
I checked the IP of the laptop I am using and it is 192.168.2.3 , in the router(which is itself 192.168.2.1) Virtual Server settings I set 192.168.2.3 TCP LAN 6699 and Public 6699 to Enable, which has saved correctly. And I similarly set UDP 6257 . Attached screen shot shows the router setting.
But when I do the port scan you recommended at winmx.dnsalias.com:801/scan.py it is telling me that TCP 6699 is closed, and UDP 6257 is open. So that's why I can't get WinMx to connect. I can't understand why 6699 is showing closed when I have definitely got it open. I do not use the router's own firewall by the way, it is disabled. Any suggestions would be most gratefully received.
Mike

Me Here · « **Reply #14 on:** February 14, 2007, 03:02:43 am »

Mike do me a favor and instead of disabling the Zone Alarm turn it on.. but first.. remove WinMX from the allowed applications and restart your WinMX.. then when Zone Alarm asks about re allowing it say yes.. please if it asks also about allowing WinMX to act as a server tell it yes for this as well.

Now if your using XP please go to your control panel > firewall icon and be sure this is disabled. Often XP likes to re enable itself.

If this still doesnt work can you be more specific with what you mean by 'connecting' is the Networks page just flashing yellow at you or are your transfers not connecting ? Makes a bit of difference in trouble shooting the problem..

Thanks for the great info so far by the way your router settings look fine.

paul99 · « **Reply #15 on:** February 14, 2007, 08:28:14 am »

Hi there - yes, it was Zone Alarm causing the problem. Very curious that Zone Alarm was showing WinMx beta as allowed to be a server already before I changed it, so I assumed it was telling the truth! I did exactly what you advised, removed both WinMx entries (3.31 was still there) , then ran WinMx. ZA did the asking, which I allowed, and all works fine now, port 6699 is showing open and WinMx connects and works (btw, when I used "connecting" in my original post I did indeed mean that the network page ws just showing the flashing yellow button).
How on earth did you know this - wide experience of the quirks of software, I expect. I am most grateful for your time and excellent advice.

Me Here · « **Reply #16 on:** February 14, 2007, 08:32:59 am »

Glad to hear its working for you..

It was indeed experience.. Often when folks change WinMX versions or perhaps even upgrade patches the Firewalls see this as a program Hijacking even though you are simply upgrading .. so for your own protection they block it.. removing it and readding it lets the firewall know it is an ok program that you're aware has changed.

If ya need anything else dont hesitate to look us up..

paul99 · « **Reply #17 on:** February 14, 2007, 08:39:45 am »

Thanks ! I have to say, ZA usually works a little more subtly than this, in that it will throw up a message notifying me that a program has changed/been updated and now wants to access the internet again - it even does this with Avast Anti-v -- when the actual program occasionally updates itself, ZA asks if the new version can access the internet to update the virus database. But it failed here miserably with WinMx. Now I have gained a little of your wisdom I shall watch it like a hawk in future in case I find odd problems with other programs being denied access.

paul99 · « **Reply #18 on:** February 15, 2007, 11:38:47 am »

Just a quick question about downloads - A search I made recently produced a lot of files with odd additional characters in the file names . Only one or two were a straightforward file name. I have attached a partial screen shot. Is there an explanation for this? Should I be suspicious of them? I didn't download anything on this occasion.

Max™ · « **Reply #19 on:** February 15, 2007, 01:30:43 pm »

Hi Paul,
in most cases when you see boxes and strange characters, its normally in Japanese, to be able to see it you would need the japanese language files installed in your WinMX, but is there a point in downloading something you cant understand?
in case you do want them you can find language files Please Click Here For Them

Author Topic: Waiting For Incoming Connection (Read 5334 times)

TDog44137

Tdog525

KM

Tdog525

Tdog525

Tdog525

Tdog525