DHCP client tries to aquire an IP for not connected network cards
Hello, I have a problem with a Windows 7 64 bits. After power on, the DHCP client tries to acquire an IP for all the network cards, even those that are not connected. I can see in the event logs that after 2 minutes from the startup, I get one message for each interface: Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0xMAC_ADDRESS. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server." I have an Astaro VPN client that manifests itself as a network card and when I start it up (manually) it fails to receive an IP from the DHCP server. I believe it is related with this general DHCP problem because if I start it up within two minutes from power on (before I get those messages in the event log), then it works. Any idea how to debug this problem? I had a Dell connection manager which I uninstalled (thinking it will solve the problem), maybe this one left some bad traces. Any idea how to find and remove them? In general, how would one know all the programs that are dealing/interfering with the network connections and dhcp settings?
October 25th, 2011 12:08pm

You can disable the network adapters that are not required when you login. if the newtork adapters try fetching IP address and fail, what is the IP address they are getting ?? 169.254.xx.xx range ? Alternate solution is if you are not using DHCP server at all, then you can disable the DHCP service from services.msc Regards, h9ck3r.
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2011 1:35am

Nope, they don't get any address at all. They show as "network cable unplugged". But when I connect the cable or I start the VPN, then it gets a 169.254 IP address. On the dhcp server I can see that the client is not even sending a dhcp request. I don't want to disable the network adapters because they are required. My question is why the dhcp is trying to acquire IP addresses for the adapters that are not connected.
October 26th, 2011 7:12am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics