Sounds like its not replicating. When you say non-domain firewall, what do you mean? You don’t want any firewall on it… unless you have a specific need.

 

If you strip the firewall off, where does that leave you?

 

If you use dcdiag and netdiag they should also give you an idea about what’s going on. If you like, feel free to mail them to me.

 

Cheers,

 

Rob

 

 

Robert Rutherford
QuoStar Solutions Limited
 

The Enterprise Pavilion
Fern Barrow
Wallisdown
Poole
Dorset
BH12 5HH
 

 

T:

+44 (0) 8456 440 331

F:

+44 (0) 8456 440 332

M:

+44 (0) 7974 249 494

E:

[EMAIL PROTECTED]

W:

www.quostar.com

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger
Sent: 28 July 2006 07:20
To: [email protected]
Subject: [ActiveDir] DC Can't Handle DNS Pointed to Self

 

Hello:

 

This is sort of a follow up to two recent postings. Any thoughts are welcome as I have now been trying to figure this one out for about a week.

 

I have DC running as a virtual machine under (host W2k3 SP1 w/ VS 2005 R2; guest: W2k3 ENT R2). This machine was recently promoted. When its local DNS points to itself, the machine does not logon to the domain. It appears to not even know about itself. No one can get to it because it loads the non-domain firewall GPO (enabling the full firewall).

 

When I point DNS across the WAN, it loads – though interestingly it does not become visible on the network until I log into it (via the VS management tools). I can then log out and it stays visible. It then appears to function correctly.

 

Any thoughts greatly appreciated.

 

-- nme


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.4/399 - Release Date: 7/25/2006

Reply via email to