IIS Intranet Configuration
-
I'm having some trouble getting an asp.net intranet project working on a Windows 2003 server -- I got it working on one server, but I want to run it on different one (both are identical, or at least we thought they were) and for some reason (authentication?) it won't work on the second one. We have a simple html home page that has links to an asp.net app. After setting up ISS on the first machine, getting it up and accessible from other machines was a snap. On the second machine, the home page wouldn’t even come up. Instead we’d get a "Service Unavailable" page. We got around that by giving the Network Service permissions to registry keys it wanted to get to. Then we could access the html home page (http://machine2/), but accessing the web service (eg. http://machine/AppName/AppName.aspx) stuff doesn’t work. To get this part working on machine1, all I needed to do was change the "Application Settings" to the virtual directory, allowing "scripts only" execute permissions. We have compared iis configurations on both machines and can’t find the problem. They seem to be identical, but obviously something must be different (maybe elsewhere in the OS config?). When we use the wfetch tool to access the aspx page we get a 401.1 error. We have looked at the permissions between the machines and can't find any difference. Any help here would be greatly appreciated. Any ideas or pointers to previously answered similar questions, FAQs, etc. appreciated. Matt Gerrans
-
I'm having some trouble getting an asp.net intranet project working on a Windows 2003 server -- I got it working on one server, but I want to run it on different one (both are identical, or at least we thought they were) and for some reason (authentication?) it won't work on the second one. We have a simple html home page that has links to an asp.net app. After setting up ISS on the first machine, getting it up and accessible from other machines was a snap. On the second machine, the home page wouldn’t even come up. Instead we’d get a "Service Unavailable" page. We got around that by giving the Network Service permissions to registry keys it wanted to get to. Then we could access the html home page (http://machine2/), but accessing the web service (eg. http://machine/AppName/AppName.aspx) stuff doesn’t work. To get this part working on machine1, all I needed to do was change the "Application Settings" to the virtual directory, allowing "scripts only" execute permissions. We have compared iis configurations on both machines and can’t find the problem. They seem to be identical, but obviously something must be different (maybe elsewhere in the OS config?). When we use the wfetch tool to access the aspx page we get a 401.1 error. We have looked at the permissions between the machines and can't find any difference. Any help here would be greatly appreciated. Any ideas or pointers to previously answered similar questions, FAQs, etc. appreciated. Matt Gerrans
Hi Matt, There are a number of reasons that can cause the error
Http 503 Service Unavailable, you may need to first check the error log fileHTTP.syswhich should appear in the foldersystemroot\System32\LogFiles\HTTPERR. The errorHttp 401.1is basically thrown when there's a problem related to the authentication issue. The IIS failed to collect the valid user account or the account supplied by the client side is invalid. May I suggest you to download the IIS Resource Kit[^] which can help you figure out the root cause. The chapters 24, 5, 11 may help. Also, you might also want to check out the IIS support site[^]. -
Hi Matt, There are a number of reasons that can cause the error
Http 503 Service Unavailable, you may need to first check the error log fileHTTP.syswhich should appear in the foldersystemroot\System32\LogFiles\HTTPERR. The errorHttp 401.1is basically thrown when there's a problem related to the authentication issue. The IIS failed to collect the valid user account or the account supplied by the client side is invalid. May I suggest you to download the IIS Resource Kit[^] which can help you figure out the root cause. The chapters 24, 5, 11 may help. Also, you might also want to check out the IIS support site[^].Thanks for the help. Turned out after trying a lot of configuration tweaking (system and IIS) to no avail, that uninstalling ISS, removing the whole project, then reinstalling ISS and putting all it back got things working. Apparently there was something strange in the original setup of ISS. Matt Gerrans