Network UNC for attached Drive

[CarvedDuck]

Hi All,
I have some software that requires a network UNC Path to store data.

I have a USB drive attached to another PC on the network and I can't seem to get the software to see it. I can see it fine with Windows Explorer so I know it is available via the network.

The remote pc name is "w2000" and has drives C: (windows 2000) and G: (blank data HDD) with a Folder named "Data"

I tried the UNC of
\\w2000\g
\\w2000\g\
\\w2000\g\data
\\w2000\g\data\

and nothing is acceptable to the software.

Is it me or the software? If it is me, what should I be using as the UNC to point the software at G:\Data

There is no option in the software to use a Mapped Drive, just a UNC only.

Thanks

 

[TanyaC]

If the G: drive on W2000 as shared as "g" then a UNC of \\w2000\g would show you the contents of the G: drive on w2000.

If the Data folder on G:\ drive on w2000 PC was shared you could access it with the UNC \\w2000\data - This would be the UNC to use if you want to point the software directly to the data folder and not to the root of the G: drive.

You don't need to specify the drive name (g), which in a UNC is not actually a drive, it's a shared resource name. So the last two of your examples would not work.

File and printer sharing and network discovery must be enabled on w2000.

 

[CarvedDuck]

Thanks Tanya,

That's what I thought too, but it is not happening. The software declares a non-existent Path.

File and Printer sharing is fine as I mentioned, I can see it fine on the network with File Explorer and the Paths on the remotes are all Shared and Permissions set OK.

 

[JTsobey]

Can you go to the \\computer name\G$ ? check to see if there is a share for it - from command line run - net share

 

[TanyaC]

Can you go to the \\computer name\G$ ? check to see if there is a share for it - from command line run - net share

Or even just \\w2000?

And see what shares are visible at all?

Edit: If you go to computer, and add a network location of \\w2000, or \\w2000\data does it work? If so, then we know that the share is available via UNC from windows, and that would suggest your software is at fault.

I have seen some software that needs an actual file name, rather than just a path. Might the software be looking for something specific?