Re: Can't find DC

Thanks Miha,

Yes it is a member of a Win2000 domain
PC gets DNS from DHCP; it points to our ISP's DNS servers.

Event log entries follow:

In the Server System Event Log

Source: NETLOGON
Dynamic registration or deregistration of one or more DNS records
failed because no DNS servers are available.

In the Workstation System Event Log

Source: NETLOGON
No Domain Controller is available for domain FLATPLATE due to the
following:
There are currently no logon servers available to service the
logon request. .
Make sure that the computer is connected to the network and try
again. If the problem persists, please contact your domain
administrator.

I also took Joshua's advice and switched the NIC from Auto to 100/full
duplex so as not to get tripped up over the negotiation.

I hope these log entries mean more to you than they do to me.

Thanks,
-- Carlos --

"Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
news:OWE2JUNrFHA.240@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> few questions and things to look at.
>
> If I understand this PC is member of Windows 2000 domain? How is DNS set
up
> on client PC? Where does DNS point to?
> Are there any errors or other events that might explain what is going on
in
> Event log (specially in System and Application logs). You should also
check
> the logs on domain controller.
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "CarlosAntenna" <nunayo@xxxxxxxxxx> wrote in message
> news:euZrd$MrFHA.2768@xxxxxxxxxxxxxxxxxxxxxxx
> >I have a network with only one server and about 25 workstations. All
> > workstations connect to a shared network drive for data and some
> > applications (drive S:). One of the newest workstations loses
> > communication with the S: drive nearly every day, but not the same time,
> > and
> > not tied to any event that can be replicated. I tried disconnecting the
> > mapped S: drive and then reconnecting. It says it cannot find the DC to
> > verify my login to the S: drive. But, I can PING the IP of the DC.
> > Rebooting the PC is the only fix. What is causing this???
> >
> > Win 2000 Server, sp4 fully patched
> > Win XP, sp2 fully patched
> >
> > And wouldn't you know it... It's the president's machine that is doing
> > this.
> > He leaves everything open on his desktop. Multiple documents in several
> > different applications. When he has to reboot, he whines and complains
> > that
> > it is going to take him hours to get back to where he was. And I'm the
> > guy
> > who has to listen to it.
> >
> > -- Carlos --
> >
> >
>
>


.

Relevant Pages

  • Re: Very Slow(60mins) XP logon
    ... The DNS on the servers is set to internal only, workstations get their dns through dhcp which also sets them up for internal dns. ... The slow logon happens with any AD account. ...
    (microsoft.public.win2000.networking)
  • Re: Random client slow Internet browsing
    ... Are you sure the workstations are free from malware? ... I am pointing to the parent company DNS servers, ... SBS 2003 Premium ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS problems
    ... the forwarders are in place and are correct for the ISP DNS servers ... the workstations as the only DNS server. ... Ethernet adapter Local Area Connection 2: ...
    (microsoft.public.windows.server.sbs)
  • Re: Group policy issue.......
    ... Check your DNS setup. ... Your workstations and member servers should be ... pointing only to your internal DNS servers. ... > I'm getting the following errors logged on my workstations in an AD ...
    (microsoft.public.win2000.group_policy)
  • Re: Problems with second DC (failover) when primary DC is offline.
    ... I believe what that is saying is DCDIAG detects an error in the event log, ... They are both set up with DHCP, DNS, WINS, they are both GC. ... >>> are being distributed by DHCP as DNS and WINS servers. ...
    (microsoft.public.windows.server.active_directory)
Loading