Version 2004 network issues when drives are mapped

Hi, I’ve got quiet a few access points and switches dotted around. Couple of NAS drives. These work great. I map them as drive letters and all works great. Diff story for a couple drives connected to access point and router’s USB port. If I map any folder on these drives they become inaccessible on next reboot. They are also inaccessible in the network. But as soon as i disconnect the mapped drive then they are no longer inaccessible under network. I can click and broaden the contents just fine. Anyone notice the same? Mapping a drive on anything other than a true NAS drive seems to have these side effects

Try cmd line which you can save as a .cmd file and double click yo run

To map a network drive from windows command line:

• Click Start, and then click Run .
• In the Open box, type cmd to open command line window.
• Type the following, replacing Z: with drive letter you want to assign to the shared resource: net use Z: \\computer_name\share_name /PERSISTENT:YES.

Thanks I’ll give it a go. It’s weird because this never an issue til the 2004 feature update. Is there a way I can set a drive to be mapped to Y as part of the login process. Because if once logged in I then map one of these drives then they work ok and are not inaccessible but the problem immediately returns on next restart. So to workaround I can temporarily map them but always have to disconnect them on shutdown

if a CMD can be set to somehow run automatically on login that disconnects at the end of my session when shutting down that could be ideal

baffled why the true NAS drives seem fine and this only afflicts the USB hard drives connected to the router USB and another connected to an access point