Re: Preparing network connection after AD install
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Sat, 2 Dec 2006 02:25:19 -0000
Hi
Can you tell us more about your actual network configuration, DCs, local DNS.
When you say that you installed active directory on your win2k3 machine because it's required by exchange, are you saying that your Exchange is also a DC?
Assuming DNS AD Integrated Zone
-Make sure that each DNS server points to itself under NIC preferred DNS. If the Server IP-Address is 192.168.0.1 then the preferred DNS should also be 192.168.0.1.
-Clients (workstations and member servers): Make sure that the clients only use their local available DNS server(s) on their NIC DNS configuration. Do not place the ISP DNS server or any other DNS on the client or DNS Server NIC properties, this is a common mistake. The clients should use their local DNS server to resolve all queries. It's up to the local DNS server to handle the Internet resolution as any other Zone that the DNS is not authoritative for. Check the link for configuring DNS for Internet resolution.
Note: The DNS client does not utilize each of the DNS servers listed in TCP/IP configuration for each query. By default, on startup the DNS client will attempt to utilize the server in the Preferred DNS server entry. If this server FAILS to respond for any reason, the DNS client will switch to the server listed in the alternate DNS server entry. The DNS client will continue to use this alternate DNS server.
Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/kb/825036/en-us
How to configure DNS for Internet access in Windows Server 2003
http://support.microsoft.com/kb/323380/
--
*************************************************
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA + Exchange + MSCE
*************************************************
"Bob" <msgdev@xxxxxxxxxxx> wrote in message news:%23CIM%23DYFHHA.4588@xxxxxxxxxxxxxxxxxxxxxxx
I installed active directory on my win2k3 machine because it's required by exchange. Now after the install the system gets to preparing network connections and no further. I waited over night just to see if it would hit some timeout but nothing.
From other suggestions I have herd I set my primary dns server to piont to its own IP. Im not sure what to set the second IP to. I was told not to use my ISPs dns server (which didn't make a difference) so it just set to a bogus ip. I also disabled all my virus scanning software.
The only way I can log on is in safe mode Directory services repair mode or safe mode no networking. I tried to run dcpromo to just remove it in safe mode and it says it can't be run in safe mode. Can anyone suggest what I can do to get this computer back online?
Bob
.
- Follow-Ups:
- Re: Preparing network connection after AD install
- From: Bob Bins
- Re: Preparing network connection after AD install
- References:
- Prev by Date: Re: Can't find cached credentials (or Interactive logon)
- Next by Date: SID Filtering
- Previous by thread: Preparing network connection after AD install
- Next by thread: Re: Preparing network connection after AD install
- Index(es):
Relevant Pages
|
