Announces 6346, but really listens on 6347?

[rlively]

I'm running LimeWire on Windows 98 SE behind a Linksys router and using ZoneAlarm Personal Firewall.

ZoneAlarm was blocking many requests coming in on port 6346 even though I told ZoneAlarm to allow javaw.exe to act as a server and forwarded port 6346 to my machine. When I investigated, ZoneAlarm reported that javaw.exe was listening on port 6347, NOT 6346. I looked in the LimeWire settings, and on the Connections tab the port was 6346 and under Tools | Options | Port 6346 was also specified.

When I changed the Port number to 6347 and forwarded that same port through my router all was well and users could start downloading from me. How did this happen and why was it really listening on 6347 instead of the stated 6346?

[dezine]

I have the same problem here, using Zone Alarm and all. So, I disabled Zone Alarm and changed everything to 6347. Did you also change the "Auto Connect Hosts" to be 6347 instead of 6346? I did but I am still not connecting for some reason. The program worked wonderfully as version 1.6d and now I am very frustrated.

I've changed all my settings back to 6346, changed my router to forward only port 6346, restarted everything and now LimeWire is listening on 6346 and everything is peachy. People can even connect to me from behind the LinkSys as long as I specify my IP # and port under Advanced | Firewalls.

I suspect this port-listening discrepancy is responsible for many of the problems. I have the problem where I can only establish Outgoing connections, not Incoming. Bearshare works fine using the same Forced IP and Port 6346.