Cable/Linksys can't join

[Schpekrazer]

I get a "connection failed" message on 9 out of 10 attempts. The one time I managed to connect last night, it was a server that required me to d/l the map, which took about 45 seconds (the connection is that good). The point is, it DID connect. I see all the servers and get pings as low as 55-90

I've got a cable modem and the 4-port Linksys router. Every other game I've tried to play online connects fine.

The two machines have thier own manually assigned, private IP address, so DHCP is disabled. I've got my machine on the DMZ, so all ports should be clear, and I gradually backed-off my BlackIce firewall protection levels until it was disabled.

One thing I don't understand is that most games require you to take some action to tell the program that the IP address of the machine it is installed on is NOT the one that the internet sees. UT doesn't seem to have an option or an .ini entry to do this.

Thanks.

 

[Fear the Beard]

Uprade the firmware on the router and check with your isp to see if they have any special settings to use for your router.

 

[Schpekrazer]

My firmware is the latest official release. Last night, I loaded the current beta firmware & it didn't solve the problem; I'll try some older versions.

That's the first time I've ever heard about talking to the ISP - I'll give them a call. What areas of the router settings do ISPs make suggestions on?

Thanks, FtB

 

[Schpekrazer]

ISP said they don't block ports and there is nothing special to be done with the router.

I looked at the UT log file, and it shows ping timeouts for every hop as it tries to connect to the server.

I can run a TRACERT to any of these IPs at the command prompt and get pings to them.

 

[Schpekrazer]

I took the router of the loop, changed the PCs TCP/IP settings, and connected to the multiplayer screen as before. I still could not connect, so it's not the router thats causing the problem.

Is there a way for me to verify that the ISP is not blocking ports? On dslreports.com, another RCN subscriber reported the same problem; I haven't communicated with him yet, but it seems strange that the two of us have this problem AND the provider in common.