Problem mapping drives to/on Server 2008 machine

[tankman1989]

I have a number of computers (Win 7 & 8) which seem to be unable to map drives on a server running Server 2008 enterprise. All machines are on the default workgroup "WORKGROUP" and I can map from desktop to desktop and I can RDP into the server (using IP or computer name) from any of the desktop's, so each machine is seeing the machine.

The server has shared folders set up with access set to "administrator" and "Everyone". The server also has local accounts setup up for User1 & User2 which are the names of the users of the desktops. The only difference is that the passwords for Admnistrator, User1 & 2 on the server are different than those on the local desktops.

When I try to map, I right click computer in Explorer, select "map network drive", enter \\server\shares and then select "logon using different credentials" checkbox. From there I have tried every account on the server with the appropriate password as well as the username of the local machines with their passwords.

What is strange is that at times when I select "use different credentials" it gives me two choices, "Machine_Name/Administrator - and then password box" and then "Use another account". This doesn't always happen which I find strange.

Anyway, I've tried maybe 25 different variations and I get two results. One is it just sits there with the screen saying "attempting to connect to \\server\shares" and it takes anywhere from 30 seconds to 2 minutes to fail out - the other result is an immediate failure that gives me a screen that offers a "diagnose issue" option, which fails each time.

I'm sorry I have no screen shots, I can get them if need be, but that wasn't really an option at the time.

On a side note, I have tried mapping with both the server name and the IP address with identical results - no go.

One strange thing is that when I try to map using local credentials, it says that the computer is using a Domain, as in Domain: Computer_name/Username. IDK if that has anything to do with this.

I'm wondering if I should just set up a domain with AD on the server and then add all the computers to the domain. IDK if this might help anything or not..

 

[CaliZ]

Are the permissions applied to both the folders, along with the network permissions? (Local permission and share permission)

What happens when you try to access the network shares directly from the client computers, (E.g. \\server2k8\sharedfolder ) with the correct user permissions

Also check for any local Internet Security suites installed on the server is not blocking the incoming connections for the shares. (Temp disable the firewall to test)

 

[tankman1989]

Are the permissions applied to both the folders, along with the network permissions? (Local permission and share permission)

What happens when you try to access the network shares directly from the client computers, (E.g. \\server2k8\sharedfolder ) with the correct user permissions

Also check for any local Internet Security suites installed on the server is not blocking the incoming connections for the shares. (Temp disable the firewall to test)

Thanks for the suggestions!

Q1 - I believe so, I'll have to verify when I have access tomorrow.

Q2 - It just times out. It takes forever and then I get some kind of message like unable to find path

Q3 - That is a good call. I installed Kasp Inet Sec on it and didn't think about that affecting the shares. The shares were working when the machine was in the shop but then I installed Kasp, took to client and all is not well. That could very well be the issue. Thanks for the idea!!!

 

[MobileTechie]

I'd be tempted to set it up properly - as a domain if the client it willing.

But from what you say KIS could well be a problem as suggested. I avoid AV's with firewalls in most circumstances but especially in offices.

Out of interest, what is acting as the DNS server?

 

[Moltuae]

What happens if you use 'net use'?

Run 'net use' (without any parameters) first to see what's mapped and 'delete' each of them. You will have mapping for each of the network locations you attempted to map, even if the mapping to a drive letter was unsuccessful. You need to remove those first, eg: net use "\\192.168.0.200\Shared Folder" /delete

I never rely on GUI mapping; it's temperamental and gives misleading information/errors. I prefer to script it at login and use IP address -- much more reliable/consistent.

For example:

net use z: "\\192.168.0.200\Shared Folder" /user:username password /persistent:no

Of course 'persistent:yes' should remap it automatically for you, but it's not 100% reliable; better to remap it at each login to be sure.

Also, Windows has a habit of trying to remap drives before the network connection is ready -- Accompanied by the annoying "could not reconnect all network drives" notification. To get around that, add the following to your login script.

:: Enter the IP of the router (or a server) here
SET ROUTER=192.168.0.1

:: Wait for the LAN connection to be established
:checknet
Ping %ROUTER% -n 1 -w 1000 >nul
if errorlevel 1 (
	goto :checknet
)

Also, I find it better to create users as 'SpecialAccounts' in the registry for net logins, rather than create Windows GUI user accounts unnecessarily for users who may never log in locally.

 

[tankman1989]

What happens if you use 'net use'?

Run 'net use' (without any parameters) first to see what's mapped and 'delete' each of them. You will have mapping for each of the network locations you attempted to map, even if the mapping to a drive letter was unsuccessful. You need to remove those first, eg: net use "\\192.168.0.200\Shared Folder" /delete

I never rely on GUI mapping; it's temperamental and gives misleading information/errors. I prefer to script it at login and use IP address -- much more reliable/consistent.

For example:

net use z: "\\192.168.0.200\Shared Folder" /user:username password /persistent:no

Of course 'persistent:yes' should remap it automatically for you, but it's not 100% reliable; better to remap it at each login to be sure.

Also, Windows has a habit of trying to remap drives before the network connection is ready -- Accompanied by the annoying "could not reconnect all network drives" notification. To get around that, add the following to your login script.

:: Enter the IP of the router (or a server) here
SET ROUTER=192.168.0.1

:: Wait for the LAN connection to be established
:checknet
Ping %ROUTER% -n 1 -w 1000 >nul
if errorlevel 1 (
	goto :checknet
)

Also, I find it better to create users as 'SpecialAccounts' in the registry for net logins, rather than create Windows GUI user accounts unnecessarily for users who may never log in locally.

Thanks for the suggestions. When I first discovered CL mapping I found that it was also more succesful than the GUI confused:), IDKY, I would think it all leads back to the same commands but maybe not.? Anyway once I found the CL mapping, I went back to GUI and didn't have any problems for a couple years until now, so I guess it's back to the B&W screen

 

[Moltuae]

Thanks for the suggestions. When I first discovered CL mapping I found that it was also more succesful than the GUI confused:), IDKY, I would think it all leads back to the same commands but maybe not.? Anyway once I found the CL mapping, I went back to GUI and didn't have any problems for a couple years until now, so I guess it's back to the B&W screen

I'm sure that 'under the skin' both methods trigger the same processes, but the difference of course is the level of control the CL gives you. By scripting/batching you control when the connection is made, what to do if it fails, etc. Also, there are some things the CL will reveal that the GUI won't, like unmapped open connections that don't have an associated drive letter. If any of those have different credentials associated with them, any attempts to map a new connection through the GUI will fail, usually with an unhelpful error message. From the CL, 'net use' will reveal all open/mapped connections and, to remove them all, you can use: net use * /delete /yes

 

[YeOldeStonecat]

I'm wondering if I should just set up a domain with AD on the server and then add all the computers to the domain. IDK if this might help anything or not..

Attempting to manage "workgroups" is a pain in the butt....and at least once a year you end up fighting with stuff, permissions, master browser issues, name resolution, permissions, etc.

Active Directory has soooo many benefits over the mickey-mouse workgroup approach, ......designed to ease your task of management....