Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Shawsy4]

I have two Xbox 360 consoles connected to the DGL-4500 by XBox Wireless "N" connections.  I have followed the Gamefuel Setup instructions according to the "Sticky" on this forum.  I can play on both consoles at the same time with Open NAT which is why I purchased the router in the first place.  So, I must have done most things right.  Each of the consoles has a reserved IP address (set on the router and the console) and a Gamefuel rule associated with it.

The only strange thing is that every time I start up either XBox, it displays a message that it cannot connect to XBox Live.  On that same message screen there is an option to test the XBox Live connection.  Invariably, the test passes, and the XBox indicates that XBox Live is "Up and Running".  With that step performed, I can connect to XBox Live as normal, and play away.  I have now gotten into the habit of booting up the Xbox console, and skipping right to the network connection test screen before even attempting to log in with an XBox Live profile.  It's an extra step that I would rather not have to perform each time.

Is there a setting that I might have missed in the setup of the router? 

The only settings that differ at all from the Sticky note as far as I can tell are the "WISH" sessions, which I left enabled because the consoles are connected wirelessly.  I also left WiFi protected setup enabled because I have a Blackberry device that uses this type of connection.

Any thoughts?
Thanks

[FurryNutz]

Review the Gaming and Gamefuel Sticky. It works well for me and others.

[Trikein]

What happens if your power up the Xbox with the router off then turn it on after. I have a feeling you can go online without the test. I think its the boot up process of the 360. WPS shouldnt effect it, and Wish shouldnt cause the symtom your explaining. I have a few ideas if my theory proofs true.

[Shawsy4]

Review the Gaming and Gamefuel Sticky. It works well for me and others.

The Sticky Note was vital in my initial setup, and I thank you for the reference document.  As noted, the setting seem to work with only one strange exception.  Some more tinkering on my part is probably required.
The gaming section does not apply, since I have multiple consoles and cannot forward the same ports to two different ip addresses on my network.
I have followed the gamefuel rules with the two exceptions noted and for the reasons noted.  i stand corrected, I also had a mixed 802.1N/G/B setting which I will change to N/G only since I have both types of devices on the network.
I will post from time to time in case there are others with a similar issue.  Maybe I will hit on the right combination for this setup.
Thanks.
Shawsy

[Shawsy4]

What happens if your power up the Xbox with the router off then turn it on after. I have a feeling you can go online without the test. I think its the boot up process of the 360. WPS shouldnt effect it, and Wish shouldnt cause the symtom your explaining. I have a few ideas if my theory proofs true.

I might give that a whirl just to see what happens, but it would be a tough one in practice.  The network supports devices other than the gaming consoles, and turning off the router before booting a gaming console doesn't seem practical.  No better than performing the test step in practice, but might be useful for diagnostics.

[FurryNutz]

Yes, Gaming does not apply, at least from my experience. However I have 2 consoles and both work great using whats outlined in the Sticky and that taken from my buddy in OK who has 3 consoles, one wireless G only and the other 2 on wired using the Gamefuel rules.

[Trikein]

Oh yea, I didnt mean as a practice. But what I suspect is the process the 360 and router communicates on boot. Another easier test may be disabling the DHCP RESERVATION on that 360 and see if you can reboot the 360 without the issue. Also, are you using DHCP or a Static IP on your 360?

[FurryNutz]

It's all in the sticky. 

[Trikein]

But where not here just to fix problems. If that was the case I would want Dlink to pay me (and a certian someone that has like a billion posts) This is a forum. I see it as a place for discussion as much as solutions. If you just refer everyone to the sticky(And as relevent as most everything in there is) its just no fun. :-p Hehe

[FurryNutz]

ok. 

[philwoz98]

 I had the same problem with the wireless n xbox adapter. If you know your settings such as your ip address and what not, of the 360,  just switch it from automatic to manual in the 360 settings. Just make sure you fill in the spaces correctly. Worked for me.

[Shawsy4]

I had the same problem with the wireless n xbox adapter. If you know your settings such as your ip address and what not, of the 360,  just switch it from automatic to manual in the 360 settings. Just make sure you fill in the spaces correctly. Worked for me.

I explained the problem to one of the systems guys at work and he said it sounded like a DNS problem.  I looked through some XBox Live support forum posts, and hit on the following.  On each of the XBox consoles, I changed the DNS settings from automatic to manual, and entered the appropriate primary and secondary DNS for my ISP.  So far so good.  No need to test the XBox Live connection before signing into an XBL profile.

The other routers I have used (DLink 605 wired, Linksys WRT54G wireless G and Linksys WRT160N wireless N)  have worked without issue using "Automatic" settings for the DNS.  (The WRT160N doesn't support two consoles with Open NAT though!) I'm not sure how the DGL 4500 passes the DNS settings to the console (I do have DNS Relay enabled) but specifying the DNS at the console level seems to work for me.  Maybe this will help someone else out too.

[Trikein]

Hmm..DNS? Ahh..ok..yea, the router uses DNS relay with a high latency. You should make sure to turn that off along with advanced DNS and fill in the DNS info into the router itself. That should work as well. Good catch