Reconnecting Mapped Drives

[Guest]

For some reason, on the network I'm on at work, which I don't control, every
morning when I go in and turn on the computer, I have four drives mapped to
other computers. I have to open My Computer, and click on one of them, and
enter my login password, and then it connects. Then I can just click on each
of the other 3 and they will connect. I don't know why that happens. But is
there a script or code that I could write a little program to connect
everything up for me on login? Or is there a way to resolve this. The
computers are all XP, but some are Pro and some are Home. I read somewhere
that putting me an account on the other servers would fix it, but it didn't.

Thanks,

Bob

 

[Guest]

You can write a batch file using

NET USE \\servername\sharename /user:username password

to connect each share. Basically, it would be better to sort the thing out,
though.

 

[Guest]

Can you use NET USE on Peer-to-Peer? I thought you had to be on a domain.
I'll give it a try, though.

Any ideas on how "sort the thing out"?

Thanks

 

[Guest]

You can use it anywhere. Main drawback is the need for the password to be in
plaintext. A more-secure alternative is to use AutoIt's DriveMapAdd command,
since you can then encrypt your script to protect the password from casual
viewing.

http://autoitscript.com

 

[Guest]

As for resolving the problems properly, that would depend on the exact nature
of the network. It seems likely there is an issue with the way in which local
and server-side user accounts have been set-up. Or, it might be a problem
with trust-relationships if you have more than one server.

One resolution would be to make the computers domain-members. The issue with
doing that on existing computers is that you will lose all your settings,
etc. as domain accounts use distinct profiles from local users. If you're
using the machine for coding then that might not be an acceptable route.

Another approach is to use MyLogon - OK I'm plugging my product again,
but... with this you can log-on to the network with a username which need not
be the same as the local one, and have a logon-script run to connect the
shares automatically. The logon-script should be in the netlogon share of the
the authenticating server, but if that's not possible it can reside on your
local drive.

 

[Guest]

IT's a Peer-To-Peer network. You don't have trusted domains - because you
don't have domains. I'd love to know how to resolve it because I do Tech
Support on our software, and as a part of that I help people network their
computers to run the software on multiple computers, and some of them
encounter the same problem. I don't know what the answer is within Windows
XP Pro and Home on a Peer-To-Peer network that would resolve it. And I don't
want to introduce additional software.

Thanks, Ian for your feedback. Keep it coming. Anyone else want to chime
in?

Bob

 

[Guest]

Basically, if you browse the posts in here, you'll see that peer-networking
IS troublesome. I support a number of small peer-sites and the network
connections (particularly shared printers) are a constant source of trouble.
I keep prodding them to go server-centric, not so much for the sake of a sale
but to stop them phoning me incessantly!

Some of the other guys in-here have extensive pages dedicated to solving
network problems, these could well be a help.

I do run a peer-network in my office (despite my advice!) mainly because the
computers here are being reconfigured all the time, and the server's often
being used for some software-test or other... I don't ever use "Network
Places" though, I connect with batch-files which assign driveletters, and
that works 95% of the time.