belong to more than 1 workgroup

[Guest]

I have an XP laptop that I take with me to various clients and do work for
them. Each client has a different workgroup. I want to have both (all) the
workgroups set up on my laptop so that I can flip back and forth between
those workgroups and my home workgroup with out having to change the tcp/ip
address on my network setup. Is this possible and if so how?

 

[Shenan Stanley]

I have an XP laptop that I take with me to various clients and do
work for them. Each client has a different workgroup. I want to have
both (all) the workgroups set up on my laptop so that I can flip back
and forth between those workgroups and my home workgroup with out
having to change the tcp/ip address on my network setup. Is this
possible and if so how?

Workgroups?
Not Domains?

Even if it *is* possible, it is a waste of time.
You can access any workgroup/domain resources without being a member of said
workgroup/domain.

With Domains, I MIGHT be able to justify it of the end user did not know how
to script a "map resources" script for my domain and would be better off
just rejoining and logging in as a domain user (running a logon script and
mapping appropriately.) However, with domains, it's a bad idea because a
machine cannot be a member of more than one domain at any given time and the
user in question must have proper rights to join the computer to the domain.

My suggestions, just make scripts that delete old mapped resources and map
new ones in accordance with whatever "workgroup/domain" you want to "be a
memeber of" at any given time.

 

[Torgeir Bakken \(MVP\)]

I have an XP laptop that I take with me to various clients and do work for
them. Each client has a different workgroup. I want to have both (all) the
workgroups set up on my laptop so that I can flip back and forth between
those workgroups and my home workgroup with out having to change the tcp/ip
address on my network setup. Is this possible and if so how?

Hi

You might get something to work with a 3rd party program, e.g this one:


NetSwitcher
http://www.netswitcher.com

 

[Leythos]

With Domains, I MIGHT be able to justify it of the end user did not know how
to script a "map resources" script for my domain and would be better off
just rejoining and logging in as a domain user (running a logon script and
mapping appropriately.) However, with domains, it's a bad idea because a
machine cannot be a member of more than one domain at any given time and the
user in question must have proper rights to join the computer to the domain.

My suggestions, just make scripts that delete old mapped resources and map
new ones in accordance with whatever "workgroup/domain" you want to "be a
memeber of" at any given time.

I agree, this is the proper way to go. I support more than 100 different
companies and use my laptop setup as a workgroup only and still access
their workgroups and domains using mapped connections or by authenticating
with the servers.

Just make a batch file to map the resources you need access too - if you
join the domain or if you are not running a firewall, you never really
know what they might do to YOUR laptop.

 

[Allen M]

Yes you can despite of what the others are saying below. Create a new
hardware profile. On bootup it will prompt you as to what profile to boot
to. This way you can change the network settings for each and any other
profile you hve and won't have to keep changing it everytime your in a
different environment.
You use your current hardware profile and call it Home. Create another one
and call it Company A then edit the network settings to reflect what you
need. Obviously you can create more if you need them.

Right click on My Computer. Left click on Properties. Click on the Hardware
Profiles button. You will see your current profile there.
Select Rename and rename this profile to "Home".
Click on the Copy button and name this profile Company A.
You will now see two profiles. When you reboot select the Comapny A profile
and boot to Windows. Make your changes now and save them with a reboot.
Now whenever you boot to one of these profiles it will use the settings
you've entered.

 

[Shenan Stanley]

Yes you can despite of what the others are saying below. Create a new
hardware profile. On bootup it will prompt you as to what profile to
boot to. This way you can change the network settings for each and
any other profile you hve and won't have to keep changing it
everytime your in a different environment.
You use your current hardware profile and call it Home. Create
another one and call it Company A then edit the network settings to
reflect what you need. Obviously you can create more if you need them.

Right click on My Computer. Left click on Properties. Click on the
Hardware Profiles button. You will see your current profile there.
Select Rename and rename this profile to "Home".
Click on the Copy button and name this profile Company A.
You will now see two profiles. When you reboot select the Comapny A
profile and boot to Windows. Make your changes now and save them with
a reboot. Now whenever you boot to one of these profiles it will use
the settings you've entered.

What Allen is talking about:
http://www.winnetmag.com/Article/ArticleID/86/86.html
and
http://support.microsoft.com/kb/225810

However, I do not believe this will work if you have to configure your
IP/DNS settings for each workgroup - as that would not be retained in a
"Hardware Profile" to my knowledge.

 

[Leythos]

What Allen is talking about:
http://www.winnetmag.com/Article/ArticleID/86/86.html
and
http://support.microsoft.com/kb/225810

However, I do not believe this will work if you have to configure your
IP/DNS settings for each workgroup - as that would not be retained in a
"Hardware Profile" to my knowledge.

Not only that, but in practical use it's a complete PITA.

 

