Xbox 360 LAN/System Link problems

Man of Honour
Man of Honour
Joined
18 Oct 2002
Posts
12,264
Location
Cotswolds
Trying to get two 360s up and running on my home LAN, whenever I start a session on one xbox I can see it on the the other, but when I try to join it I get an error and can't connect. I've tried this with several games and the result is always the same.

I've tried various settings in the router but nothing seems to work.

Any suggestions?
 
NAT is moderate on both consoles, but as above, NAT doesn't come into it when connecting consoles over a LAN.

It's frustrating :(
 
You got access to the router admin interface to check both of the 360s are showing up?

Have 3 360s and never had to do anything other than turn them on and select system link for them to find each other so sounds very odd.
 
Are they static IP's or DHCp assigned from the router?
What's the error message you get and what game is this message from?
How are these xbox's being connected up? They hooked up with a cross over, or both through a router, or what?

More details please Drex! :D
 
The error message varies from game to game, but they are all along the lines of 'can't connect to session'. Same story on every game, I can see the sessions, but get on error on trying to connect.

Both 360s show up on the router's admin page, they are assigned IPs by DHCP, but they are given the same IP each time because I have set them static leases (DDWRT firmware on Linksys router).

They are connected like this:

1st 360 (downstairs) is connected directly to the router via RJ45 cable.

Second 360 (upstairs) is connected to a switch, which in turn is connected to a WiFi bridge which wirelessly connects to the router. Bypassing the switch and connecting the second 360 directly to the WiFi bridge doesn't help.
 
Last edited:
Weird, they can both see each other, so that rules out most network problems. I don't like however, that they are on the same IP. Have you tried setting an IP address to each xbox manually. E.g. one with 192.168.0.2 and the other 192.168.0.3. Just make sure they are on the same subnet. It's worth setting the NAT to open as well on both (although yes not strictly controlled via LAN, once on live they are.)

You're not using the same account on both xboxes are you, or something daft like that? Example: DreXeL tag on both upstairs and downstairs xbox, over Xbox Live? Obviously, you don't need to do this locally, just over live! :)

Can both xboxes get on xbox live independently? Are all the games patched both ends? What does the network connectivty / system link tests show?
 
Last edited:
When I said same IP, I don't mean they share the same IP, mean I have set the router to give them the same IP via DHCP each time, one gets 192.168.1.104 and the other one gets 192.168.1.108.

Different accounts on each xbox, games are patched to latest updates, both can access live and pass all network tests.
 
You said you have one going through a wireless bridge.

Your problem could very well lie there. Check all the settings on the wifi bridge and make sure something in that is not blocking something
 
It's just a basic WiFi bridge, there aren't really many things to setup, it doesn't have a firewall or anything.
 
Set static IPs from within the consoles?

I think you will have to do this, set static IP's to both the xbox's, and make sure that you can access Live from each machine.

In theory you shouldn't need any setup though, it's weird:

Internet connection - router - xbox 1, 2, 3, 4. Should all work without any setup.
 
Tried setting static IPs to both consoles from within the dash, both consoles pass all network tests and can access live, but still can't connect to each other's local system link games :(

I guess it's just not going to work through the WiFi bridge for some reason. I can do it through live, but obviously this will mean two gold accounts :rolleyes: :(
 
Last edited:
Easy way to test that Drex, is to hook both up with a system link cable, have you got one lying around you can test. That way, it rules out the bridge and the router. Then try it with the router and rule out that and carry on from there.
 
Back
Top Bottom