Mapped Drive will not connect after reboot

Hi!

My network drive is not on a server, rather on a NAS without those kinds of setting, but if One has access to the server which the mapped drive is located to, this is a solution.

Thanks John,

I selected a series of device numbers in my 192.168.1 range that were not close to any of the 15 or so other device IPv4 addresses shown by my router. When I ran that batch file the NET USE /DELETE lines worked - those share are no longer mapped; but the lines to remap, using the selected IP addresses, failed. So I reverted to the original format for NET USE, with the account name and password, that had worked for me when entered manually. It seemed not to work at all, and no NAS shares are now mapped and visible. Some further research indicated that I need to create an "elevated shortcut" for the batch file, to enable it run as administrator in the STARTUP folder. I'm currently learning how to do that. If you have any further advice on this subject, I would be grateful.

Thanks Andreas,

I'm losing track of who I am replying to; so this reply may also appear elsewhere in the thread. My apologies.

I selected a series of device numbers in my 192.168.1 range that were not close to any of the 15 or so other device IPv4 addresses shown by my router. When I ran that batch file the NET USE /DELETE lines worked - those share are no longer mapped; but the lines to remap, using the selected IP addresses, failed. So I reverted to the original format for NET USE, with the account name and password, that had worked for me when entered manually. It seemed not to work at all, and no NAS shares are now mapped and visible. Some further research indicated that I need to create an "elevated shortcut" for the batch file, to enable it run as administrator in the STARTUP folder. I'm currently learning how to do that. If you have any further advice on this subject, I would be grateful.

Thanks John,

I had thought about maybe trying a batch file to "remap" the NAS drives at every reboot. However, having not done batch files since DOS days, I didn't know how to proceed. I will certainly try yours, adjusted for my system. But first, how did you arrive at the IP addresses for each network drive? The 192.168 part is clear to me; but how one determines the other two parts isn't. Is it arbitrary, or is there some process to suss out just what they need to be?

Hi Rab,

I use a couple of tools, one is Buffalo's NASNavigator which gives the IP addresses, and I have a MAC address database in EXCEL which I maintain to map known entities.

With the MAC address (which is  the hardware ID of a device's network card) I can map that to the DNS data from my home router. I did this in self defense a few years ago when I noticed that there were unnamed machines on my network. Turns out, they were all legitimate but my Canon printer, for example, doesn't have a name in the DNS tables on my router. I know when I see b8:3e:59:d9:99:1b, OK, that's the printer, no worries.

Anyway, the devices, due to DNS leasing, can change IP addresses. So, I also keep the NAS drive IP addresses static in my router setup, for that, you need the MAC address. Once it is setup, most routers can remember that unless you do a factory reset.

For some reason, using the device or server names (like BUFF2/public) wasn't as reliable as the IP, not sure why WINDOWS gets so easily confused, my LINUX boxes don't.

Cheers,

John

PS - I hope the part about DNS leases helps you setup your environment so you can use the IP addressing for the bat files.

Hi!

Thank you for the tip.

My solution with the correction of the date on the NAS only lasted for a few days. :-)

Got another tip now to use the IP Address to the NAS and not the name, and this has worked today. I'll test it for a few more days to see what happens.

This solution worked for me. The mapped network drives remained after a reboot. I'll let you know if anything changes after a few days. My test would be when the NAS goes to sleep and see if the network drives reconnect.