Users connecting in remote office

[Guest]

Have a remote overseas office that has a W2k3 workgroup. When users from our
USA W2k domain visit this overseas office, they cannot access local resources
with their US domain laptops. Have created username/password for them in
overseas workgroup. I believe the problem to be the VPN that connects remote
to US office allows their laptops to connect to domain in US which of cource
workgruop doesn't recognize. Before you tell me to create overseas domain
and trust the domains, thats not possible as there is some issue with the DNS
overseas that prevents domain formation. Is there some other way to make
this work? Cannot disable the VPN as that stops everyone in remote office
Outlook from running. I can't expect the travling users to log in to a
different profile everytime they are in overseas office. Is there some
workaround for this? Thanks

 

[Phillip Windell]

Have a remote overseas office that has a W2k3 workgroup. When users from our
USA W2k domain visit this overseas office, they cannot access local resources
with their US domain laptops. Have created username/password for them in
overseas workgroup. I believe the problem to be the VPN that connects remote
to US office allows their laptops to connect to domain in US which of cource
workgruop doesn't recognize.

The VPN isn't the problem and has nothing to do with it.

The laptops cannot function equally in two different network environments
unless they are reconfigured for the environment they exist in at the
particular moment. This is a problem becuase you cannot make them members of
the Workgroup without having to remove and then rejoin them to the Domain
afterwards.

I can't expect the travling users to log in to a different profile everytime they are in
overseas office.

There is no "other profile" for them to log into anyway. There is no way for
a machine to be part of a domain and part of a workgroup at the same time.
The closest you could come to that is rename the workgroup in the remote
office to match the name of the US Domain. That won't solve the situation,
but it would improve it.

Is there some workaround for this?

One possibility is Netswitcher (www.netswitcher.com)

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

 

[Randy]

Phillip Windell skrev:

Have a remote overseas office that has a W2k3 workgroup. When users from our
USA W2k domain visit this overseas office, they cannot access local resources
with their US domain laptops. Have created username/password for them in
overseas workgroup. I believe the problem to be the VPN that connects remote
to US office allows their laptops to connect to domain in US which of cource
workgruop doesn't recognize.

The VPN isn't the problem and has nothing to do with it.

The laptops cannot function equally in two different network environments
unless they are reconfigured for the environment they exist in at the
particular moment. This is a problem becuase you cannot make them members of
the Workgroup without having to remove and then rejoin them to the Domain
afterwards.

I can't expect the travling users to log in to a different profile everytime they are in
overseas office.

There is no "other profile" for them to log into anyway. There is no way for
a machine to be part of a domain and part of a workgroup at the same time.
The closest you could come to that is rename the workgroup in the remote
office to match the name of the US Domain. That won't solve the situation,
but it would improve it.

Is there some workaround for this?

One possibility is Netswitcher (www.netswitcher.com)

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

A more powerful suggestion is MultiNetwork Manager 7 from
www.globesoft.com
switch profiles with the push of a button at boot time.

 

[Randy]

Phillip Windell skrev:

Have a remote overseas office that has a W2k3 workgroup. When users from our
USA W2k domain visit this overseas office, they cannot access local resources
with their US domain laptops. Have created username/password for them in
overseas workgroup. I believe the problem to be the VPN that connects remote
to US office allows their laptops to connect to domain in US which of cource
workgruop doesn't recognize.

The VPN isn't the problem and has nothing to do with it.

The laptops cannot function equally in two different network environments
unless they are reconfigured for the environment they exist in at the
particular moment. This is a problem becuase you cannot make them members of
the Workgroup without having to remove and then rejoin them to the Domain
afterwards.

I can't expect the travling users to log in to a different profile everytime they are in
overseas office.

There is no "other profile" for them to log into anyway. There is no way for
a machine to be part of a domain and part of a workgroup at the same time.
The closest you could come to that is rename the workgroup in the remote
office to match the name of the US Domain. That won't solve the situation,
but it would improve it.

Is there some workaround for this?

One possibility is Netswitcher (www.netswitcher.com)

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

A more powerful suggestion is MultiNetwork Manager 7 from
www.globesoft.com
switch profiles with the push of a button at boot time.