Problem with DC browsing another DC...

[NewMan]

We have a small network with 4 x Win2000 Servers using Active
Directory. All servers have been promoted to be Domain Controllers.

I just built the last box to replace one of the older servers, and I
have a problem with it. It wont browse into one of the other servers
on the network - and - the same server cannot browse into the new
server!

Both of these servers can browse to all of the other servers on the
LAN.

Here is some info from the new box:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : VPN-Server
Primary DNS Suffix . . . . . . . : xx.yyy.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : xx.yyy.com
yyy.com

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 GT
Desktop Adapter

Physical Address. . . . . . . . . : 00-0E-0C-74-9B-13
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.9
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.9
Primary WINS Server . . . . . . . : 192.168.1.6
Secondary WINS Server . . . . . . : 192.168.1.3


DCDIAG:

Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... VPN-SERVER passed test frssysvol

NETDIAG

When I run this, all I get is a line of dots

.................................................

and it hangs. I let it sit for 4 hours - no change.

<sigh>

What the HECK is going on!

All assistance greatly appreciated!

 

[Meinolf Weber]

Hello NewMan,

I would also configure the DC to use an additional DNS server, if itself
fails. Also post an ipconfig /all from all other DC'DNS machines.

Check out this one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;275278&id=kb;en-us;275278

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

[NewMan]

After considerable screwing around....

I gave up!

I took a spanking new hard disk (absolutely clean!) and did a complete
bare-metal rebuild of the Win2000 Server O/S.

Now working like a charm! No browsing or integration problems at all.

I will say this, on the first (and FAILED) attempt, I did all the
patches, updates, and installs BEFORE I promoted the box to be a
domain controller.

THIS TIME (WORKS!) The only thing I "installed" was the driver for the
NIC so that I could talk to the network.

I then set the static IP address for the box and pointed the DNS at
the FSMO role holder for the domain which is also the main DNS server.

I then joined the domain, rebooted, and ran DCPROMO.

AFTER integration into the Active Directory, THEN I ran ALL patches,
updates, installs and VON config - and I tested it EVERY step of the
way (JUST IN CASE).

Like I said, worked like a charm (this time).

And with all that said, it took me much less time to rebuild the box
than to try and troubleshoot it!

<sigh>

And because I still had the old had drive, I rebooted the box with the
old drive and then demoted the old server, then removed it from the
domain - just as a clean-up.

All's well that ends well.