• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Frustrating Windows 7 DHCP Issue

S

soulesschild

Supreme [H]ardness
Joined
Feb 18, 2007
Messages
6,176
So I know some of you may know about the Windows Vista/7 DHCP bug where if you use something other then a Windows based DHCP, Vista and 7 don't pull proper IPs. However, if you set manual IPs, you have internet just fine. There are registry fixes and stuff on the Microsoft databases but unfortunately, none of them seem to work.

Interestingly enough, this bug doesn't happen on a fresh install of Win 7. However, once you run an update (not sure which one and I'm too lazy to hunt down which one), it breaks the internet connection of the machine.

Now, if I set a manual IP to the machine, it works. Problem is, if the user brings the machine (a laptop home), they'd have to change it out of the manual IP range that we assign to users to get internet access again and it's just a hassle.

The easy way out is just to get a Windows DHCP but it's not available right now. So are there any IT support guys that have had this same issue? I've done everything I can and am just utterly defeated by this stupid issue (why did Microsoft change how this worked from XP??!?!?)

:mad:
 
Eh? I run a smoothwall at home and it does DHCP and I have never had a problem with any version of windows. I havent ever heard of this problem before, sounds to me like you have something weird going on there..
 
extide said:
Eh? I run a smoothwall at home and it does DHCP and I have never had a problem with any version of windows. I havent ever heard of this problem before, sounds to me like you have something weird going on there..
Click to expand...

It's this problem,

http://support.microsoft.com/kb/928233

Known by Microsoft yet still not fixed (despite them offering registry fixes that DONT work). We're running a linux based DHCP.

They also say it doesn't happen in Windows 7 but it still does :(
 
Last edited:
Configure your DHCP server to not suck then. If Linux's DHCP implementation doesn't support the BROADCAST flag that's a pretty epic fail.
 
So on further research, apparently people who use our particular setup, don't have issues, we just do so we're just hiring someone to come fix it for us. Lol. I'll be highly curious to see what the exact issue is. Thanks though for your replies though.
 
Arainach said:
Configure your DHCP server to not suck then. If Linux's DHCP implementation doesn't support the BROADCAST flag that's a pretty epic fail.
Click to expand...

First of all, the BROADCAST flag is not a MUST in the RFC, it's a SHOULD feature and thus not mandatory. And it was introduced because some networking stacks at the time (early 90's) couldn't receive unicast traffic without an address assigned, not because its a desireable feature. Why Microsoft changed to using the BROADCAST flag by default with no fallback is beyond me. It offers nothing, creates extra broadcast traffic on the network, and they've had (and continue to have) support for the preferred and better supported unicast method.

ISC DHCPD of course supports the legacy BROADCAST flag though, yet lots of folks still report issues with this DHCPD and others. Microsoft's DHCP client implementation is broken in at least two ways, and has a poor default configuration.

Which DHCPD are you using soulesschild? I've seen reports that the always-broadcast flood-your-network option in the ISC config file can resolve this, but taking a look at a packet capture from the Vista side might be helpful as well, it's very possible the broadcast traffic is being blocked by a switch or DHCP relay.
 
Arainach said:
Configure your DHCP server to not suck then. If Linux's DHCP implementation doesn't support the BROADCAST flag that's a pretty epic fail.
Click to expand...

Not sure what rock you've been hiding under but Windows and it's problems with DHCP and use of the BROADCAST flag are well known and they prevent windows from playing nice in a lot of network environments.
Posted via [H] Mobile Device
 
Wierd, we don't have this issue in our office, running win 7 enterprise (Chinese Simplified version)
What settings are you using? (subnet mask etc)
 
Why don't you use the alternate configuration tab? That's what it is there for.

When you get an IP via DHCP you get the IP offered by DHCP. When you don't get an IP you automatically get the alternate configuration IP.

Simple effective and it works.
 
Mackintire said:
Why don't you use the alternate configuration tab? That's what it is there for.

When you get an IP via DHCP you get the IP offered by DHCP. When you don't get an IP you automatically get the alternate configuration IP.

Simple effective and it works.
Click to expand...

Bad solution. Why not fix the actual problem instead of wrapping a silly work-around on top?

The alternate configuration is generally used for a machine that moves between a DHCP and non-DHCP network.
 
You must log in or register to reply here.
Back
Top