Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DC + a regular time server. Will it work?

Status
Not open for further replies.

JBruyet

IS-IT--Management
Apr 6, 2001
1,200
US
Hey all, I need to get an internal time server going for devices that aren't in the AD domain (credit card swipers for one, and my ProCurve switches don't seem to like the DC/time server either). I'm talking about devices that are looking on port 123 for the time information. I found MS kb816042 but before I make the change to one of my domain controllers I wanted to know if it would change the way computers in the domain get their time information. Will it? Should it NOT go on a domain controller? Any help here would be greatly appreciated.

Thanks,

Joe B
 
Let's not confuse how time services are used in AD domains in comparison with other devices/OS

1. All windows clients should get their time from a Domain Controller (using SNTP). Domain Controllers get time from either NTP or SNTP servers on the internet. SNTP is similar to NTP but certain functions are not the same and cannot be used by other OSses and devices that require pure NTP

2. For all non-windows OSses and devices have them point to an actual NTP server on the internet or local which synchs with internet based NTP servers.
 
itsp1965, that's what I'm trying to do--I want a local NTP server on my network. My question is if I add the NTP service to my DC would it have any negative effects on any of the other services a DC offers? Specifically would it mess with workstations trying to update their clocks through SNTP?

Thanks,

Joe B
 
Not sure but I would figure you would not want to enable NTP on the same domain controller that has the PDC emulator role (hence the one that provides time synch) as what could happen is your clients will end up attempting to synch via NTP instead.
Wouldn't it be better just to setup an NTP server on a member server, VM, etc as opposed to putting it on a DC
 
I was hoping to point "everything" to one server but I think you're right--probably better to use something not that important to the domain.

Thanks,

Joe B
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top