Print

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

[FurryNutz]

Just ask...tell them that you've already done troubleshooting and need to speak with a higher level support person.

[FurryNutz]

So have an interesting question/problem for those interested:
Setup:
DIR-655, 657 and possibly 857.
2.4Ghz only. 5Ghz doesn't reproduce this.
Reserved IP address for 1st gen 360.
MS Wireless 2.4/5Ghz USB adapter. Connected in front. Haven't tired back yet.
QoS rules set up as per XBL sticky.
NAT EndPoint.
Single Mode N Only.
WPA2 and AES Only.
Channel 11 (Manual)
Auto 20/40Mhz

Reserved IP address:
Wired = Works
Wireless 2.4Ghz = Sees the SSID name and allows me to enter PW. Fails to connect and acquire the IP address. Times out and gets a self assigned IP address of 169.
Wireless 5ghz to my DGL-4500 in 5Ghz AP mode = Works and gets a IP address from the router and connects successfully to the XBL services.

DHCP IP address:
Wired = Works.
Wireless 2.4Ghz = Works and gets a IP address from the router and connects successfully to the XBL services.

I also tested with a 3rd party 2.4Ghz AP set in bridge mode and it's LAN wire connected to the LAN port on the 360 and same thing happens if I use the Reserved IP address. If I change to DHCP, it works.  

Is there a conflict some where or is this a configuration issue? I notice that one one occasions the MS adapter seem to connect as I was watching the Wireless status window on the router and there was a reserved IP address seen, however no IP address appeared on the xbox network settings. Most other times the connections were seen on the Wireless status window however the IP address was 0.0.0.0. Connected speeds were around 130 on the MS adapter and 200-300 using the 3rd party bridged AP.

I don't use WiFi for gaming however wanted to set gaming on WiFi on 2.4Ghz for some wireless testing. The times I have used WiFi for gaming it's always been on 5Ghz.

Anyone else see this or can offer up some info? Help?

[Hard Harry]

Hmm, first thing that comes to mind is the MAC address in the DHCP reservation, is it the MAC of the adapter or the Xbox? Maybe try cloning the MAC of the adapter to the Xbox? Or a easier work around is to set the DHCP reservation to a certian IP and then just set that IP as static on the Xbox.

[FurryNutz]

I believe it's the MAC address of the xbox as I looked at the MAC of both wireless adapters and they differ from what is seen on the router.

[Slomar]

Still no fix to original issue with Canadian 1.05 beta.

[FurryNutz]

So I did a quick test last nite with my DIR-826L and 868L with my roommates xbox slim wifi.
Using the 826L it connected at 65Mb.
Using the 868L it connected at 1Mb however I did not have the 868L connected to the main modem. Was just stand alone router with out any thing connected. The 826L is my current main router connected to the ISP modem.

I'll reconnect the 868L to the main modem and retest to see if there is an idle issue or not and sometimes I have noticed that the connection speed drops if there isn't anything going on on the xbox.

I'll check my DIR-810L as well.

[FurryNutz]

I put my DIR-868L online as the main host router and re-tested the Xbox Slim and it only connects or is being reported by the status page on the router as connecting at 5Mb and nothing higher is seen. I have forwarded this on to D-Link.

[Slomar]

Nice!  868L issues might grab their attention.

[FurryNutz]

Ya. I let them know about it. I'm hoping that someone will have a look and see where the issue comes from. Either MS or D-Link or combination of both. And good luck with getting MS to do anything. LOL.

[FurryNutz]

I have been in contact with D-Link and seems to have someones attention. Please be patient while they review the situation as I presume this could take some time. 

[Slomar]

Good to hear.  Just looked at the read count (9500)  It's not exactly youtube famous, but it seems we've got a few people looking at the issue.

[FurryNutz]

FYI people, got some basic info. Looks like the wireless drivers that reside on the xbox slims are the culprit. These are handled by MS and the xbox developers. Not sure if anything will be done. Since most of the new generation routers have more up to date drivers, this may cause problems with the xbox slim WiFi since those drivers maybe out of date and not fully compliant or work correctly with newer WiFi drivers on routers that they seem to be using now days.

I highly recommend to those seeing this problem with there xbox Slims as a alternative work around solution, disable the onboard WiFi and connect either wired LAN cable or install a DIR-868L/865L or a DAP model bridge. LAN wire connect the Slim to the back of the Bridged AP and then you'll have a better connection between the xbox and main host router. DAP-1522. 1525, 1533 and 1650 are good DAP models for bridging for the various DIR series of routers that are effected. The DIR-868L and 865L are now supporting full bridge mode so those can be used as bridges.
http://us.dlink.com/product-category/home-solutions/connect/access-points-range-extenders-and-bridges/
I've tested the DAP-1533, DIR-865L, 868L and 880L and all work well with the xbox Slim and even work with the Elites and XB1.

D-Link routers are not the only routers that see this issue. There has been reports of other Mfr routers exhibiting the same thing as well. Not sure if MS is aware or not sure if they will even do anything since new gen xboxes are arriving soon. If your stuck on getting the slim working with WiFi, you'll need to phone contact MS support and talk to them about this. Or use one of the suggestions above.

Good Luck.