Hello
I am involved with supporting mostly XP based machines. I've serviced a number of machines which were severely infected with numerous spyware programs. Even though in most cases, I've been able to erradicate the spyware, I've been left with machines that won't pole the router for a DHCP IP address. I've checked several locations in the registry but have yet to find the problem. All the necessary services seem to be running also. So, I'm at a loss as to what causes this. I've not been able to find any articles related to it either.
What I'm thinking, is that something in the registry is changed when this happens, to disallow the DHCP service from operating properly. The only IP address I get when this happens, is the one generated when a DHCP server is not detected on the network. This is the address generated by XP's Automatic Private IP Addressing.
Has anyone ever come across this problem? Any help would be greatly appreciated.
Thanks.
fast586
I am involved with supporting mostly XP based machines. I've serviced a number of machines which were severely infected with numerous spyware programs. Even though in most cases, I've been able to erradicate the spyware, I've been left with machines that won't pole the router for a DHCP IP address. I've checked several locations in the registry but have yet to find the problem. All the necessary services seem to be running also. So, I'm at a loss as to what causes this. I've not been able to find any articles related to it either.
What I'm thinking, is that something in the registry is changed when this happens, to disallow the DHCP service from operating properly. The only IP address I get when this happens, is the one generated when a DHCP server is not detected on the network. This is the address generated by XP's Automatic Private IP Addressing.
Has anyone ever come across this problem? Any help would be greatly appreciated.
Thanks.
fast586