Domain / Workgroup Login Checklist

[Larry Tullos]

Once again the question is how to easily move a laptop between
connecting to the domain at the office and to the workgroup at home.
At first I refused to beleive that MS made such a common problem so
difficult (or at least absure) to solve, but having scrolled through
13000+ messages in this NG today, I've learned that many people are
stuck as well. I found several different "solutions" offered and a
few good references, but nothing as definitive as I hoped. Maybe my
expectations are too high, but I just want to do this as transparently
as possible without having to -

a. Bug my domain admin to set up my log-in again each time I switch
back and forth between worgroup and domain
b. run obscure (to me) net use x commands
c. buy MultiNetwork Manager or other software that changes many more
things that I have to figure out and track
d. Use Simple File Sharing which seems to be another half-ass MS
solution.

None of this is meant to criticize the posters of these solutions
(or bite the hands that's holding the answers) as they at least jumped
into the arena and are contributing their time and effort to help the
rest of us.

Anyway after this lengthy preamble, I'm hoping the experts here can
help confirm, correct, and add to this proposed checklist for what is
required to do this. Here's what I've learned so far ...

1) XP Pro is MANDATORY
2) Use a local account (log-in to this computer) for Workgroup login,
while continuing to use Domain log-in for work
3) MUST have password set for both Workgroup & Domain login. (XP
allows login to Workgroup with blank password, but this will not work)
4) Workgroup name should be same as Domain name on all computers
being shared. (I'm really not sure about this one, nor understand
why)
5) Likewise, Username and Password should be same for Workgroup and
Domain (same question as above)
6) Cache Domain login credentials (not sure where this is done or if
it is absolutely required)
7) Make sure computer brower service is running on each computer in
the Workgroup
8) Don't ever run Network Wizard (It will reset Workgroup name to
MSHOME ... WTF I don't know!)
9) Enable NetBIOS over TCP/IP on all computers (don't really
understand if this is required, just good practice, or needless)

Currently I'm sharing files on my laptop across my home network by
manually searching for the computer name and entering the IP address
to browse across my network. I HAVE NOT CONFIRMED THAT MOST OF THE
SUGGESTED CHANGES ACTUALLY WORK yet for fear of losing the
connectivity I already have. I hope the real experts here
(particularly Steve W., Chuck, Lawrence P., and others) will
contribute one more time to clean up the mess that MS left for us!

- Larry

 

[Richard G. Harper]

Inline:

1) XP Pro is MANDATORY

Yeah, since XP Home won't log into a domain and therefore is irrelevant.

2) Use a local account (log-in to this computer) for Workgroup
login, while continuing to use Domain log-in for work
Yeah.

3) MUST have password set for both Workgroup & Domain login. (XP
allows login to Workgroup with blank password, but this will not work)
Yeah.

4) Workgroup name should be same as Domain name on all computers
being shared. (I'm really not sure about this one, nor understand
why)

Not necessarily. Having the workgroup and domain name the same allows you
to use GUI tools like browsing for shared devices and folders. If you could
master the NET USE command then this is not necessary.

5) Likewise, Username and Password should be same for Workgroup and
Domain (same question as above)

Same answer.

6) Cache Domain login credentials (not sure where this is done or if
it is absolutely required)

Yep. Absolutely necessary unless you have a local admin account on the
computer. Without a cached login you won't be able to log in off the
domain.

7) Make sure computer brower service is running on each computer in
the Workgroup

I'm not so sure on this one, the browser service shouldn't be disabled
unless someone's been feeling froggy with the Services tool.

8) Don't ever run Network Wizard (It will reset Workgroup name to
MSHOME ... WTF I don't know!)
Yeah.

9) Enable NetBIOS over TCP/IP on all computers (don't really
understand if this is required, just good practice, or needless)

Yeah. Remember that your domain provides a list of shared resources at
work, at home you don't have the domain doing that so you will need NetBIOS
to find computers, printers and shares.

I hope the real experts here (particularly Steve W., Chuck,
Lawrence P., and others) will contribute one more time to clean
up the mess that MS left for us!

What mess? Your work computer is your work computer. If your system
administrators want you using it on a network at home they should gladly
assist you in making the changes necessary for home network functionality.
If they don't want you using it on a network at home then you should be
respecting their wishes.

We have a few laptops in my network that are set up to be mobile, the rest
are locked into domain access only and that's the way I want it and my
bosses have agreed. Anyone who tries to go around me winds up with
disciplinary action.

 

[mshannon]

Check-out "Plug and Browse" at
http://www.interactive-studios.net/products/plugbrowse.htm. It allows
you to store multiple network configurations and switch between them
as needed. The program can store network connection settings, computer
name and domain, Internet Explorer, etc.