Need expert diagnosis (is there a doctor in the house?)

From: Ric (anonymous_at_discussions.microsoft.com)
Date: 03/09/04 

Date: Tue, 9 Mar 2004 06:54:04 -0800

HI,

I've recently ran into a bit of a snag with my Domain
controller.

Here's what I'm using:

Windows 2003 Server (acts as a AD Domain Controler, DNS
server, file server)
Most clients are running Win XP except 1 win98 and 1 NT
4.0 wkstn.

Yesterday, 10 out of 35 people couldn't log into the
domain . They would get an error message saying that the
Domian controller could not be found.

Friday, I was monkey-ing around with trying to setup VPN
access to the server by enabling the servers 2nd NIC
(actually, it was enabled but not connected to the
network. I gave it a static ip on the same segment as the
rest of our network and connected it, then ran the Remote
Access wizard )and this is what I think created the
problem.

I have since disconnected the 2nd nic and disabled Remote
Access. This seemed to solve the problem for all Win XP
clients BUT: THe win 98 and NT4.0 machines still can't
find the domain controller. I switched the nt4.0 computer
from our domain to a workgroup (using the same name for
the workgroup as the domain) and then tried to rejoin the
domain but the computer can't find the DC.

I've checked all IP/subnet masks and all are correct.
I can ping all computers and the DC by both IP and by
their netbios Name so DNS is working.

There's more:
If you browse the network through network neighborhood on
a client computer, the domain controller is no longer
listed. Even more strange, if I browse the network through
network neighborhood on the DC, NO COMPUTERS ARE LISTED!!
I think then that maybe it is the workgroup NOT the domain
that may be showing up in network neighborhood?

Is this a master browser problem (and how exactly do I fix
it?)

I need an experts opinon (and diagnosis)!!!

Thanks,

Ric

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... One thought, when you introduced the Windows Server 2008 and before making them DC's, did you extend the schema on the SBS 2003 server? ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Random Network Disconnects
    ... network and the only way I can seem to get it back up is to restart the box. ... Testing IpConfig - pinging the Secondary WINS server... ... DNS Host Name: itdspstest01.itd.edited.edited ... Provider Version:2 ...
    (microsoft.public.windows.server.dns)