Computer joined with domain can't get IP when off network
Hi all -
Here's the deal.
I have a user who has a company issued laptop that is joined with our domain.
On our network, he can get an IP address when both wired and wireless.
When he is not on our network, however, he can only get an IP address when connecting to a wireless network. When he tries to plug an Ethernet cable in, it gives him an invalid IP address. I have tried statically setting the IP address to no avail - there is no connectivity.
Any idea what could be causing this? Again, when he is on the domain, everything works fine (via DHCP and statically).
Thanks!
Here's the deal.
I have a user who has a company issued laptop that is joined with our domain.
On our network, he can get an IP address when both wired and wireless.
When he is not on our network, however, he can only get an IP address when connecting to a wireless network. When he tries to plug an Ethernet cable in, it gives him an invalid IP address. I have tried statically setting the IP address to no avail - there is no connectivity.
Any idea what could be causing this? Again, when he is on the domain, everything works fine (via DHCP and statically).
Thanks!
ASKER
It does the same thing on both AC power and battery.
I only have 2 other thoughts, but neither makes much sense to me.
1 Remove and add back to domain. This technically should do nothing.
2 Remove the nic and reinstall with latest driver. Again I would not expect this to work either.
1 Remove and add back to domain. This technically should do nothing.
2 Remove the nic and reinstall with latest driver. Again I would not expect this to work either.
ASKER
Won't be able to test either option until he takes the laptop home tonight, but will do both of those things
Anything in your (AD) policies that would interfere with the wired NIC?
Some firewall or security settings ?
Is he the only person who has this issue?
Some firewall or security settings ?
Is he the only person who has this issue?
ASKER
Nothing that I can see.. There may have been one other person with the same issue but I haven't had a chance to take a look at their computer to tell. That being said, 50+ users DON'T have this issue.. :\
Can you run some tests?
Sometimes, it could be that the DHCP server on the "non-AD" wired LAN has an issue.
I remember that I had a DHCP server that had recorded a "BAD ADDRESS" for one MAC address and then did not give a correct IP configuration to that particular host's Wired NIC.
Removing the existing lease/reservation entry solved the issue.
How many wired LANs has the user tried?
Sometimes, it could be that the DHCP server on the "non-AD" wired LAN has an issue.
I remember that I had a DHCP server that had recorded a "BAD ADDRESS" for one MAC address and then did not give a correct IP configuration to that particular host's Wired NIC.
Removing the existing lease/reservation entry solved the issue.
How many wired LANs has the user tried?
ASKER
It's not our DHCP server that has a problem - it's when the user takes it home. He has a DSL modem that plugs directly into his desktop. When he brings his laptop home, he unplugs the ethernet cable from the desktop and plugs it into the laptop. Even after power cycling both the laptop and the modem, it still won't pick up an IP address
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
user is going to get a wireless router rather than have someone (me) come take a look at the modem again
Often the laptop will disable the network port when running on battery to conserve battery power. You can go into device manager and properties and power management and make a change to not allow power control of the nic.