Can't find DNS server.

[Guest]

This computer can't find the Windows2000 server. The workstation had a sever
adware infestation, and now can't find its way home. Symptoms:
1. I can't ping it from other computers or server.
2. It won't map named drive on Win2k server.
3. Errors in Event Viewer: "DCOM was unable to communicate with the
computer BILLB using any of the configured protocols."
4. Can ping server by IP address, but not by name, from this machine.

Running XP SP2. I am letting Norton INternet Security handle firewall duties.

ipconfig.txt below:



Windows IP Configuration



Host Name . . . . . . . . . . . . : PatDell

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No
Note: When I run this from my own workstation,
the DNS Suffix Search List is added after this line.


Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controller

Physical Address. . . . . . . . . : 00-0D-56-28-ED-5A

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.12

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.200

DNS Servers . . . . . . . . . . . : 192.168.1.200

Primary WINS Server . . . . . . . : 192.168.1.200

Lease Obtained. . . . . . . . . . : Wednesday, August 10, 2005
12:40:46 PM

Lease Expires . . . . . . . . . . : Thursday, August 18, 2005
12:40:46 PM

 

[RWS]

http://support.microsoft.com/kb/811259
How to recover from Winsock2 corruption
Windows XP with Service Pack 2 instructions
To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed,
type netsh winsock reset at the command prompt, and then press ENTER.

Note Restart the computer after you run this command. Additionally, for
computers that are running Windows XP SP2, there is a new netsh command that
can rebuild the Winsock key. For more information, visit the following Web
site:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx
(http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx)
Warning Programs that access or monitor the Internet such as antivirus,
firewall. or proxy clients may be negatively affected when you run the netsh
winsock reset command. If you have a program that no longer functions
correctly after you use this resolution, reinstall the program to restore
functionality.

 

[Chuck]

This computer can't find the Windows2000 server. The workstation had a sever
adware infestation, and now can't find its way home. Symptoms:
1. I can't ping it from other computers or server.
2. It won't map named drive on Win2k server.
3. Errors in Event Viewer: "DCOM was unable to communicate with the
computer BILLB using any of the configured protocols."
4. Can ping server by IP address, but not by name, from this machine.

Running XP SP2. I am letting Norton INternet Security handle firewall duties.

ipconfig.txt below:



Windows IP Configuration



Host Name . . . . . . . . . . . . : PatDell

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No
Note: When I run this from my own workstation,
the DNS Suffix Search List is added after this line.


Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controller

Physical Address. . . . . . . . . : 00-0D-56-28-ED-5A

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.12

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.200

DNS Servers . . . . . . . . . . . : 192.168.1.200

Primary WINS Server . . . . . . . : 192.168.1.200

Lease Obtained. . . . . . . . . . : Wednesday, August 10, 2005
12:40:46 PM

Lease Expires . . . . . . . . . . : Thursday, August 18, 2005
12:40:46 PM

Will,

If the problem doesn't involve Norton Internet Security (Norton Personal
Firewall), I'd start by checking for an LSP / Winsock problem:
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>

If you try all 5 solutions recommended, and no improvement, then un install
Norton Personal Firewall, using instructions from Symantec. NIS / NPF doesn't
un install easily, so be thorough. And please let us know what works or doesn't
work for you.

 

[Guest]

Well, I ran netsh winsock reset catalog and it really didn't seem to get me
anywhere, (but maybe it helped in ways I couldn't see) and the other winsock
solutions didn't really apply.
So I looked at registry settings mentioned in one of Chuck's IP articles. I
filled in appropriate values for Domain, SearchList, and NameServer keys as
they appeared on the ipconfig of a properly functioning machine on our
network. Eureka! Now I could ping the server by name! I launched the
application that wouldn't run before, and after telling Norton Internet
Security that it was OK to access the server, we were off and running.

So thank you for your help. Your suggestions, a lot of great network info
on Chuck's blog, and some trial and error saved the day (er... week).

Will

 

[Chuck]

Well, I ran netsh winsock reset catalog and it really didn't seem to get me
anywhere, (but maybe it helped in ways I couldn't see) and the other winsock
solutions didn't really apply.
So I looked at registry settings mentioned in one of Chuck's IP articles. I
filled in appropriate values for Domain, SearchList, and NameServer keys as
they appeared on the ipconfig of a properly functioning machine on our
network. Eureka! Now I could ping the server by name! I launched the
application that wouldn't run before, and after telling Norton Internet
Security that it was OK to access the server, we were off and running.

So thank you for your help. Your suggestions, a lot of great network info
on Chuck's blog, and some trial and error saved the day (er... week).

Will

Will,

Thanks for the update, and the feedback. Where did you fill in those values?
Was your DNS server not setup to issue the information? Do you have an actual
DNS / WINS server (indicated as 192.168.1.200)?

 

[Guest]

:

Will,

Thanks for the update, and the feedback. Where did you fill in those values?
Was your DNS server not setup to issue the information? Do you have an actual
DNS / WINS server (indicated as 192.168.1.200)?

Chuck,

We do have an actual DNS/DHCP server at 192.168.1.200. I don't know about
the WINS -- we don't really use that aspect. The registry keys I used were
in:
HKLM>SYSTEM>Current Control Set>Services>Tcpip>Parameters. The Database
Path looked OK, so I looked at some of the other parameters.

Will

 

[Chuck]

:



Chuck,

We do have an actual DNS/DHCP server at 192.168.1.200. I don't know about
the WINS -- we don't really use that aspect. The registry keys I used were
in:
HKLM>SYSTEM>Current Control Set>Services>Tcpip>Parameters. The Database
Path looked OK, so I looked at some of the other parameters.

Will

Will,

If you have a DHCP server, then it should provide some of that information. So
you may still have a problem.

The "netsh winsock..." command is one of four similar (but not redundant) fixes
for the LSP / Winsock problem. If you look at this forum, you will see cases
where the OP has reported one of those four (five even) has worked, while the
others didn't.