Learn the essential features and functions of the popular JavaScript framework for building mobile, desktop and web applications.
IIS Website displaying server error in '/' Application
I have a website that wont display correctly when I have the storageRoot0 value in application settings set to a unc path on another server
if I change the unc path to something local like c:\test it displays ok
I have attached screenshots
what could be causing this?
I need to have the storageroot0 pointing to a server in my lan
Capture.JPG
if I change the unc path to something local like c:\test it displays ok
I have attached screenshots
what could be causing this?
I need to have the storageroot0 pointing to a server in my lan
Capture.JPG
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
What are you doing exactly? Are you using some other custom made package?
Most probably, it's just not designed to work from a remote server. Ask the developer of that custom package you're using.
Most probably, it's just not designed to work from a remote server. Ask the developer of that custom package you're using.
I would agree with Kim but try using 2 slashes instead of one.
eg: \\\\<ip>\\path
The other thing you can try is mapping that drive to say X: and then use that as a local drive.
eg: \\\\<ip>\\path
The other thing you can try is mapping that drive to say X: and then use that as a local drive.
Try the 'mapped drive' approach. I don't think you are able to give the IIS user permission to access other servers.
It's the permissions of the IIS User. It is a special user for the web server and it is intentionally limited by design.
Yes but what server
I have the fronet end server with its accessing a file share on another server that does not have its
Where do I configure permission
I have the fronet end server with its accessing a file share on another server that does not have its
Where do I configure permission
In all the previous questions about accessing a remote server from IIS, the answer has always been that you can't. The problem has always been that the IIS user does not have and can not be given permission to access other machines.
I have 2 iis servers that are on a subnet
if I try the storageroot0 location as local on one of the iis servers it works and even if I have the folder on the second iis server as a unc path it works
but if I have the file location on another server that does not have iis installed and on a different subnet I get the error
if I try the storageroot0 location as local on one of the iis servers it works and even if I have the folder on the second iis server as a unc path it works
but if I have the file location on another server that does not have iis installed and on a different subnet I get the error
If that's the case, it's still an authentication problem, and if different subnet, check also if your network settings are correct (source should be able to ping destination and vice versa).
I can ping and access the file via cifs or explorer
its just browsing the website from the iis server fails
its just browsing the website from the iis server fails
Accessing the files is a good step (networking in correct order).
However, you're accessing it as the user you're logged in with.
The app will be accessing the files with the IIS_Users account, which the OTHER side will know nothing about. Just create that account with the correct password on the DESTINATION server.
However, you're accessing it as the user you're logged in with.
The app will be accessing the files with the IIS_Users account, which the OTHER side will know nothing about. Just create that account with the correct password on the DESTINATION server.
just create the same local account?
or maybe install the iis role on the file server
that would install the iis accounts
or maybe install the iis role on the file server
that would install the iis accounts
You're better off switching to a domain account for your application pool, then granting permissions on the file server for that account.
Note you should add the same domain account to the IIS_Users local group on the web server. The IIS user is a local account, so even if you were to install IIS on the file server, it wouldn't grant permissions.
Note you should add the same domain account to the IIS_Users local group on the web server. The IIS user is a local account, so even if you were to install IIS on the file server, it wouldn't grant permissions.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial