PC Not Receiving IP Address From DHCP Server
Hi;
I have a machine which does keeps receiving a 169. . . address on its home network. The home network is a Windows 2008 AD domain. The machine was cleaned and separated for specific use by employees for internet access.
The onboard card sometims works at my office so a different PCI ethernet card was installed which works perfectly at my office. However, when it was returned to the home network the new card stopped receiving an IP address.
Eset Smart Security was previously installed but it was removed as part of the troubleshooting process. I have attached my mobile machine to the network cable used by that machine and I immediately got an IP address and was able to browse the internal network and internet.
I need to get it resolved tomorrow so your assistant would be appreciated.
I have a machine which does keeps receiving a 169. . . address on its home network. The home network is a Windows 2008 AD domain. The machine was cleaned and separated for specific use by employees for internet access.
The onboard card sometims works at my office so a different PCI ethernet card was installed which works perfectly at my office. However, when it was returned to the home network the new card stopped receiving an IP address.
Eset Smart Security was previously installed but it was removed as part of the troubleshooting process. I have attached my mobile machine to the network cable used by that machine and I immediately got an IP address and was able to browse the internal network and internet.
I need to get it resolved tomorrow so your assistant would be appreciated.
wolfcamel
try dropping the speed on the network card, or trying a different port.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i think the ip address or the machine name is clashing on the network check the computer name and try
regards
gaurav
regards
gaurav
Test the machine on a different cable. My thought is that it will fail there, too.
Delete the protocol stack and driver for the card. Then, install updated drivers and allow the stack to be rebuilt.
Delete the protocol stack and driver for the card. Then, install updated drivers and allow the stack to be rebuilt.
Also have a look at the duplex / speed settings on your network card..
Not sure of your switching infrastructure, but there may be mismatches of duplex/speed - ie port hardcoded to 1GB. Network card only being 100mb etc..
Also, as it is a PCI card, that works on a different PC - ie different software, i would jump on the manufactures website, and download the latest drivers.. The drivers on the machine may not have been installed properly / become corrupt, or may need an updated version to work with the System OS SP, patches etc...
Cheers
Not sure of your switching infrastructure, but there may be mismatches of duplex/speed - ie port hardcoded to 1GB. Network card only being 100mb etc..
Also, as it is a PCI card, that works on a different PC - ie different software, i would jump on the manufactures website, and download the latest drivers.. The drivers on the machine may not have been installed properly / become corrupt, or may need an updated version to work with the System OS SP, patches etc...
Cheers
ASKER
Ok;
The cable is working . As I indicated my netbook has no issues when using the same connection.
Secondly why would I need to rebuild the stack for a new card.
I have already renamed the computer and ran ipconfig/renew, I have also tried giving a static ip address .
Finally the new card works on the same machine just at a different physical location on a different network.
All of the things mentioned above have basically already been tried.
The cable is working . As I indicated my netbook has no issues when using the same connection.
Secondly why would I need to rebuild the stack for a new card.
I have already renamed the computer and ran ipconfig/renew, I have also tried giving a static ip address .
Finally the new card works on the same machine just at a different physical location on a different network.
All of the things mentioned above have basically already been tried.
a couple of things:
What is the make / model of the card and switch that its plugged into.
1st thing i would try is to set a static ip address to an address that is the same network address as te rest and set the last octect to an address that is not on the list of host address and not used by any other machine with your server as the default gateway and the same mask as the server(obviously) then try to ping the server if that fails then DHCP is not your problem - only a sympton of a bigger problem.
remember your laptop my be 100 mb using 4 cores of the cable and 1gb uses all 8 and i've also seen problems where the machine sees the connection but no data transferred if one of the cores are faulty. - i would use a cable tester to check the link from the back of the PC right to the switch.
if youy can ping then i wonder...
Have you checked the event log on the client machine for any errors eg dhcp client service not started.
have you checked the dhcp server admin tool on the server to see if the machine name is listed - if so delete the machine name from the list and try again
let me know how you get on
What is the make / model of the card and switch that its plugged into.
1st thing i would try is to set a static ip address to an address that is the same network address as te rest and set the last octect to an address that is not on the list of host address and not used by any other machine with your server as the default gateway and the same mask as the server(obviously) then try to ping the server if that fails then DHCP is not your problem - only a sympton of a bigger problem.
remember your laptop my be 100 mb using 4 cores of the cable and 1gb uses all 8 and i've also seen problems where the machine sees the connection but no data transferred if one of the cores are faulty. - i would use a cable tester to check the link from the back of the PC right to the switch.
if youy can ping then i wonder...
Have you checked the event log on the client machine for any errors eg dhcp client service not started.
have you checked the dhcp server admin tool on the server to see if the machine name is listed - if so delete the machine name from the list and try again
let me know how you get on
Make sure both the DHCP and DNS Client services are started and set to Automatic. You can look for these in Services.msc.
Have you tried creating a DHCP reservation for this PC?
This will confirm that the PC is at least reaching the DHCP Server.
Make sure that there are no other settings enabled on the TCP/IP configuration, except, Obtain an IP address automatically.
If you really want to start troubleshooting then install a network sniffer tool to see if network card broadcasting the correct information.
Do you know if there is a Network Access Control device on the network?
This could be stopping this PC from obtaining an IP address?
This will confirm that the PC is at least reaching the DHCP Server.
Make sure that there are no other settings enabled on the TCP/IP configuration, except, Obtain an IP address automatically.
If you really want to start troubleshooting then install a network sniffer tool to see if network card broadcasting the correct information.
Do you know if there is a Network Access Control device on the network?
This could be stopping this PC from obtaining an IP address?
ASKER
Hi;
The tech from my office who did the cable did not follow the standard code but just put the pairs sequentially. While it worked on my mobile machine it would not work on the pc. While on another job with another tech from the company I insisted that he use the right sequence and at that point he indicated that the other tech had not used it there. I changed the ends using the right sequence and that was it. Everything worked fine.
The tech from my office who did the cable did not follow the standard code but just put the pairs sequentially. While it worked on my mobile machine it would not work on the pc. While on another job with another tech from the company I insisted that he use the right sequence and at that point he indicated that the other tech had not used it there. I changed the ends using the right sequence and that was it. Everything worked fine.