Very Odd Sharing Issue

25 Mar 2009 8:08 PM

Ed

I have several PCs in a domain and on one of the PCs are two folders that are
needed to be shared (\\PCName\Share1 and \\PCName\Share2). From all of the
PCs, I'm able to get to \\PCName (and it shows the two folders), and
\\PCName\Share2. However, when I try to get to \\PCName\Share1 from one of
the PCs in the network, it shows as inaccessible.

Using the same user name and password on each of the PCs so it can't be a
username/pwd issue. Even stranger, if I go to a command prompt and enter 'net
use z: \\PCName\Share1', it maps to drive letter Z: and I can browse it fine.
Great! Problem is, the software being run requires me to use the UNC pathname
and not a mapped drive.

I've deleted the user profile and recreated it. I've logged on as the domain
admin on the trouble PC and still been unable to access the shared folder on
\\PCName.

Any ideas would be GREATLY appreciated.

26 Mar 2009 7:47 PM

John Wunderlich

=?Utf-8?B?RWQ=?= <E*@discussions.microsoft.com> wrote in
Show quoteHide quote

news:44100C30-23A1-42F5-AAC3-8F6FE28AD6DB@microsoft.com:

> I have several PCs in a domain and on one of the PCs are two
> folders that are needed to be shared (\\PCName\Share1 and
> \\PCName\Share2). From all of the PCs, I'm able to get to \\PCName
> (and it shows the two folders), and \\PCName\Share2. However, when
> I try to get to \\PCName\Share1 from one of the PCs in the
> network, it shows as inaccessible.
>
> Using the same user name and password on each of the PCs so it
> can't be a username/pwd issue. Even stranger, if I go to a command
> prompt and enter 'net use z: \\PCName\Share1', it maps to drive
> letter Z: and I can browse it fine. Great! Problem is, the
> software being run requires me to use the UNC pathname and not a
> mapped drive.
>
> I've deleted the user profile and recreated it. I've logged on as
> the domain admin on the trouble PC and still been unable to access
> the shared folder on \\PCName.
>
> Any ideas would be GREATLY appreciated.
>

Agreed. This is a strange problem. Once a network share is mapped to
a drive letter, it is mounted and authenticated and should also be
accessible via UNC without further authentication.

All I can think of is to try to put an entry in your LMHOSTS file
for your network share computer...

"How to Write an LMHOSTS File for Domain Validation and Other Name
Resolution Issues"
<http://support.microsoft.com/kb/314108>

HTH,
John