a) Verify that the machine has at least one ether-net interface.

This can be done by running command devmgmt.msc (which opens device management console). Verify that network adapters exist and are installed properly.

 

b) Verify that the DHCP (DHCP Client) service is running.

Execute the command sc queryex dhcp and verify that the state of DHCP service is running.

 

c) Verify that the DHCP packets are not dropped by IPSEC or Firewall or BFE (Initial state of the machine -> No IP Address)

Stop the firewall service (net stop mpssvc) and run “ipconfig /renew”.

If the machine gets IP address this time, that means firewall is dropping the DHCP packets.

If still no IP Address, proceed with next step.

 

Stop the IPSEC service (net stop policyagent) and run “ipconfig /renew”.

If the machine gets IP address this time, that means policy agent is dropping the DHCP packets.

If still no IP Address, proceed with next step.

 

Stop the BFE service (net stop bfe) and run “ipconfig /renew”.

If the machine gets IP address this time, that means “BFE” is dropping the DHCP packets.

If still no IP Address, proceed with the remaining step.

 

Start all the above stopped services and then proceed to the next step.

 

d) Verify that there are no hardware connectivity issues.

Give a static IP address of the same subnet to the machine and see if you can reach the network. This is to avoid the issue of hardware glitches.

 

-Tanu Mutreja