Cannot UNC FROM Win 7 in a Domain (Post 2)

Microsoft Windows xp professional w/serv...
November 17, 2011 at 09:44:54
Specs: Win7Ultimate, C2D8400; 2GB RAM
I just started using our first Windows 7 ("Ultimate") machine to help administer my XP Pro/ Server 2003 environment. My problem is that i cannot use UNC paths in Windows Explorer to connect to other computers. Instead, i get an error that says "Windows cannot access \\pcname\C$. check the spelling ...otherwise there might be a problem with your network..." (diagnose does nothing).

i have completely disabled Windows Firewall. All options in Network & Sharing are set to allow. I am in a domain, not a Homegroup. the problem persists regardless of using names or IPs. I tried disabling UAC. I even tried a recommended regedit of adding a "LocalAccountTokenFilterPolicy" key to "HKLM\software\machine\windows\currentversion\policies\system" but this did nothing as well.

thanks in advance...


See More: Cannot UNC FROM Win 7 in a Domain (Post 2)

Report •

#1
November 17, 2011 at 10:00:24
Have you tried \\<IP of server>\c$?

How To Ask Questions The Smart Way


Report •

#2
November 17, 2011 at 13:15:40
Is it the name issue or the hidden share? The share should not be C$ it should be a real shared name. Pretty sure a long ago path blocked hidden shares.

1/3 of highway deaths are caused by drunks. The rest are by people who can't drive any better than a drunk.


Report •

#3
November 18, 2011 at 10:37:10
@razor2.3 - tried by IP too, it's not a name resolution issue.

@jefro - there's shares, like \\pcname\sharename\, but microsoft also includes "hidden admin shares" at the root of every drive, so an admin can ("is supposed to be able to") UNC to \\pcname\C$\ or \\pcname\D$\ or whatever. it still exists in Server 2008 and Windows 7, it's just not working for me.

any other ideas?


Report •

Related Solutions

#4
November 18, 2011 at 11:16:51
Without knowing why or where it's failing, it's mostly just stabs in the dark.

Have you tried to map the share though net use? You'll probably get error 53, but you might get lucky and hit a different error code.

You could also use net view to see if the client / server are talking.

Another step would be to enable all audit logging on a server, then try to connect to its admin shares. If the server's refusing to talk, that should tell you why.

How To Ask Questions The Smart Way


Report •

Ask Question