Dchp error

And there's no involvement with IPv6 in this picture?

 

IPv6 is fully supported by my ISP in my area but disabled on my router (which does support dual stack, though I haven't tried it yet).

 

I doubt it would work but id be curious to see if changing your networks IP scheme would have an effect

 

Also ipv6 sounds like it could work too but i cringe at the idea of converting all my static addresses to ipv6..

 

@GZA - But this do not occur when you're using wired solution, or the 2.4 Ghz range, correct?

 

It (cannot connect to DHCP server) happens on 2.4Ghz also--just did tonight. Not sure I've seen the problem on wired though. Just to be clear, unlike some folks, I can ultimately get up and going (though not on 5.8Ghz lately); but something is definitely
wrong here that is, I believe, what is causing others problems. There is no reason that the Xbox One should give a DHCP error at all in my setup (which includes many other devices connecting without issue) and certainly not when configuring the IP and network
settings manually on the Xbox One itself...

 

If you would navigate your way in to 'Alternate MAC address', is this option empty?

 

So tonight i was discussing this issue in a lobby for BF4 and a guy was telling me that he found a fix for this. He said you have to clear the cache for the system and then afterwards it would connect with no issues. His friend also confirmed this. He said
there is a button you push when hi-lighting the disk usage that clear the hd cache. Or something like that. I have not looked for the option myself but it sounded worth a try

 

@taidara, yes it's empty. I've never assigned an alternate MAC and have cleared it for good measure in the past and also because it is a convenient way to restart the Xbox One.

 

@GZA - It would be interesting to know if you can reproduce this with a wired solution.

How long have you had this problem?

 

@taidara - It has intermittently reported a spurious "cannot connect to DHCP server" error when connecting wirelessly using DHCP since I got it at launch. Actually, it did it also when wired to my 5.8ghz wireless bridge (WDS). It will eventually work
after a few tries or a reboot then work fine for a while. 5.8Ghz is especially problematic it seems.

Until recently, I had never tried assigning a static IP, so I'm not sure when that problem started but can't understand why it would ever contact DHCP when setting a static IP. Several other folks have reported problems assigning static IPs in this forum
and various other networking weirdness (beyond just NAT issues, which are generally user error/improper configuration). I believe there is a software problem behind most of these issues and that it is something go do with the way network settings are stored,
retrieved, and applied, especially when switching between wired/2.4/5.8 and DHCP/static (manual). It is almost like new settings don't always take for some reason--e.g. it still tries to use DHCP even after setting a static IP, gets "stuck" with bad or old
settings that results in DHCP failure, etc.

 

So this dhcp error has been happening to me from the start, when i power cycle the console and unplug the plug of my modem/router for 5 mins (just as it says on the networking issues page) it works 90% of the time. But this is not a fix as i have to go through
the steps on the trouble-shooting page every-time i turn it back on.

IT friend of mine just told me to use a static IP and that should fix the problem, but from some of the other posts on this thread it still doesn't seem to work?

 

You can try it, but in my experience and others assigning a static IP on the Xbox One is itself buggy. A lot of the time it just won't save or hold the static IP. I hope MS is taking the many reports of network issues like these seriously.

 

Last night i kept getting the DHCP error and it wouldn't connect, i turn it off for about an hour, turn it back on and it works, was connecting without the DHCP error the whole night. This morning when i got up (8:53 am here) i got the error again but when
i clicked on "check again" it said everything is good and connected without me having to disconnect my modem or anything.

This i getting annoying hopefully they are listening and provide a fix BEFORE Destiny or halo comes out.