How to check remote server shared folder file path is accessible or not.

Question

0.00/5 (No votes)

See more:

Hi Friends,
I have 3 texboxes where i am entering for remote file path like 10.201.101.3\test\log.txt, one is for username and other one is for password. So i just need to check whether the remote file path is accessible or not with the use of these username and password of that remote device. Please help me out how to do this in c# and asp.net

Posted 31-Mar-15 0:19am

SanSkun

Add a Solution

Comments

F-ES Sitecore 31-Mar-15 6:29am

Try to read the file using System.IO.File

https://msdn.microsoft.com/en-us/library/system.io.file.openread(v=vs.110).aspx

but put the code in a try\catch block so if you don't have access you'll catch the relevant exception. However if you are using the default anonymous IIS account I can tell you now you probably won't have access as it is a local account with no access to network shares. You might need to change the default anonymous user to an account that has the rights you need. Google for changing the default iis anonymous use account to see how.

SanSkun 31-Mar-15 8:19am

Hi..
This is for reading file from local system. I need to check whether the remote shared folder/file is accessible or not. using userid,password,ip of that remote server

F-ES Sitecore 31-Mar-15 10:36am

You can try calling WNetUseConnection which isn't in a .net assembly but an unmanaged DLL so it's not that straightforward to call.

http://lookfwd.doitforme.gr/blog/media/PinvokeWindowsNetworking.cs

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)