UNC required ???
-
Have a problem with the Server.MapPath command. This works on the local ServerA Server.MapPath("\FSDIR\WORK\track.mdb"); If I want access it from ServerB, programm requires UNC path. This is UNC, isn't it ? He doesn't accept \\ServerB Server.MapPath("\\ServerB\FSDIR\WORK\track.mdb"); Background : I have a Connectionstring and need access to an external server. Is there another method to do this ? Has anybody an example for a connectionstring which handles external access ?
-
Have a problem with the Server.MapPath command. This works on the local ServerA Server.MapPath("\FSDIR\WORK\track.mdb"); If I want access it from ServerB, programm requires UNC path. This is UNC, isn't it ? He doesn't accept \\ServerB Server.MapPath("\\ServerB\FSDIR\WORK\track.mdb"); Background : I have a Connectionstring and need access to an external server. Is there another method to do this ? Has anybody an example for a connectionstring which handles external access ?
This is the forum for ADO.NET. You should post in the ASP.NET[^] forum.
Do you want to know more? WDevs.com - Member's Software Directories, Blogs, FTP, Mail and Forums
-
Have a problem with the Server.MapPath command. This works on the local ServerA Server.MapPath("\FSDIR\WORK\track.mdb"); If I want access it from ServerB, programm requires UNC path. This is UNC, isn't it ? He doesn't accept \\ServerB Server.MapPath("\\ServerB\FSDIR\WORK\track.mdb"); Background : I have a Connectionstring and need access to an external server. Is there another method to do this ? Has anybody an example for a connectionstring which handles external access ?
It's almost certainly a permissions problem. IIS runs as an anonymous user, which probably won't have access to your share. Try enabled NTLM (Integrated Windows Authentication) on your webserver, and then logging into your web application like that. IIS will then use your credentials, and it'll probably work.
using System.Beer;
-
It's almost certainly a permissions problem. IIS runs as an anonymous user, which probably won't have access to your share. Try enabled NTLM (Integrated Windows Authentication) on your webserver, and then logging into your web application like that. IIS will then use your credentials, and it'll probably work.
using System.Beer;
Jon Hulatt wrote: IIS runs as an anonymous user, which probably won't have access to your share. IIS runs as a special user, not anonymous. The user name is different depending on the version of windows being used. In IIS you can set which user will be used when the end user is logged on as anonymous. This user can be configured as a domain user, by default it is a machine user.
Do you want to know more? WDevs.com - Member's Software Directories, Blogs, FTP, Mail and Forums