Multiple AD Servers (different domains) on a single subnet

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Dave Weber (david.weber_at_backbonesecurity.com)
Date: 10/07/04 

Date: Thu, 7 Oct 2004 13:59:52 -0400

I'm in the process of architecting a switch from one domain to another (long
story, don't want to get into the why's).

So, I have the new server set up, and I'm attempting to add systems to the
new AD server. It craps out (bad username/password when trying to assign
the system via "My Computer").

So, I create a separate network from the "production" server, and try to add
the system again. This time it works. So, obviously, the current server is
interfering w/ the registration w/ the New server.

Do I have any other options other than setting up a whole separate subnet
for the new server?

BTW, the two domains don't trust each other, and basically I don't want them
to know anything about each other. I want to be able to start fresh anew.
FYI

Thanks..

Relevant Pages

  • Guest access to printer
    ... I have set up a separate network for visitors when they ... gives out DHCP addresses so that visitors can access the ... server, ... to the shared printer they get the message "Access is ...
    (microsoft.public.win2000.printing)
  • RE: firewall test
    ... > bounces@xxxxxxxxxx] On Behalf Of Robert Williams ... > I have a server firewall we developed using RHL Fedora Core 3. ... Our workstations are on a separate network, ...
    (RedHat)
  • Re: Upgrading from exchange 2003 to 2007
    ... setup fine, can have roles on one server. ... exchange 2007 server which we would install in a separate network. ...
    (microsoft.public.exchange.admin)
  • Re: Remote events in NAT enviroment
    ... Did you try with WCF? ... I try to implement a server that should fire events to clients placed on a ... separate network than the server and use NAT. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Remote events in NAT enviroment
    ... I try to implement a server that should fire events to clients placed on a ... separate network than the server and use NAT. ...
    (microsoft.public.dotnet.framework.remoting)