nt sure what you mean... we're taking seats, yes?
Main Topics
Browse All TopicsI usually setup a new install or XPSP3 as part of a work group to start, and then join it to the domain through the properties>computername>Ch
I put in the domain name, it asks for credential,s and a few seconds later it says Welcom to <domain name>
I have a situation now where I'm trying to join a fresh install to the domain, and then it just hangs with the hour glass for a long time after i put in my credentials. I've repeated it with different Admin accounts and still the same thing. The attached screen cap is the error I finally get.
Changes recently made to the server recently are as follows:
Transfered FSMO Roles over from older DC
Synchronised server with Internet based clock.
Synchronised Each client with the same clock.
Microsoft update last night, needs reboot.
We are running Windows XP Clients and the DC in question is Windows Server 2003 R2
Please help!
Thanks,
JPertchik
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Some questions for troublehsooting...
How many DCs do you have now? When you say you've sync the clients with the same clock, do you mean the internet time source? You should be syncing clients with your networks internal time source, typically your PDC emulator, which in turn can either use an external source or it's own internal clock.
Is DNS correctly configured on the client to look at the new DC? Is DNS up and running on this DC? Are the DCs DNS records (Host and SRV) registered correctly on the DC (try stop/starting the NETLOGON service on the DC to re-register them).
Have you successfully joined any clients to the domain since making your changes? Is the network traffic getting through to the new DC (try disabling windows firewall on the DC).
All is as it should be IP wise:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Setup>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : jpertchik
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : owprnetwork.local
hsd1.va.comcast.net
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-10-18-0C-3F-16
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.145
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.15
192.168.1.14
Lease Obtained. . . . . . . . . . : Friday, April 17, 2009 9:36:31 AM
Lease Expires . . . . . . . . . . : Friday, April 17, 2009 10:36:31 AM
Ethernet adapter Wireless Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Compact Wireless-G USB Network Adapt
er
Physical Address. . . . . . . . . : 00-23-69-0E-E2-29
C:\Documents and Settings\Setup>
I assume the 2 DNS server are the domain controllers right?
Is the transfer of FSMO a succes? Can your 2 domain controllers can perform replication on NTDS settings? (located start --> run type: dssite.msc)
Please check your event logs and paste here errors specifically from "directory services" section.
Falcon
OK make sure you have Group Policy Manager installed on your DC and check out the following article.
http://technet.microsoft.c
Normally Windows clients on a domain synced their time on the Domain Controller.
You can do the following approach:
1) Add on DHCP Settings --> Server Options "TIME SERVER" pointing to active directory
2) Via Group Policy like what cmorffew suggested (search google for more info and more print screens)
I'm quite positive there's more problem other than time sync. Is there error messages on event logs?
Kindly post it here.
You will need to run mmc.exe
then add the addin - group policy manager
once in there you can then change the gp to set your time servers as per the link i posted.
Alternatively, as Falcon said, go into your DHCP server add-in(again in mmc) and "1) Add on DHCP Settings --> Server Options "TIME SERVER" pointing to active directory"
Wow, the posts are coming in thick and fast here!!
The first thing I would do, is check the event logs on the DCs to ensure there aren't any obvious problems in there. If there are, take some screenshots and post them on here.
If you're looking to set up time synchronisation across your domain, read this article - http://articles.techrepubl
Most will have their DC syncing with an internet time source, and all the clients syncing with the DC. The article above explains how to set it all up properly.
Take one step at a time, if you try and do too much at once, you'll only end up tangled and confused... :P
Pete
I believe the Author has 3 options to resolve the problem,
1. manual update the time on each machine that needs to join the domain and then continuously update the time on each machine as it falls out of acceptable time difference parameters.
2. move the DHCP server role away from the Firewall/Router and on to the DC and add the TIME SERVER option as per chatxfalcon
3. Use Group Policy to set the NTP to the desired settings and control ALL machines in the domain.(this would work for static and dynamic IP address reservations/leases)
If the issue really was an out of sync client/server time, then a check of the Timer server setup should be done. For correct internal time, the domain should reference one source - the DC or another dedicated NTP server. The NTP server or DC server should sync its time with an internet based time source. e.g. Internet Time Server-> DC Time Server-> Client Time.
Suggested Links:
Group Policy overview http://technet.microsoft.c
Configuring time server via group policy http://technet.microsoft.c
How to configure an authoritative time server in Windows Server 2003 http://support.microsoft.c
Business Accounts
Answer for Membership
by: cmorffewPosted on 2009-04-17 at 06:13:11ID: 24167364
what license model is the server running?