Re: Floating Computer between domains

When you say two different networks, do you mean physically disconnected? I.E. The forests cannot communicate with each other? If they are connected and can communicate, then you can set up a trust. If not you are in a bit of a spot. Assuming the latter, I would set this up by running Virtual PC or VMWare workstation on the laptop. Then I would load another copy of the OS in a guest VM and that would be used for talking to one domain. The main laptop would be used for talking to another domain.

I do something like this for work only the laptop itself isn't in any domain, I run VPC and any customers I deal with that I need to work on their network, I set up a VM for each of them and I use that VM exclusively when working on their stuff. I also have a VM for talking to my company network I work for.

joe

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm


JoshG wrote:
Hi All,

In an earlier thread I asked about the ability to take a computer out
of a domain for a long period of time and return it without any
hastles.

Now I'm trying to work out if I can have Two Domains... like this...

Domain A:
DC
DBSVR
COMMSSVR
WORKSTATION

Domain B:
DC
DBSVR
COMMSSVR

Both of these domains need to be on completely different networks
(otherwise the DBSvrs and the Comms servers would interfer)

I need the workstation machine to be able to float between the two
domains (at the flick of a switch)
What are the issues involved in getting this to work at a domain level?

Would the two domain controllers need to be connected externally in
order to form a trust?

Also, What issues could you forsee from a DNS/ARP point of view, Would
the Workstation be confused as the HostNames are the same as before but
different on the new subnet? Should I keep all the IP addressing the
same to solve this, but then would the ARP be confused about mac
addresses?

The main motivation behind this architecture is to be able to switch
the workstation to operate on a development network as opposed to a
production one.

Thoughts Anyone?
Thanks

Josh

.

Relevant Pages

  • Re: For the AdaOS folks
    ... Mach's concept of thread migration seems inappropriate. ... Since priorities must be enforced by the AdaOS kernel at all times (to ... could be on any workstation in the network. ...
    (comp.lang.ada)
  • Need help with XP Home edition networkin workgroup
    ... I'm trying to set up a small home network with a workstation and a laptop, ... The problem is that I can access the "shared documents" folder on the laptop ...
    (microsoft.public.windowsxp.help_and_support)
  • RE: Routing oddity on domain.
    ... The client workstation 's gateway should be the Router internal IP address ... >I. Please check DNS and Gateway settings. ... >II Please ensure proper binding order of the network adapter cards. ... Click Internet Protocl, and then click Properties. ...
    (microsoft.public.windows.server.sbs)
  • Wireless networking problem with user accounts
    ... My home network involves a laptop and a PC workstation masquerading as ... Restricted accounts can open the software the ...
    (microsoft.public.windowsxp.security_admin)
  • Sudden Network Problem Accessing Home Network
    ... Dell laptop communicating to the hub via a wireless connection. ... system network operating successfully until ....... ... Had to disable consecutively each monitor in the desktop dual monitor ... The desktop will communicate with the laptop. ...
    (microsoft.public.windowsxp.security_admin)