Check your DNS settings. AD uses your internal DNS server to locate all internal resources, DC's, DHCP, Client's, etc... Your DNS setting on your DC should point to your INTERNAL DNS server. If the DC is the DNS server then it should point to itself. Then in the forwarders tab of your DNS server properties, you enter the DNS server's from your ISP.
So then all internal request's are resolved first and then all requests that are not internal are forwarded i.e. websites, etc... HTH, Bacardi K. Bryant, MCP Assistant Manager of Technology Kinko's, Inc. [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Salvatore Palmisano Sent: Tuesday, June 18, 2002 9:59 AM To: NT 2000 Discussions Subject: DC Issue Every two hours I'm getting this event log error on the AD DC on our small network. There are two member servers, one DC, and several workstations. **error text** Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5719 Date: 6/18/2002 Time: 9:50:04 AM User: N/A Computer: MACHINENAME Description: No Windows NT or Windows 2000 Domain Controller is available for domain DOMAINNAME. The following error occurred: There are currently no logon servers available to service the logon request. Data: 0000: 5e 00 00 c0 ^..� **/error text** Why would I get this on the DC itself? There are no ill effects across the network we know of. All accessability is accounted for (applications, printers, files, et cetera). Where can I begin to research this? .salvatore ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
