• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Cannot Map NAS Fileserver

EXCellR8

EXCellR8

Diamond Member
Hoping someone can help me out with this, as I am at a bit of a loss. I implemented a Synology DS213+ NAS enclosure with 2 mirrored 1TB drives on our network while our main file server is reconfigured. I have everything I need copied to the enclosure so that we can temporarily access our files but I can't seem to get it working right.

I am trying to map the workstations to the NAS but I cannot seem to figure out why it isn't working. The machines run windows 7 but a few are XP. When I map the drive I can see all of the files but it won't stay mapped after logging off and on again, and the machines keep mapping back to the main server. I've tried changing drive letters but something clearly isn't right and I keep getting the "could not remap all networking drives" error.

This is very frustrating since I've literally wasted an entire weekend and I couldn't get it working. User accounts have been set up on the NAS so that each user can access the drive with their own credentials, but I simply cannot get the client machines mapped. Is there something simple that I am overlooking here?
 
I did some digging earlier and it sounded like that could be the issue. I didn't mess around with logon credentials too much, seemed like time was just racing by.

basically a folder on the C: drive on the server is mapped as the F: drive on everybody's local machine. i simply want F: to be used for the new enclosure so that all of our software works as if nothing has changed; since the file directory structure is the same. but there's some kind of conflict it seems and the right location isn't staying mapped.

just my .02 it seems like mapping of drives could have been implemented much better because i feel like this is pretty basic. no idea why i'm struggling so much. oh well.
 
Sounds like a login script or AD mapping issue. Also could be a persistent map and you should use "net use f: /delete" to remove it. If you are using AD it would be better to use a login script or a AD based drive mapping.
 
got a chance to play around with this some more... only partially resolved.

it seems the 'net use' method in the command prompt isn't working on all workstations. some of them did and after logging in again it's fine, but others the original mapping always reappears! grrrrr

i tried both net use f: /delete & net use * /delete /yes

EDIT: also tried deleting registry entries ##servername#sharename but that doesn't work either. server is always remapped upon logging in. this is ridiculous.
 
Last edited:
I'm assuming this is in a domain. Check the "home" directory setting in AD for each user having trouble and make sure it's not using the same drive letter you are trying to use for the network share. If your login script uses the same letter as the home directory setting you'll get this kind of conflict. Also make sure those machines dont have any sort of locally configured login scripts that could be overwriting the one you changed.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top