Prev: Resovled - RPC over HTTP Issue
Next: SBS BPA 2008: WARNING: DNS name server records do not exists
From: Wael on 26 Mar 2010 17:08
Hi,

I get this error when I do dcdiag. Everything else is fine and the
server is able to synchronize the time correctly (and the workstations
are able to sync with the local pdc server). What could be wrong?

Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error 1355
A Good Time Server could not be located.
......................... MyOrganization.local failed test
FsmoCheck

Thanks
From: Ace Fekay [MVP-DS, MCT] on 26 Mar 2010 23:56
"Wael" <sedky69(a)gmail.com> wrote in message news:81ffb177-b1a6-4bd5-bb66-d6800d0f5f75(a)q16g2000yqq.googlegroups.com...
> Hi,
>
> I get this error when I do dcdiag. Everything else is fine and the
> server is able to synchronize the time correctly (and the workstations
> are able to sync with the local pdc server). What could be wrong?
>
> Starting test: FsmoCheck
> Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
> A Time Server could not be located.
> The server holding the PDC role is down.
> Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
> error 1355
> A Good Time Server could not be located.
> ......................... MyOrganization.local failed test
> FsmoCheck
>
> Thanks


Well, you didn;t give us much to go on, such as configuration info (ipconfig /all, Event error logs, if there's an additional DC in your SBS domain, if you have a firewall blocking UDP123, etc).

What I can help with if you can't provide that info, is my blog on setting the time service. I hope you find it helpful.

Configuring the Windows Time Service for Windows Server
http://msmvps.com/blogs/acefekay/archive/2009/09/18/configuring-the-windows-time-service-for-windows-server.aspx

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
From: kj [SBS MVP] on 28 Mar 2010 18:55
Wael wrote:
> Hi,
>
> I get this error when I do dcdiag. Everything else is fine and the
> server is able to synchronize the time correctly (and the workstations
> are able to sync with the local pdc server). What could be wrong?
>
> Starting test: FsmoCheck
> Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
> A Time Server could not be located.
> The server holding the PDC role is down.
> Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
> error 1355
> A Good Time Server could not be located.
> ......................... MyOrganization.local failed test
> FsmoCheck
>
> Thanks

The Event logs should provide information about why the PDCe is not
advertsising as a time source.
Check the event log sequence just after reboot/restart.
--
/kj


 | 
Pages: 1
Prev: Resovled - RPC over HTTP Issue
Next: SBS BPA 2008: WARNING: DNS name server records do not exists