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

XP Client cannot join a domain due to time server problems

I have a DNS w/ AD running at home. Each pc, including this XP client, is addressable by  other PCs on the network via ping. I can even surf to the web pages on the Win 2003 SBS (which is the DNS server). When I try to have the XP client join the domain, I get problems. Don't know where to start. I need to have authentication for security.

I currently have the XP PC set to use the domain, but when I try to login using the domain, I get the date time synch error. So in reading some of the articles, it appears I may need a timeserver. I think the one currently used by Xp is time.windows.com.

What does anyone suggest? Please keep in mind I may need specific directions on how to perform the steps you ask me.

In advance, thank you.
0
rathodr
Asked:
rathodr
  • 4
  • 2
  • 2
2 Solutions
 
mattisflonesCommented:
Hi rathodr,
Do this from the server net time \\computername /set /yes first, then try...

Mattis
0
 
mattisflonesCommented:
You can also try creating a computer account for the machine before you join it..
I assume you can ping fine, and use network shares without any problems?
0
 
jncashCommented:
another simple solution -- that solved the same problem for me -- check the date and time on on the machine -- that was the simple solution to my problem -- I had been messing around in the bios and inadvertently changed the year.  make sure the XP machine's date and time and the server's date and time match.  Good Luck
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
rathodrAuthor Commented:
Luck is what I need!

on the DNS server, did the net time \\servername /set /yes
--> the command was successful

on the XP client, in WORKGROUP mode, I went to control panel/date time snap-in/internet time
--> I set the timeserver to the servername above and clicked 'Update Now'
--> Update unsuccessful. There were no reasons provided why it was unsuccessful.
--> I used another non-existent name and clicked Update Now and the error message reported the server does not exist.

I can ping fine. I can even go to the web page on that server without any problems. I don't create any shares off of the server so I keep the connections clean. Besides, there is nothing I really want to share off of the server (files, directories, etc.) anyway -- so, I did not verify if the shares are an issue.

My thought is that if that sync works, then the date/time will match and then I can login using the proper credentials against AD.

What would cause the sync. to be unsuccessful in the date/time snap-in?
0
 
mattisflonesCommented:
I honestly don`t know.. I`ve experienced the same problem as you when joining a domain through VPN.. It did always fix itself upon the second try.. so i do not think this is the core of the isue, witch leads me to believe that the problem might be a winsock or netbios problem on the XP client...
Heres a winsockfix: http://members.shaw.ca/techcd/VB_Projects/
and something on XP-IP connectivity.. http://support.microsoft.com/default.aspx?scid=kb;EN-US;314067
0
 
rathodrAuthor Commented:
Ok, got it working. The solution consisted of two answers above. The first to set the timeserver. As I said before, it worked fine. The second solution was by jncash to check the date and time. When I did my preliminary setup in BIOS, I made the date time sync with my clock in the kitchen (its pretty accurate). But after I loaded XP, somehow the day shifted one day ahead. So, I didn't notice it right away since most of the articles I have been reading have been referring to checking the year. Well, the year and month are correct, only the day was wrong. I manually changed the day in WORKGROUP mode, went on to the Domain, and BAM, everything worked.

The credits should be shared on this one!

Thank you both for your responses.
0
 
mattisflonesCommented:
Glad we could be of assistance.. :-)
0
 
jncashCommented:
great!! glad it worked -- an old saying:  "Computers don't do what we want them to do -- they do what we tell them to do" --

not my quote -- can't remember the author --
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

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