Problems mapping network drives

Microsoft WINDOWS XP
July 21, 2009 at 07:35:35
Specs: Windows XP
Hello All,

I work in a domain environment with a central server, Win2003 Standard. All pc's in the office use the same image with WinXP Pro SP3. User accounts are through AD

My problem is that I am unable to access the base directory of our local server or any other domain server.

Symptoms are:
Can ping each server successfully
Can connect to shares on the server
Can use printers on the servers
There is no dialogue box that appears when attempting to map a network drive via "Tools > Map Network Drive
When attempting "net use" in cmd I receive error 67 - The network name cannot be found
When attempting to connect to the server via explorer I get a similar message "windows cannot find \\servername - check the spelling.."
I can navigate to subfolders on the server \\servername\folder

Problem started a few weeks ago.
I can navigate to the
I know it sounds like a permissions problem on the server however when logging in with the same account from a different pc I can access the base directory fine \\servername

Also not being able to open the map network drive prompt leads me to believe a problem with a .dll

I have searched high and low but have found nothing similar to this..

Any help is appreciate.


See More: Problems mapping network drives

Report •

July 21, 2009 at 11:20:31
"All pc's in the office use the same image"

Did you change the SID on all of these imaged machines?
How many machines are we talking about?

Report •

July 21, 2009 at 11:29:22
It is a standard image used on all pc's - around 40-50 in my office. it is set up by our corporate office and each office in the company uses the same image as well.

I don't know exactly how the Security ID works but I assume the security would be different.

Report •

July 21, 2009 at 11:56:16
Didn't use sysprep? Didn't use a sid changer?

Someone in corporate didn't do their homework.

Problem with same SID has been well known since NT days. Results in weird things happening just like you describe.

Google NewSid for an explaination of why the same SID is a problem.
This should help

Solution is as follows;

join workstation to a workgroup
delete AD computer and dns entry for workstation
run the NewSid utility
join the workstation to the domain

Do this for every cloned workstation.

Report •

Related Solutions

July 21, 2009 at 13:11:06
Checked with another one of our techs who assures me the SID is changed during the image process.

Any other direction this can go?

Report •

July 21, 2009 at 13:39:13
post an ipconfig /all from the workstation and the server for review

Any group policies engaged? Who is responsible for group policies?

What changed a week or so ago? Any new updates or work done on the servers from corp it?

Why isn't corp IT addressing this?

Report •

Ask Question