Hi,

Is it possible to put two NICs in a client machine and make it a member of
two completely separate AD domains simulatenously so that it can access both
networks w/o rebooting?

Example
NIC #1: IP: 10.0.0.1, Domain: abc.com
NIC #1: IP: 10.10.0.1 Domain: xyz.com

Sam

Correction:

NIC #1: IP: 10.0.0.1, Domain: abc.com
NIC #2: IP: 10.10.0.1 Domain: xyz.com

By mistake, I defined both network cards as NIC #1

Sam

"Sam" <(E-Mail Removed)> wrote in message
news:u6C%(E-Mail Removed)...
> Hi,
>
> Is it possible to put two NICs in a client machine and make it a member of
> two completely separate AD domains simulatenously so that it can access
both
> networks w/o rebooting?
>
> Example
> NIC #1: IP: 10.0.0.1, Domain: abc.com
> NIC #1: IP: 10.10.0.1 Domain: xyz.com
>
> Sam
>
>

No. A computer can belong to only one domain/workgroup at a time.

Sam wrote:
> Hi,
>
> Is it possible to put two NICs in a client machine and make it a
> member of two completely separate AD domains simulatenously so that
> it can access both networks w/o rebooting?
>
> Example
> NIC #1: IP: 10.0.0.1, Domain: abc.com
> NIC #1: IP: 10.10.0.1 Domain: xyz.com
>
> Sam

True. But with MultiNetworkManager from www.globesoft.com you can join that
computer to several domains/workgroups. It is easy to switch to another
domain and it will reboot your computer and apply the necessary settings.

--
Regards,

Marina
Microsoft SBS-MVP

"Lanwench [MVP - Exchange]"
<(E-Mail Removed)> schreef in
bericht news:(E-Mail Removed)...
> No. A computer can belong to only one domain/workgroup at a time.
>
> Sam wrote:
> > Hi,
> >
> > Is it possible to put two NICs in a client machine and make it a
> > member of two completely separate AD domains simulatenously so that
> > it can access both networks w/o rebooting?
> >
> > Example
> > NIC #1: IP: 10.0.0.1, Domain: abc.com
> > NIC #1: IP: 10.10.0.1 Domain: xyz.com
> >
> > Sam
>
>

Yes, true - I've never used it nor known anyone who has, though, so I don't
generally recommend/mention it. I'm a big fan of keeping things as simple as
possible...and it's so easy just to map a drive!

Marina Roos [SBS-MVP] wrote:
> True. But with MultiNetworkManager from www.globesoft.com you can
> join that computer to several domains/workgroups. It is easy to
> switch to another domain and it will reboot your computer and apply
> the necessary settings.
>
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed)> schreef in
> bericht news:(E-Mail Removed)...
>> No. A computer can belong to only one domain/workgroup at a time.
>>
>> Sam wrote:
>>> Hi,
>>>
>>> Is it possible to put two NICs in a client machine and make it a
>>> member of two completely separate AD domains simulatenously so that
>>> it can access both networks w/o rebooting?
>>>
>>> Example
>>> NIC #1: IP: 10.0.0.1, Domain: abc.com
>>> NIC #1: IP: 10.10.0.1 Domain: xyz.com
>>>
>>> Sam

You know me! And I'm using it for quite some time now. I have several
clients all with their own domain, so it is a big help not having to set all
those things manually, but let MultiNetworkManager do it. It also enables me
to have all my emailboxes offline.

--
Regards,

Marina
Microsoft SBS-MVP

"Lanwench [MVP - Exchange]"
<(E-Mail Removed)> schreef in
bericht news:(E-Mail Removed)...
> Yes, true - I've never used it nor known anyone who has, though, so I
don't
> generally recommend/mention it. I'm a big fan of keeping things as simple
as
> possible...and it's so easy just to map a drive!
>
> Marina Roos [SBS-MVP] wrote:
> > True. But with MultiNetworkManager from www.globesoft.com you can
> > join that computer to several domains/workgroups. It is easy to
> > switch to another domain and it will reboot your computer and apply
> > the necessary settings.
> >
> >
> > "Lanwench [MVP - Exchange]"
> > <(E-Mail Removed)> schreef in
> > bericht news:(E-Mail Removed)...
> >> No. A computer can belong to only one domain/workgroup at a time.
> >>
> >> Sam wrote:
> >>> Hi,
> >>>
> >>> Is it possible to put two NICs in a client machine and make it a
> >>> member of two completely separate AD domains simulatenously so that
> >>> it can access both networks w/o rebooting?
> >>>
> >>> Example
> >>> NIC #1: IP: 10.0.0.1, Domain: abc.com
> >>> NIC #1: IP: 10.10.0.1 Domain: xyz.com
> >>>
> >>> Sam
>
>

Good to know - thanks for the informal product review. :-)

Marina Roos [SBS-MVP] wrote:
> You know me! And I'm using it for quite some time now. I have several
> clients all with their own domain, so it is a big help not having to
> set all those things manually, but let MultiNetworkManager do it. It
> also enables me to have all my emailboxes offline.
>
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed)> schreef in
> bericht news:(E-Mail Removed)...
>> Yes, true - I've never used it nor known anyone who has, though, so
>> I don't generally recommend/mention it. I'm a big fan of keeping
>> things as simple as possible...and it's so easy just to map a drive!
>>
>> Marina Roos [SBS-MVP] wrote:
>>> True. But with MultiNetworkManager from www.globesoft.com you can
>>> join that computer to several domains/workgroups. It is easy to
>>> switch to another domain and it will reboot your computer and apply
>>> the necessary settings.
>>>
>>>
>>> "Lanwench [MVP - Exchange]"
>>> <(E-Mail Removed)> schreef
>>> in bericht news:(E-Mail Removed)...
>>>> No. A computer can belong to only one domain/workgroup at a time.
>>>>
>>>> Sam wrote:
>>>>> Hi,
>>>>>
>>>>> Is it possible to put two NICs in a client machine and make it a
>>>>> member of two completely separate AD domains simulatenously so
>>>>> that it can access both networks w/o rebooting?
>>>>>
>>>>> Example
>>>>> NIC #1: IP: 10.0.0.1, Domain: abc.com
>>>>> NIC #1: IP: 10.10.0.1 Domain: xyz.com
>>>>>
>>>>> Sam