I am trying to find out why an ASP.net program works when accessed from the same machine that has the web server, but fails when accessed from another machine in the local network.
I have an ASP.net program that puts a list of files into a list box. The files are in a network directory that resides on a 3rd machine, accessed via \\mach3\myDir\... I logon into machine A (where the web browser resides) and bring up the web page. All of the files are in the list box. I logon to machine B and bring up the web page, I get an error (see above). What is IIS doing differently to tasks that originate from the local machine and tasks that originate from another machine? Some other info:
- The security type is integrated windows, no annomyous user
- On both machines, the Environment.UserName returns the same value (myUser)
- On both machines the HttpContext.Current.User.Identity.Name returns the same value
- Both machines are Windows 2003 SBS
- Before refering to the fixe as a UNC name (\\mach3\myDir...), I referred to the dir using a mapped drive (X:\myDir\...). I worked on the local drive and didnt on the remote drive. The error was "Path xxx not found". (Maybe local and remote tun under a different process?)
- My test machine is XP/Pro, VS 2008, allow annonomous. It is on a different Domain. Environment.UserName returns ASPNET and HttpContext.Current.User.Identity.Name returns MyDomain\myUser
I know that the CustomErrors field in web.config can make the server work differently when the client is not on the local machine. Are there other differences that must be set up or considered?