• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 383
  • Last Modified:

XP Hangs when logging in when connecting to 2011 SBS

Hello,

I am receiving the following errors on a laptop that I have recently added to our domain.  The laptop is located at another location away from the server and connected by a wireless link.  It is located on a different subnet other computers, laptops and PC's have not had this issue.  I have checked DNS on the server and it lists the laptop I am having the issue with.  Also on the laptop the DNS server comes up with the correct IP for the SBS server.  The system just hangs for several minutes when logging in and then can't access the SBS resources once it does. The laptop was working fine on Friday prior to being shutdown for the weekend.

The errors in the event viewer are as follows:
Windows cannot determine the user or computer name.  (an internal error has occured) group policy processing aborted.
The security system could not establish a secured connection with the server DNS.  No authentication protocol was available.
The security system detected an attempted downgrade attach for server.  The failure code from authentication protocol Kerberos was "there are currently no logon servers available to service the logon request)

From what I have been able to find this could be a DNS issue I suspect but I am not sure on how to correct it.  If any of you suggest a DNS issue please be specific on what I might need to correct it.  

We can use VNC from the other location np to access the laptop by name, that is something I thought might be useful as well as that would tell me that the DNS has to be working I would think?  Also I have upgraded the network card drivers and tried both a wireless and wired connection.  
Thanks in advance for your assistance.
0
efx-wpg
Asked:
efx-wpg
  • 7
  • 5
1 Solution
 
setasoujiroCommented:
just to be sure, because i'm not to sure about all you said.
The xp client, does he have the right dns server configured? that is the dc?
and if so, can you once logged on, ping to the fqdn of the sbs?
0
 
efx-wpgAuthor Commented:
Yes the right DNS server is there, it is configured through DHCP and I verified its the SBS and it is.  I can ping the server for sure as well from that laptop.  the laptop did connect fine last week, it seemed like after it was rebooted is when the problem occured.
0
 
setasoujiroCommented:
can you try to rejoin the domain?
0
Get Certified for a Job in Cybersecurity

Want an exciting career in an emerging field? Earn your MS in Cybersecurity and get certified in ethical hacking or computer forensic investigation. WGU’s MSCSIA degree program was designed to meet the most recent U.S. Department of Homeland Security (DHS) and NSA guidelines.  

 
efx-wpgAuthor Commented:
Just had another computer now show up with the same problem.  These are the last two that were added, not sure if I should start a new question. Do you recommend readding both of them?
0
 
setasoujiroCommented:
no i wouldn't
and you are 1000% sure dns is working fine?
if you ping servername, it gives replies?
and if you ping servername.domain.suffix ?
0
 
efx-wpgAuthor Commented:
I can ping servername.domain.local yes.  Do you recommend anything else I can check to ensure DNS is working?
0
 
setasoujiroCommented:
one other question, where is the dc pointing for his dns?
it must be pointing to itself (127.0.0.1)
0
 
efx-wpgAuthor Commented:
The server name  has an address that is used on our local network.  For example our server is called dfps01 and has a host entry in the DNS of 192.168.5.25 which is the server's IP address on our local network.  dfps01 is the SBS server IP address.  We have had this installed since Feb. this way and these two workstations are the first issues we have come across, is that the information you were requesting?  From what your saying this entry should be 127.0.0.1 on the server itself?  Should that have caused other issues before though?
0
 
setasoujiroCommented:
check the network interfcae properties on the dc, and check wether it is pointing to itself in the dns section of the properties (127.0.0.1)
0
 
efx-wpgAuthor Commented:
It is pointing to 192.168.5.25 the IP of the server.  This should be 127.0.0.1 your saying correct?
0
 
efx-wpgAuthor Commented:
MS Article 244474 fixed the issue.  I had ran the auto fix yesterday but apparently I needed to run the manual fix, did this and all is well.
0
 
efx-wpgAuthor Commented:
Figured it out myself which is why the solution is from me.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Identify and Prevent Potential Cyber-threats

Become the white hat who helps safeguard our interconnected world. Transform your career future by earning your MS in Cybersecurity. WGU’s MSCSIA degree program was designed in collaboration with national intelligence organizations and IT industry leaders.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now