File.OpenRead WinIOError with UNC Path when not connected to LAN

[cisjokey]

Hello Dear

As in the title above, im getting a WinIOError Exception (_COMPlusExceptionCode -532459699) if i would like to open a file for Read with "File.OpenRead(UNCPath)" and the network cable is not connected to the pc.

The UNC-Path is a legal path to the local harddisk ("\\\\DEV220\\D$\\Temp\\b.doc")
I do not get any error if i plugin the network cable.

Is there a way to open the file by another API call or is the only way to convert the path back to a Windows Path?

The errormessage is as following;
"The network location cannot be reached. For information about network troubleshooting, see Windows Help."

Seems to be a wrong internal handling?

Thanks for your help

Cis

[Plater]

Are you on a domain? You might get something funky for that.
I just unplugged my cable and attempted to open (from the startmenu) \\mycomputer
And I was able to open that and see my shares, but when I tried to look into the shares directories I got a permission denied error.

I am fairly certain that unless you have some extra netbios protocols running, you shouldn't be able to use the UNC paths to your own computer without being connected to something that gives you an IP.

You could just trap that error and manipulate the UNC path to point to something different. Does the UNC path work if you replace your computer name with 127.0.0.1 ? Because that might work.

[cisjokey]

Hmm

I am connected to a domain, but i do not access shares in the network, i just want to access a file on my local disk via a UNC-Path. (D$ is a sharing from my local computer)

If i am not connected to the LAN, i get this Error (but i think it doesn't need network or something because all is completely local?)

I will try with 127.0.0.1 instead of my local host name and will post the result...

[cisjokey]

I tried with 127.0.0.1, no success

Strange thing is, if i put in the given path into the "run" box under "Start", the same error occurs.

I've tried with
\\D$\Temp\b.doc
and \\127.0.0.1\D$\Temp\b.doc"

I've really got no plan?

Thanks

[Plater]

If your computer is part of a domain, your security permisions and everything are obtained from the domain controller.

I've tried with
\\D$\Temp\b.doc
and \\127.0.0.1\D$\Temp\b.doc"

Both of those are accessing shares. Is there any way you can NOT use UNC paths for local actions? UNC is pretty much that standard format for using windows(samba) shares

[cisjokey]

I think if windows is generally not able to connect to a local Path via UNC if no Networkcable is connected, i have to reconvert the UNC Path to a Windows Path. Maybe there is some sourcecode on the www. Or another way?
Thanks again.

[cisjokey]

I think the only option is to reconvert the path, i do not have the path in this "normal windows path" form...

If your computer is part of a domain, your security permisions and everything are obtained from the domain controller.

Both of those are accessing shares. Is there any way you can NOT use UNC paths for local actions? UNC is pretty much that standard format for using windows(samba) shares

[Plater]

Well if you really wanted to get nasty with it, there is a way to find out all the shares on your system and where the physical location they point to is (You can see this by right-clicking my computer and choosing manage, then going to "Shared Folders" and then "Shares")
You can acces this information through code (WMI at the very least I would think) and then use this to determine how to convert the UNC path to a physical path.