![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Good Day All!
Recently I've run into an issue in Windows 7 (bootcamp) that "seems" to be tied to the DHCP Lease on a lab of wireless Macbooks (education setting), and some wired MacMini machines.
In a nutshell the issue typically goes like this (in Windows 7 remember):
- System boots up fine and connects to the wireless (Wireless working fine)
- After a few minutes the wireless stops working and the machine starts getting a 169 address. I can then reconnect to the wireless and everything works fine.
- Repeat
I should confess that we have recently changed all our access points to HP MSM422 and they are controlled by a MSM 760 controller, and this is when the issue seemed to start. When the same machines are booted into MacOS X they DON'T exhibit the same issue.
I've done some googling and it appears it has something to do with the dhcp release time messing up, unfortunately I haven't come across a sure fire solution (yet).
Tomorrow I'm going to try and assign a static ip just for testing purposes. Unfortunately that can't be the only solution as that won't work in our environment as a permanent solution.
Would SP1 fix this issue? I'm 94% sure the machines don't have SP1 installed. It's also on my "to try" list tomorrow.
Recently I've run into an issue in Windows 7 (bootcamp) that "seems" to be tied to the DHCP Lease on a lab of wireless Macbooks (education setting), and some wired MacMini machines.
In a nutshell the issue typically goes like this (in Windows 7 remember):
- System boots up fine and connects to the wireless (Wireless working fine)
- After a few minutes the wireless stops working and the machine starts getting a 169 address. I can then reconnect to the wireless and everything works fine.
- Repeat
I should confess that we have recently changed all our access points to HP MSM422 and they are controlled by a MSM 760 controller, and this is when the issue seemed to start. When the same machines are booted into MacOS X they DON'T exhibit the same issue.
I've done some googling and it appears it has something to do with the dhcp release time messing up, unfortunately I haven't come across a sure fire solution (yet).
Tomorrow I'm going to try and assign a static ip just for testing purposes. Unfortunately that can't be the only solution as that won't work in our environment as a permanent solution.
Would SP1 fix this issue? I'm 94% sure the machines don't have SP1 installed. It's also on my "to try" list tomorrow.
Last edited: