> Thankyou for your answer!
>
> No, this problems are on Domain Members.
> DNS configured on them are both DC's.
> Yes, they have fixes IP addresses.
>
> The problem is just during startup, after that, they work well.
> The major problem are with SQL Servers, because we use domain users on its
> services and when they startup can't contact AD and we must restart it
> manually after server is booted up.
>
> FM
>
> "Meinolf Weber [MVP-DS]" <meiweb(nospam)[ at ]gmx.de> escreveu na mensagem
> news:ff16fb6610fae8cb2f7ed65fcb20[ at ]msnews.microsoft.com...
>> Hello Fabio,
>>
>> Event id 5719 with source netlogon is about connectivity. Is the server
>> configured to use the domain DNS servers only, no ISP's DNS on the NIC?
>> Does it have fixed ip or DHCP? Is it a domain member server or domain
>> controller? Please describe your domain setup a bit more detailed. Also
>> time problems states connection problems to the domain / domain
>> controller.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm>>
>>> Hi!
>>>
>>> We have servers that some services doesn't start automatically because
>>> they can't contact AD when it's booting up, some services like SQL
>>> Server. So we have to configure it to try in case of fail, and anyway,
>>> we have to start it manually.
>>>
>>> In event viewer, event 5719 on Netlogon and event 18 on W32Time, among
>>> others, are very common.
>>>
>>> How can I solve this problem?
>>> It's like that it has a delay to start the network and other services
>>> try to
>>> start with network unavailable yet.
>>> Thankyou in advance.
>>>
>>> FM
>>>
>>
>>
>
>