[Shenan Stanley]

What Allen is talking about:
http://www.winnetmag.com/Article/ArticleID/86/86.html
and
http://support.microsoft.com/kb/225810

However, I do not believe this will work if you have to configure
your IP/DNS settings for each workgroup - as that would not be
retained in a "Hardware Profile" to my knowledge.

Not only that, but in practical use it's a complete PITA.

That is the truth.

 

[Guest]

Workgroups?
Not Domains?

Even if it *is* possible, it is a waste of time.
You can access any workgroup/domain resources without being a member of said
workgroup/domain.

With Domains, I MIGHT be able to justify it of the end user did not know how
to script a "map resources" script for my domain and would be better off
just rejoining and logging in as a domain user (running a logon script and
mapping appropriately.) However, with domains, it's a bad idea because a
machine cannot be a member of more than one domain at any given time and the
user in question must have proper rights to join the computer to the domain.

My suggestions, just make scripts that delete old mapped resources and map
new ones in accordance with whatever "workgroup/domain" you want to "be a
memeber of" at any given time.

after reading all the posts here I'm more confused than ever
Domains?????????
I took the laptop "out of the box" and ran network setup for connecting to
computers that DON'T have Internet access, and when it asked for the
workgroup name gave it the office workgroup called "MSHOME" then selected
assign TCP/IP address automaticaly. When I go to the Print offie, for
example, their network group is called "WORKGROUPQ" and they have assigned
TCP/IP addresses begining (###.xxx.?.computer#). When I plug into thier USB
Hub, turn on my computer, go to "My Network" several things show up:
Add new connection; network setup; and Entire Network
going to "Entire Network" 3 things show up:
Microsoft Terminal Services (What's this????? nothing comes up)
Web Cleint Network (What's this????? nothing comes up)
and Microsoft Windows Network
This opens up to show my office network group "MSHOME" but not thier
workgroup "WORGROUPQ"
I gotta go through network setup to connect to computer w/o I-net access and
call my workgroup "WORKGROUPQ" and assign TCP/IP address of ###.xxx.?.99 and
finish setup. Then I see "WORKGROUPQ" (but not "MSHOME") and can send stuff
to their printer (###.xxx.?.60)
NEVER have I connected to an off-site workgroup and seen my "MSHOME"
workgroup AND the local workgroup "thiscompanyworkgroupname" both listed
under "Microsoft Windows Network"
Given All This----HOW DO I DO WHAT I WANT TO DO???????

 

[Shenan Stanley]

<snipped>

Calm yourself.
Deep breaths.

A workgroup is the OLD style - unofficial membership - method of "grouping"
computers (workstations) in organizations. A domain is something where
there is a true "membership" and that comes with priviledges that
non-members would not have. However, the computer does not have to be a
member of the workgroup or domain in order to gleam benefits from the
grouping or membership - the username/password combination needs to be a
member though.

You are trying to use the GUI tools to connect to things - what you need to
do is talk to someone (in person - with your laptop in hand) with more
experience at this sort of thing at your office and allow them to change
your computer as needed. They may determine that for you it is in fact
easier for you to use the GUI tools and change your workgroup for you
(workgroups are easy to change.. START --> RUN --> "sysdm.cpl" --> OK -->
Computer Name tab --> Change button --> Under Member Of section, change the
Workgroup name to whatever you want/need.. --> OK and OK as many times as
you need to close all that. Welcome to the "whatever you typed" workgroup.)
However, if you explain you want to use this at home as well and you are
only willing to use the GUI method of finding resources, etc - then they may
recommend that you rename all your workgroups on your other home systems or
they may write you a script to map the office resources and leave it to you
to figure out your home setup.

A domain is harder to join. *If* your office has a domain setup (and I
think it should,m but d4epending on its size and if it could be afforded, it
may not) then the only person who can join that laptop to the domain is the
administrator and anyone who they have given the proper priviledges to do
so. However, you do not need your computer to be a member of the domain to
use the domain resources (server-printers, shared directories, etc) - you
just need to have a proper domain username/password. Your system
administrator can write you a script to "map" these resources - giving you
the ability to run this script while at work and use the resources there,
then when you go home, still use your laptop normally.

 

[Guest]

A domain is harder to join. *If* your office has a domain setup (and I
think it should,m but d4epending on its size and if it could be afforded, it
may not) then the only person who can join that laptop to the domain is the
administrator and anyone who they have given the proper priviledges to do
so. However, you do not need your computer to be a member of the domain to
use the domain resources (server-printers, shared directories, etc) - you
just need to have a proper domain username/password. Your system
administrator can write you a script to "map" these resources - giving you
the ability to run this script while at work and use the resources there,
then when you go home, still use your laptop normally.

The office is really small-3 people and we're all pretty much neos in
computers so how do we go about setting up a domain?