Welcome to WebmasterWorld Guest from 54.167.46.29

Forum Moderators: bill

Message Too Old, No Replies

How to reconnect mapped drives on windows 7

Mapped network drives

     
7:16 pm on Oct 27, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 5+ Year Member

joined:Feb 22, 2009
posts:1396
votes: 0


Hi all,

Well in my windows 7 environment, which is fine, runs great, except when I have to reboot (can't leave it on over the weekend at work) - this causes my network drives to "disconnect" even though when I click on the icons, it takes me directly to that mapped location...

Anyone else have this issue at all, or knows of a way of stopping this little niggle.

Cheers,
MRb
6:25 am on Nov 3, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 5+ Year Member

joined:Apr 28, 2006
posts:1043
votes: 1


Are you mapping to shared drives through a wireless connection?
Are the destination computers being restarted or staying on over the weekend?
You could always create a login.bat script to start when you log in to Windows

net use O: \\servername\sharename /y
10:30 pm on Nov 3, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 5+ Year Member

joined:Feb 22, 2009
posts:1396
votes: 0


Hi there youfoundjake,

The server at work is on a UPS, and is on near as damn it permanently - AFAIK it all wired network, some of the development laptops are wireless, but they are only used when visitors are in, this little glitch is playing havoc with only our windows 7 machines, all the others are fine.

Not too familiar with that switch there, what does that mean?

Thanks for the input anyway.

Cheers,
MRb
11:01 pm on Nov 3, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 5+ Year Member

joined:Feb 16, 2007
posts:846
votes: 0



C:\>net use /?
The syntax of this command is:

NET USE
[devicename | *] [\\computername\sharename[\volume] [password | *]]
[/USER:[domainname\]username]
[/USER:[dotted domain name\]username]
[/USER:[username@dotted domain name]
[/SMARTCARD]
[/SAVECRED]
[[/DELETE] | [/PERSISTENT:{YES | NO}]]

NET USE {devicename | *} [password | *] /HOME

NET USE [/PERSISTENT:{YES | NO}]


The /Y flag creates a persistent connection.
5:54 am on Nov 4, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 5+ Year Member

joined:Apr 28, 2006
posts:1043
votes: 1


Oh, also check power management for your nic cards, they could be getting turned off in order to save power.

Another thing to consider is that if you are using DHCP, I have seen Windows try and connect to a mapped drive prior to getting an IP address from the DHCP server or router, and of course a little box pops up saying "Unable to connect to network drives" but by the time you open up my computer and double click the network drive, the address has been obtained, and you are able to browse the network share. If this is the case, you can try a static IP address.
6:31 pm on Nov 8, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member

joined:Jan 30, 2006
posts:1599
votes: 1


ok the command line is fun at all but.

== click my computer
== click map network drive
== enter drive path
== enter user name and password
== check mark reconnect at login
10:14 pm on Nov 13, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 5+ Year Member

joined:Apr 28, 2006
posts:1043
votes: 1


J_RaD
I think the OP said the drive is already mapped. The issue is on reboot, he has to manually force it to refresh the connection. From what I gather, he wants it to just happen, not have to do the same thing every Monday morning.
Command line could automate it. The Power options and static IP address could address the core issue.
9:30 pm on Nov 16, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 5+ Year Member

joined:Feb 22, 2009
posts:1396
votes: 0


Update!

Well this is bizarre, since I had a windows update, quite rudely interrupt me during a NIOS compiling session, the issue seems to have gone. When I booted on Monday morning, I was thoroughly expecting to snarl angrily at the computer screen as the drives would need connecting (in house software fails it's first db query if the drives aren't connected), but this time - they were already connected.

So I shut down and tried again, and so far, it seems to be ok.

It is actually company policy to have windows updates disabled as the nature of our products rely on machines being on (as best they can 24/7), and windows updates are renowned for needing to 'restart' your machine!

Anyway, just thought I ought to just update the issue.

Cheers,
MRb