dcdiag - advertising errors on newley promoted domain controller

Hi there, a newly promotoed win2k domain controller (which is a virtual
machine running under virtual server 2005 sp1. This is the second time I've
promoted the server and the second time I am receiving these errors.

Any ideas anyone?

Starting test: Advertising
Warning: DsGetDcName returned information for \\server1.domainname.com
when we were trying to reach server2.
Server is not responding or is not considered suitable.
The DC server2 is advertising itself as a DC and having a DS.
The DC server2 is advertising as an LDAP server
The DC server2 is advertising as having a writeable directory
The DC server2 is advertising as a Key Distribution Center
The DC server2 is advertising as a time server
......................... server2 failed test Advertising

I'm at a loss, no SYSVOL shares are showing and this is the only test that
DCDIAG fails on.

Thanks.

Hello Andrew,

Please post an unedited ipconfig /all from both DC's.

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


> Hi there, a newly promotoed win2k domain controller (which is a
> virtual machine running under virtual server 2005 sp1. This is the
> second time I've promoted the server and the second time I am
> receiving these errors.
>
> Any ideas anyone?
>
> Starting test: Advertising
> Warning: DsGetDcName returned information for
> \\server1.domainname.com
> when we were trying to reach server2.
> Server is not responding or is not considered suitable.
> The DC server2 is advertising itself as a DC and having a DS.
> The DC server2 is advertising as an LDAP server
> The DC server2 is advertising as having a writeable directory
> The DC server2 is advertising as a Key Distribution Center
> The DC server2 is advertising as a time server
> ......................... server2 failed test Advertising
> I'm at a loss, no SYSVOL shares are showing and this is the only test
> that DCDIAG fails on.
>
> Thanks.
>

Hi,

Server1

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server1
Primary DNS Suffix . . . . . . . : domainname.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domainname.com

Ethernet adapter Team:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : BASP Virtual Adapter
Physical Address. . . . . . . . . : 00-06-5B-FD-E6-64
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.1.1
10.0.33.99
Primary WINS Server . . . . . . . : 10.0.1.1
Secondary WINS Server . . . . . . : 10.0.33.99


Server2

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server2
Primary DNS Suffix . . . . . . . : domainname.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domainname.com

Ethernet adapter LAN1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21140 Based PCI Fast
Ethernet
Adapter
Physical Address. . . . . . . . . : 00-03-FF-FE-56-2F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.2
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.1.2
10.0.33.99
Primary WINS Server . . . . . . . : 10.0.1.1
Secondary WINS Server . . . . . . : 10.0.33.99

Hello Andrew,

Is 10.0.33.99 also domain controller? What kind of zones do you use, AD integrated?
Please post a complete dcdiag /v output from both DC's. Also from repadmin

Hello,

10.0.33.99 is our UHB domain controller at head office.

We use only AD integrated zones.

Are you using AD integrated dns? Because each server you are showing has
itself as the primary dns and your secondary dns is some unknown server you
haven't defined. What is the .33 server?

You also are using server1 as a router, is this intentional?