• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

UT LAN problem - solved

R

rcraig

Senior member
This weekend I tried to play UT over my home network, but all I got from my second computer was "Connection failed" when it tried to connect to the first in UT. The second computer can see the first listed as a server in UT, but it just won't connect. I was running Microsoft Internet Connection Sharing, and thought maybe that was the problem, so I unintstalled that and set a static IP on both computers, but the same happened. This was my network setup after removing ICS:

Computer #1:
Client for Microsoft Networks
Network card
TCP/IP with IP 192.168.0.1, 255.255.255.0 subnet, WINS disabled, no gateway, DNS disabled.

Computer #2:
Client for Microsoft Networks
Network card
TCP/IP with IP 192.168.0.2, 255.255.255.0 subnet, WINS disabled, no gateway, DNS disabled.

Tried adding IPX/SPX, but no joy.
Looked online but couldn't find anything that helped.
The computers can connect just fine through Network Neighborhood. I also had some of the same problems getting CS to network. Sometimes it would take several tries before the second computer, which could see the first listed in CS, would connect. Eventually it would work and once the connection was made, CS would run fine.

Anyone see something I missed?

Thanks,
RCraig
 
1. Check your cabling. Use a storebought patch cable if possible. Bad cables can cause all sorts of strange and intermittent network problems.

2. Since your PC's see each other in network neighborhood, we'll assume that the hub works and your NIC's are working and the drivers installed correctly.

3. It bugs me that you are using 102.x.x.x for your IP's. Use 192.168.1.1 255.255.255.0, 192.168.1.2 255.255.255.0 just to keep it technically valid (private IP space and away from the zero-subnet). The zero-subnet works with MS and most other vendors, but is actually reserved in the original TCP/IP spec.

4. Go to each PC and have it ping the other one. Post results.
 
The 102.x.x.x was a typo. I am using 192.x.x.x. I'm at work now, but will post the ping when I get home. All other network functions work perfectly. This is a Linksys 10/100 switch with Linksys 10/100 nics and cables. It was one of those network-in-a-box kits.

Normally I use 192.168.1.1 and up but the ICS used 192.168.0.1 so I changed the second IP from "obtain an ip automatically" to 192.168.0.2 when I removed the ICS from the first computer. I'll try changing the third number to 1.
 
Are you running Windows 2000 or another OS that can be restrictive on permissions? I had the same problem when I was running UT on a LAN with the Server running Win2K Pro - I ended up having to add users for all my buddies and put them in groups with access to the Machine and the UT folders themselves.
 
I could see having to add the users for file sharing, but not connecting to a tcp/ip service like UT or FTP or stuff like that. Anyways, the 192.168.1.x addresses are just for the ping test. I would seriously recommend un-sharing and re-sharing and let MS do its thing.
 
When in UT, I tell the second computer to ping the first and it has a ping rating of the low 40's.

I found out my problem, though. I had installed the patch on the first computer, but not the second. Once I installed the patch, the second computer connected and I had both computers playing UT.

Unfortunately, I wanted to play this last weekend when a friend was in town. Now I don't know how long until another comes to visit. Until then I guess it's just me and the bots.

Thanks for you help and suggestions.

RCraig
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top