Re: Lost connection..? by Pegasus
Pegasus
Sun Mar 02 11:55:56 PST 2008
"Kent J" <kent.johnson@telia.com> wrote in message
news:pqCyj.4329$R_4.3136@newsb.telia.net...
> Pegasus (MVP) skrev:
>> "Kent J" <kent.johnson@telia.com> wrote in message
>> news:DYwyj.4311$R_4.3055@newsb.telia.net...
>>> Pegasus (MVP) skrev:
>>>> "Kent J" <kent.johnson@telia.com> wrote in message
>>>> news:vTdyj.4303$R_4.3040@newsb.telia.net...
>>>>> Hi all,
>>>>>
>>>>> I have a server that sometimes loses connetion with the network
>>>>> without apperent reason.
>>>>> Last time the server lost connection there were no activity on the
>>>>> server and after a restart connection where up and running again.
>>>>> After a few weeks the problem comes back.
>>>>>
>>>>> Can it something wrong with the network card?
>>>>>
>>>>> Kent J.
>>>> I would start by looking at the Event Viewer.
>>> OK!
>>>
>>> This is what I have:
>>> =================================
>>> The Security System detected an authentication error for the server
>>> DNS/dns1.MyDNS.se. The failure code from authentication protocol
>>> Kerberos
>>> was "There are currently no logon servers available to service the logon
>>> request.
>>> ==================================
>>>
>>> The system failed to register host (A) resource records (RRs) for
>>> network adapter
>>>
>>> with settings:
>>> Adapter Name : {DDCD65F0-1AA7-4019-BBD2-F65CC8A7DA49}
>>> Host Name : MyServer
>>> Primary Domain Suffix : MyDns.se
>>> DNS server list :
>>> xx.xxx.xx.xx,xx.xxx.xx.xx
>>> Sent update to server : <?>
>>> IP Address(es) :
>>> xx.xxx.xx.xx
>>> ==================================
>>> .. and after a restart everything works fine.
>>>
>>> Kent J.
>>
>> I suspect you have a dud network adapter, as you already suggested
>> at the beginning. Try a different adapter.
>
> Well, I thought that first.
> But: "The Security System detected an authentication error for
> DNS/dns1.MyDNS.se....There are currently no logon servers available"
> ...doesn't that tell the problem is outside MyServer?
>
> Kent J.
Don't know. If this was my machine then I would check Google
to see what exactly causes this message to appear. I suspect
the message is the ***result*** of a network failure, not its cause.