Archived from groups: microsoft.public.win2000.dns (
More info?)
In news:090d01c4902a$3fb6fe80$a401280a@phx.gbl,
dan <anonymous@discussions.microsoft.com> made a post then I commented below
>> -----Original Message-----
>> Hi Dan
>>
>> Seems a bit of a non-specific error. I'd suggest this is a general
>> network/DNS issue that's manifesting itself in this way. Suggestions:
>>
>> 1. Make sure that the DC points to itself for DNS, there's no
>> alternate specified and if external name resolution is required, use
>> forwarders.
>>
>> 2. Make sure there's no firewall like software installed on this DC.
>>
>> 3. Try updating the NIC driver or replacing the NIC with one that
>> uses a different chipset.
>>
>> 4. Examine the event logs for DNS problems.
>>
>> 5. See whether the DC is reachable from the network when the issue
>> occurs. Ping name and IP.
>>
>> 6. Check to see whether there's any kind of power saving involved
>> with the NIC.
>>
>> Get the general idea?
This is the area I'd be looking at to
>> start with.
>>
>> Kind regards
>> --
>> Mark Renoden [MSFT]
>> Windows Platform Support Team
>> Email: markreno@online.microsoft.com
>>
>> Please note you'll need to strip ".online" from my email address to
>> email me; I'll post a response back to the group.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>>
>> "dan" <dan@integriguard.org> wrote in message
>> news:3b4b01c48f9b$77cad1a0$a601280a@phx.gbl...
>>> about every week or so my DC decides to forget who he is.
>>> I will come in the morning and have users complain that
>>> they can't print. My DC also serves as the print server.
>>> When this happens I try to log onto the server, only to
>>> wait about 30 minutes before logging on. But it doesn't
>>> log onto the domain, in fact on login the domain doesn't
>>> even appear in the options. If I reboot the machine it
>>> comes up fine for the next couple/few days at least. The
>>> only error I get in the Application Log is as follows:
>>>
>>> Source: Usernv
>>> Event ID: 1000
>>>
>>> Windows cannot obtain the domain controller name for your
>>> computer network. Return value (2146)
>>>
>>> It seems as though it can't resolve itself via DNS. Not
>>> sure.
>>>
>> I just noticed that about two minutes before i get the
> error mentioned above, I get a system log warning....
>
> Source: W32time
> Event ID: 63
>
> The time service cannot provide secure (signed) time to
> client 192.x.x.x because the attempt to validate its
> computer account failed.
>
> not sure if this is causing the problem or is a result of
> the problem. Any help would be appreciated.
That may be a symptom of the problem and is starting to confirm that it may
be a DNS misconfiguration.
Not sure if I missed your response in your post or not, but didn't seem to
see any replies on it, but did you confirm what Mark and I mentioned?
Tell you what, let's try to narrow it down for you. Could you please post:
1. An unedited ipconfig /all, the AD DNS domain name,
2. The zone name in DNS
3. If updates are allowed on the zone?
Like I said, these items can help us narrow this down. Otherwise, with
limited config info, its difficult to ascertain with any certainty.
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.
This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================