Lost Network Access to Netlogon

  • Thread starter Thread starter Jim Buyens
  • Start date Start date
J

Jim Buyens

I have a small network consisting of:

a. A Windows 2000 Server acting as Domain Controller,
which I upgraded some time ago from an NT4 PDC.
b. A Windows 2000 member server.
c. A Windows 2003 member server.
d. Two Windows XP Pro workstations.
e. A laptop running Windows XP Tablet, connected through
a wireless access point.
f. A Linksys NAT box connected to a cable modem. This is
also an 8-port wiring hub.

A couple of days ago all the lights in the building
flickered and something blew out three network adapters:
one each in machines a, b, and f.

I replaced the Linksys NAT box and the NIC in machine b.
Machine a, however, had two network adapters already, only
one of which I was using. So:

1. I moved the network cable to the previously unused
adapter.
2. Configured it to respond to all the same IP addresses
that the failed NIS used to service.
3. Removed TCP/IP from the failed NIC and disabled it in
Network And Dial-Up Connections.

At this point I could ping and browse Web sites from the
server, but other machines on the network weren't getting
DNS or Netlogon.

I fixed DNS by going to Network And Dial-Up Connections,
Advanced, Advanced Settings, Adapters And Bindings, and
then making the previously unused (but now active) NIC the
first one in the list. However, the other machines still
weren't getting Netlogon.

Next, I physically removed the failed NIC and rebooted.
Plug And Play took the old NIC out of Network And Dial-Up
Connections, but the the other machines still aren't
aren't getting Netlogon.

WINS seems to be OK. Viewing registrations directly on the
server shows dates and times only a few minutes old.

Domain logins on the workstations are still partially
working, but logon scripts don't get run, so I think the
workstations are using cached credentials.

net use u: /home fails because the home directory for the
current user can't be determined.

I can map u: to \\server\myhome if I specify the username
as (e-mail address removed), but not if I use the form domain\user.

Do I have to specifically bind the Netlogon service to the
new adapter somehow? If so, how?

Jim Buyens
 
You should not need to anything special to the network adapter. Just make sure that
Client for Microsoft Networks and file and print sharing is installed and enabled for
tcp/ip for that adapter and that the workstation and server service are running. Look
in Event Viewer for any pertinent errors. Of course the tcp/ip address needs to be on
the correct subnet.

Then make sure that the other computers know how to find your domain controller. If
the tcp/ip address of it as shown with ipconfig /all has changed then the other
computers need to be configured which would involve changing their tcp/ip info if
statically configured or changing the DHCP scope to reflect changes to dns and wins.
First make sure that the domain controller is pointing to itself by it's static IP
address as it's preferred dns server. I assume that the W2K domain controller is
doing DHCP for the domain and not the router which would be a bad idea and can cause
lots of problems. I would also run first netdiag /v and then dcdiag /v on the domain
controller looking for failed tests that may indicate a problem and what the problem
is. Running netdiag on a domain member would also be a good idea. It is possible your
dns _srv records are not correct since you made the changes. It would be a good idea
to run netdiag /fix on it and then restart netlogon service on the domain controller
after making sure it is correctly configured. -- Steve


http://support.microsoft.com/default.aspx?scid=kb;en-us;321708 -- about netdiag.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;301423 -- how to install
support tools such as netdiag and dcdiag, you must use correct operating system disk.
 
Thanks for your suggestions. I'll give them a try this
evening.

Jim Buyens

-----Original Message-----
You should not need to anything special to the network adapter. Just make sure that
Client for Microsoft Networks and file and print sharing is installed and enabled for
tcp/ip for that adapter and that the workstation and
Click to expand...
server service are running. Look
in Event Viewer for any pertinent errors. Of course the tcp/ip address needs to be on
the correct subnet.

Then make sure that the other computers know how to find your domain controller. If
the tcp/ip address of it as shown with ipconfig /all has changed then the other
computers need to be configured which would involve changing their tcp/ip info if
statically configured or changing the DHCP scope to
Click to expand...
reflect changes to dns and wins.
First make sure that the domain controller is pointing to itself by it's static IP
address as it's preferred dns server. I assume that the W2K domain controller is
doing DHCP for the domain and not the router which would be a bad idea and can cause
lots of problems. I would also run first netdiag /v and then dcdiag /v on the domain
controller looking for failed tests that may indicate a problem and what the problem
is. Running netdiag on a domain member would also be a good idea. It is possible your
dns _srv records are not correct since you made the
Click to expand...
changes. It would be a good idea
to run netdiag /fix on it and then restart netlogon
Click to expand...
service on the domain controller
 
Thanks; this let to a solution.

Netdiag reported a number of fatal errors involving NETBT not being
available, and I eventually tracked that to Disable NetBIOS Over
TCP/IP being checked in teh adapter's TCP/IP Properties, Advanced,
WINS tab. Duh. I have no idea how that got set, except maybe long ago
when there was no network cable on that adapter.

Thanks again for your help.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
 
Hi Jim.

Great that you got it fixed and thanks for reporting back what it was and how you
found it.

Steve
MVP Windows Security
 
Hi Jim,

Its a long shot, but I might try opening AD Users and Computers. Expand to
get into the Computer folder. Right click the computer, and reset.

I'm not sure what Server uses to ID a machine - but if its dynamically based
on a MAC address, this could be a problem.

Jeff
 
Back
Top