Unable to make TCP connections, uploads timeout

[the__extreme939]

This is the first time I haven't been able to solve my TCP connection issues, so I just don't know where to go next.

Issue:
Clearly, I can't make any TCP connections.  Or at least WinMX won't recognize that I can make any.  
I can make a primary connection to the network, connect to other primaries & have searches routed through me, but no secondaries can connect to me.
Uploads won't connect - they just time out waiting for "incoming connection"
Download connection is erratic, but will operate. (Could just be the lower usage since the "shut down")

System:
WinXP/SP1
Windows Firewall Disabled (no other firewall installed)
Bell Sympatico DSL w/ Speedstream 4200 modem (Bell firmware - bridged by default)
No router (want to solve this issue before I add the router to the mix)
WinMX 3.54b (patch operational)

Other items:
Tried connecting through dial-up account - downloads & uploads would connect, but WinMX still wouldn't acknowledge TCP connections.
Used Azureus's NAT test to test all ports I've tried to use in WinMX, and all came back as functional/operational.
Other apps (ie Azureus) have no issues connecting using TCP protocol.

Any advice would be greatly appreciated.  Can't wait to start sharing files again.  My queue gets pretty long.

Note - Windows firewall has been verified as deactivated several times.  I activated it just to check, and no other apps could connect to their servers.  Deactivated it again, and all apps returned to normal operation.

[Bearded Blunder]

You don't mention AV software, but if you're using Norton 2005 or later, check WinMX is set to allow in internet worm protection.

Also check your modem documentation, many have routing capabilities, & require that you set port forwarding, even though they appear to be a modem for a single connection.

Once this is eliminated, try non standard ports, ISPs are increasingly blocking or filtering the default ones (sorry I don't have a list of culprits), personally I quite like 1547 and 5631, I think it would be a brave ISP that decided to block Laplink or PC Anywhere, yet few people have them.... (this assumes YOU don't use either of these).

Once everything else is eliminated, last resort is to set WinMX as unable to recieve in port settings & restrict yourself to a secondary connection, this will reduce your potential to share files to 3000 files instead of 5000, but as a last resort works & in some situations is the only answer.

[the__extreme939]

There is no AV software running either.

As for the modem, my ISP had their firmware installed which doesn't allow me to do anything other than reboot the modem or change my username/password.  Fortunately, the firmware also sets the modem into bridged mode, which allows all traffic to pass through.  I wish I could get some general firmware, but haven't been able to locate any as of yet.  (Siemens SpeedStream 4200 anyone???)

WinMX won't acknowledge TCP connections on any port I choose, even non-standard ports, where as other applications have no problems using just about any port I choose.

Even running as a secondary, I still cannot get any upload to connect.

Thanks for the reply Bearded Blunder.

[Bearded Blunder]

Well the documentation on how to use it, set firewall rules, port forwarding & configure for hoime networking is located here: http://kb.efficient.com/utility/getfile.asp?rid=5226

If your ISP has indeed locked you out, ie, you can't access thge settings at all as outlined in that document, you'll probably have to go to the port settings & set winmx as "Unable to receive" on TCP & possibly UDP also, it will then work as a secondary connection (or should) with NO port in use to listen on. (firewalled mode) you should then be able to upload or download normally as long as you don't encounter another user configured the same way, (in which case things turn red with a "both users firewalled" message).

[nylly444]

Found some discussion about the SpeedStream 4200 here, maybe it helps you?
http://www.dslreports.com/forum/remark,12998125

[the__extreme939]

You guys probably won't believe this, I cand even figure it out myself, but I actually solved my problem by connecting the modem through my router.  Yeah, figure that one out...for once a router actually solved a problem.  I think it may have had something to do with the PPPoE config settings, but why it will work with the router & not with the modem on its own is confusing to say the least.  

Thanks again to everyone who posted advice.

I'm back up & running as a primary, with uploads firing on all cylinders.  WinMX for Life.