Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 409
  • Last Modified:

Windows XP PC unable to communicate with domain controller

I have a single windows XP pro PC that is not able to communicate with the domain controller. I have 20 other pc's no problem. This pc was working as well up until a little while ago. Here is what I have done so far...

Rebooted PC
netsh winsock reset
netsh winsock reset catalog
ipconfig /dnsdlush

removed from domain
tried to rejoin domain, unable to contact DC
deleted instance from AD
deleted instance from DNS

Server can ping all other PC's gets no reply on this pc, same with the PC, PC can ping all pc's just not server.

Removed avg free just in case, also running Norton removal tool just in case.

Gave the PC a static, then DHCP, also weird thing is I can VNC from the server to the PC???
0
eli290
Asked:
eli290
  • 4
  • 2
1 Solution
 
CompProbSolvCommented:
Is the symptom just that it can't ping the server?  Can it access shares there?  Can it get to the internet?

Are there other shares on the domain on other devices?  If not, I'd share a folder on another computer that is part of the domain and see if it can access it.  I'm trying to separate basic network issues (pinging success with other PCs implies this is fine), from AD issues, from issues specifically with this server.

What is used for DNS?

When you ping the server, are you pinging it by name or by IP?  If by name, is it getting resolved?
0
 
eli290Author Commented:
Pinging by name or Ip doesnt work. I just tried to restore back to a previous day and I get the following error when trying to connect to a network drive. The system detected a possible attempt to compromise security. please ensure that you can contact the serfver that is authenticating you
0
 
CompProbSolvCommented:
The following:
http://support.microsoft.com/kb/938457
says that one problem can be a firewall blocking TCP or UDP port 88.  Make sure there is no blocking going on within the workstation.

This (and other links):
http://www.techsupportforum.com/forums/f103/system-detected-a-possible-attempt-to-compromise-security-600653.html
says that it could be a DNS issue.  What is the workstation using for DNS?  If you could post the output of ipconfig /all here (from the workstation) that could be useful.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
eli290Author Commented:
I checked both the firewall on the DC and it is off but also just in case i went into advanced and added an allow rule for port 88 for tcp and UDP.

IP config is like this

192.168.111.111
255.255.255.0
192.168.111.1

DNS - 192.168.111.11
               8.8.8.8 (added this after the fact, took it out same result)
DC address is 192.168.111.11
.
0
 
CompProbSolvCommented:
Since other PCs can get to the server I'm not too concerned about the firewall on it.

I would have concerns about any sort of firewall on the workstation, though.  You did mention removing AVG and Norton, which is a good step.  I've found it may not be enough to disable them (either internally or through msconfig).  I'd make sure Windows Firewall is not running.

What happens if you try Start, Run, \\192.168.111.11\

Also... as an aside... just have the .11 for DNS, don't do the external one.  I do recognize that you tested it with and without, just general advice here.
0
 
CompProbSolvCommented:
Also... what if you do nslookup <servername> ?  Does it resolve correctly?
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now