Logging on to network computers...

[Guest]

I have started to upgrade some of my client computers on my network at work.
I currently have 2 desktop clients running XP SP2, 1 laptop running XP SP2, 4
clinets running 2000 Pro and the Server is running 2000 server. The problem I
am running into are on the ones running XP SP2. Everytime I reboot one of
these, I am forced to log into each computer running 2000 (client and server)
to be able to get to the shared item (folder and printers). I am trying to
make this as easy on my employees as possible and need some way for the
computers running XP SP2 go ahead and log into these computers automatically
or somehow set up permissions to not have the log in asked for after each
re-boot. I do not have this problem with the computers running 2000 - they
find and use all of the other computers (even those running XP SP2) fine. Any
ideas?

Thanks in advance!

 

[Guest]

.....

 

[Chuck]

I have started to upgrade some of my client computers on my network at work.
I currently have 2 desktop clients running XP SP2, 1 laptop running XP SP2, 4
clinets running 2000 Pro and the Server is running 2000 server. The problem I
am running into are on the ones running XP SP2. Everytime I reboot one of
these, I am forced to log into each computer running 2000 (client and server)
to be able to get to the shared item (folder and printers). I am trying to
make this as easy on my employees as possible and need some way for the
computers running XP SP2 go ahead and log into these computers automatically
or somehow set up permissions to not have the log in asked for after each
re-boot. I do not have this problem with the computers running 2000 - they
find and use all of the other computers (even those running XP SP2) fine. Any
ideas?

Thanks in advance!

John,

Are you using persistent (mapped) drives on the WinXP computers to the Win2K
computers?

When you are "forced to log into each computer running 2000", what account are
you using to log in with? Is that account the same one used to log into the
WinXP computer locally? Or are you using "log in as"? Or Guest?

On any XP Pro computer, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Pro,
you need to have SFS consistently set on each computer.

On XP Pro, and with SFS disabled, check the Local Security Policies (Control
Panel - Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to "Classic -
local users authenticate as themselves".

On XP Pro, and with SFS disabled, if you set the above Local Security Policy to
"Guest only", enable the Guest account, using Start - Run - "cmd" - type "net
user guest /active:yes" in the command window. If "Classic", setup and use a
common non-Guest account on all computers. Whichever account is used, give it
an identical, non-blank password on all computers.

On XP Pro with Simple File Sharing enabled, make sure that the Guest account is
enabled, on each computer. Enable Guest with Start - Run - "cmd" - type "net
user guest /active:yes" in the command window.

The Win2K computers use Advanced File Sharing, which will use either the remote
account / password (if a matching account / password is enabled locally), or the
Guest account (if enabled locally), for authentication. If that doesn't work,
then the Guest account is used (if enabled locally). If neither work, then you
have to log in manually.

With workgroup membership, you have to setup local accounts (with matching
password) on any workgroup computer that you want to access. As opposed to
domain membership, where you authenticate thru a domain, and possibly get access
to any computer that's also a membership of that domain. Once you get over the
initial setup, using a domain is so much easier than a workgroup.

More about file sharing, between all different versions of Windows:
<http://www.microsoft.com/downloads/...db-aef8-4bef-925e-7ac9be791028&DisplayLang=en>

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.