Link to home
Start Free TrialLog in
Avatar of mpiaser
mpiaser

asked on

Second web server security issue

I am adding a second web server (Web02) to work with the existing Web01 server.  The website for Web02 points to the path for Web01.  When i try to access Web02 via IP address, I get an authentication dialog box (asking for userid/password).  I can't figure out how to give Web02 permissions to the Web01 path.  When I look at permissions on Web01 - I can only see users (such as IUSR_Web01) for the Web01 server and I can't point it to Web02.  
Avatar of pcsmitpra
pcsmitpra
Flag of India image

You may define remote server path as Home path for website properties Home Dir  tab, choose resource located on remote server.
Avatar of mpiaser
mpiaser

ASKER

I have the home path setup on the Web02 IIS configuration to point to the web01/share.  The problem is when I try to access the web02 server by IP address, it asks me for authentication.  When I access web01 by IP address, it does not ask me for authentication.

In Security tab, web02 is pointing to a userid IUSR_DELLSBSR2.  Web01 points to IUSR_WEB01.  I expect that the issue is the IUSR_DELLSBSR2 isn't known  by Web01 (but I can't figure out how to either point Web02 to IUSR_WEB01 or allow Web01 to accept IUSR_DELLSBSR2 as authorized)
ASKER CERTIFIED SOLUTION
Avatar of harperse
harperse
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mpiaser

ASKER

I put Everyone access on the WEb01 share, the directory, IIS permissions for both Web01 and Web02...but I still get the authentication box.    
Avatar of mpiaser

ASKER

Anyone else have any ideas?  WEb01 and Web02 are a member of a group.  i can not access Web01's program set from Web02 as it asks for authentication.  

Perhaps the IUSR_DELLSBSR2 user specified in IIS for Web02 doesn't have the right permissions?  How do I even access the permissions for the user (on a non-Active Directory system)?
Avatar of mpiaser

ASKER

The key problem was that there were subdirectories in the share which had not inherited the security settings.