Re: Preparing network connection after AD install

Thank you for the suggestions.

I didn't install exchange yet. The only thing I did was run dcpromo. After
that I restarted and could not log in. I get preparing network connections
infinitely. No errors in the event log or anything else to help me.

It is a test machine but I have every debugger and debugging tool known to
man installed on that machine and it would take an entire week to put
everything back on.

For now I removed active directory it using the registry trick I found on
another site. I am just going to install Virtual Server and go fresh with a
new install of both win 2k3 server and exchange. That way It will be a lot
easier to start over if I have problems.





"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:eoGlL0kFHHA.4464@xxxxxxxxxxxxxxxxxxxxxxx
Inline
Basically there are no clients. Its a stand alone win2k3 machine. The
only reason I installed active directory is because when I tried to
install exchnage on that machine it told me it was required. So I just
want the minimal required to run exchange. There are no tree's forests
or any other wildlife.
You must have at least 1 Forest, 1domain tree, 1domain, 1GC. That's the
minimum requirements to install exchange.
Tell me is that machine a test machine?
If yes, do it all from start again, and make sure before you install
Exchange that everything is working Ok in that DC, run the suggested cmds
(dcdiag and netdiag) before running exchange setup.
What is your real gold with an Exchange installed in a DC?
Does your hardware box meet the minimum requirements?
Slow startups, slow shutdowns, services failing to start, etc... Are all
known symptoms of having exchange installed on DC and bad DNS
configuration.
Have a look at these articles:
http://www.petri.co.il/how_to_install_active_directory_on_windows_2003.htm
http://www.microsoft.com/technet/prodtechnol/exchange/2003/sysreqs.mspx
http://www.microsoft.com/technet/prodtechnol/exchange/Guides/Ex2k3DepGuide/a3318f57-3536-4e65-9309-9300cda23c73.mspx?mfr=true

--
*************************************************
I hope that the information above helps you
Good Luck

Jorge Silva

MCSA + Exchange + MSCE
*************************************************

"Bob Bins" <msgdev@xxxxxxxxxxx> wrote in message
news:eEBB1XhFHHA.3304@xxxxxxxxxxxxxxxxxxxxxxx
Basically there are no clients. Its a stand alone win2k3 machine. The
only reason I installed active directory is because when I tried to
install exchnage on that machine it told me it was required. So I just
want the minimal required to run exchange. There are no tree's forests
or any other wildlife.

My win2k3 machine which I want to install exchange on thus am installing
active directory on has its local IP set to 10.10.10.28. That is also
what the DNS setting is set to. The secondary entry is left empty.

I had DNS installed on that machine prior is there some zone or lookup
that could be causing a problem?




"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:%23wVMykbFHHA.3616@xxxxxxxxxxxxxxxxxxxxxxx
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







.

Relevant Pages

  • Re: Preparing network connection after AD install
    ... only reason I installed active directory is because when I tried to install exchnage on that machine it told me it was required. ... So I just want the minimal required to run exchange. ... Are all known symptoms of having exchange installed on DC and bad DNS configuration. ... Do not place the ISP DNS server or any other DNS on the client or DNS Server NIC properties, ...
    (microsoft.public.windows.server.active_directory)
  • Re: E2K3 SP2 + IMF -> SMTP Outbound reports errors if no smart host is set
    ... the mail could queue at the smarthost server. ... > install IMF v1 after you have installed SP2, your IMF may break and yes, I ... >> I have an Exchange 2003 server running SP2. ... >> 2) I've manually walked the DNS queries that Exchange should be executing ...
    (microsoft.public.exchange.connectivity)
  • Re: AD/DNS/DHCP - Upgrading Windows 2000 to Windows 2003
    ... Exchange is a member now and in total we got 2 DCs. ... exchange ios on a DC to install it on a member server? ... On the old server open DNS management console and check that you ... Install the new machine as a member server in your existing ...
    (microsoft.public.windows.server.migration)
  • Re: AD/DNS/DHCP - Upgrading Windows 2000 to Windows 2003
    ... Exchange is a member now and in total we got 2 DCs. ... exchange ios on a DC to install it on a member server? ... On the old server open DNS management console and check that you ... Install the new machine as a member server in your existing ...
    (microsoft.public.windows.server.migration)
  • Re: Exchange 2003 installation
    ... As suggested I had created a forwarder to my ISP in my DNS server. ... List of NetBt transports currently bound to the Redir ... what is about the old exchange installation. ...
    (microsoft.public.win2000.active_directory)