T
Tommy Vielkanowitz
I am having some problems with a Windows XP box. To give
some background, Spybot and Ad-Aware removed over 500
instances of spyware, so this machine was pretty eaten up
with the stuff. Because of all of the spyware, the user
was having problems accessing the network. After the
system was cleaned, still having problems. The PC is not
getting an IP address from the DHCP server. When I
configure the NIC with a static IP address, I can see the
local network, but DNS does not work on this PC. It
works fine on other PCs on the network. Once I set the
static IP address, I went to
HKLM\system\currentcontrolset\services and deleted
winsock and winsock2 and then ran: netsh int ip reset
resetlog.txt from a command prompt. When I ran the netsh
command I got the following error message: Warning:
Could not obtain host information from machine:
[PAREMBURGXP]. Some commands may not be available.
Class not registered.
According to a Knowledgebase article, this was supposed
to reinstall TCP/IP on the XP machine.
If you have any solution to this problem other than
reinstall XP it would be greatly appreciated.
--Tommy Vielkanowitz
tvielkanowitz (at) shared-resources (dot) net
some background, Spybot and Ad-Aware removed over 500
instances of spyware, so this machine was pretty eaten up
with the stuff. Because of all of the spyware, the user
was having problems accessing the network. After the
system was cleaned, still having problems. The PC is not
getting an IP address from the DHCP server. When I
configure the NIC with a static IP address, I can see the
local network, but DNS does not work on this PC. It
works fine on other PCs on the network. Once I set the
static IP address, I went to
HKLM\system\currentcontrolset\services and deleted
winsock and winsock2 and then ran: netsh int ip reset
resetlog.txt from a command prompt. When I ran the netsh
command I got the following error message: Warning:
Could not obtain host information from machine:
[PAREMBURGXP]. Some commands may not be available.
Class not registered.
According to a Knowledgebase article, this was supposed
to reinstall TCP/IP on the XP machine.
If you have any solution to this problem other than
reinstall XP it would be greatly appreciated.
--Tommy Vielkanowitz
tvielkanowitz (at) shared-resources (dot) net