I have XP connected to a local area network and have volumes on the remote
computers mapped to local drive letters on XP. Each time I reboot XP,
though, I have to relog in to the remote computers, providing "Administrator
" for user the Administrator password for that machine before I can access
the shares. I've tried logging into all the remotes once and then running
net use /persistent:yes
but this doesn't help. On the next XP reboot I've still got to do it all
over again. How can I make XP log in automatically each reboot?

Thanks
Steve

did you create the same username on the remote computer? this link may help,

Access issues "computername is not accessible. No permission to access the resources" Case Study · Troubleshooting "No accessible" ... is not accessible ...
www.chicagotech.net/accesserrors.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"SteveA" <(E-Mail Removed)> wrote in message news:AB7B5783-0021-47B8-8C61-(E-Mail Removed)...
I have XP connected to a local area network and have volumes on the remote
computers mapped to local drive letters on XP. Each time I reboot XP,
though, I have to relog in to the remote computers, providing "Administrator
" for user the Administrator password for that machine before I can access
the shares. I've tried logging into all the remotes once and then running
net use /persistent:yes
but this doesn't help. On the next XP reboot I've still got to do it all
over again. How can I make XP log in automatically each reboot?

Thanks
Steve

SteveA wrote:

>I have XP connected to a local area network and have volumes on the remote
>computers mapped to local drive letters on XP. Each time I reboot XP,
>though, I have to relog in to the remote computers, providing "Administrator
>" for user the Administrator password for that machine before I can access
>the shares. I've tried logging into all the remotes once and then running
> net use /persistent:yes
>but this doesn't help. On the next XP reboot I've still got to do it all
>over again. How can I make XP log in automatically each reboot?
>
>Thanks
>Steve
>
>
Create a .BAT with a series of NET USE commands, one per mapping, like:

NET USE \\servername\sharename password /PERSIST:yes /USER:yourname

Then park a link to that .BAT in your startup folder.

--
Cheers, Bob

Robert L,

"did you create the same username on the remote computer?"

Yes, they're both "Administrator."

Bob Williard,

"Create a .BAT with a series of NET USE commands, one per mapping, like:

NET USE \\servername\sharename password /PERSIST:yes /USER:yourname
Then park a link to that .BAT in your startup folder. "


I didn't try this, Bob, though I it may well work. I have to believe,
though, that there's a way to form persistent connections within W2K/XP
without resorting to custom batch files.

I did get this work, finally. Here's what I found:

I can generally login automatcially to remote machines that have an account
with the same password as the account I'm logged into, even if the account
name is different.

Default “CR” passwords on the remote machnine (where you just have to enter
a Carriage Return to login at that machine) don’t seem to match anything
passed in over the network, so client machines can never auto log onto those
remote machines, even if their account has a CR password.

The printer on remote machines belongs to Administrator group so if the
client account password is the same as the remote Administrator password, the
autolog to the printer on will generally work.

It appears that if the remote machine has a Guest account , it needs to be
enabled for any automatic logins to succeed. Apparently all remote logins
come in through the Guest account, it that account exists.

In general, it seems that Microsoft networking is a mess! If I thought it
had a cohesive structureI would take the time to dig to its bottom until I
"knew it" , but I suspect rather that it is just a collection of exceptions
that are in constant flux as new rules and excpetions are found to be
necessary. A tool that sensed what you were trying to do and then told you
why it wasn't working would be a big help ("Connection refused: wrong
password", "Connection refused: no xyz account on machine C4") but nothing
like that exists that I know of.

Anyway, thanks for the help.
Steve