Re: DC doesn't know it's own domain name
From: Mark Renoden [MSFT] (markreno_at_online.microsoft.com)
Date: 09/01/04
- Next message: Mark Renoden [MSFT]: "Re: Need help with DNS design and settings"
- Previous message: dan: "DC doesn't know it's own domain name"
- In reply to: dan: "DC doesn't know it's own domain name"
- Next in thread: dan: "Re: DC doesn't know it's own domain name"
- Reply: dan: "Re: DC doesn't know it's own domain name"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 1 Sep 2004 10:09:28 +1000
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. >
- Next message: Mark Renoden [MSFT]: "Re: Need help with DNS design and settings"
- Previous message: dan: "DC doesn't know it's own domain name"
- In reply to: dan: "DC doesn't know it's own domain name"
- Next in thread: dan: "Re: DC doesn't know it's own domain name"
- Reply: dan: "Re: DC doesn't know it's own domain name"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
