IIS 5 & IIS 6
Cannot Access Localhost Nor My IIS
Last post Sep 14, 2017 11:01 AM by abrogard
Aug 27, 2017 11:05 PM|abrogard|LINK
Got a new router from Telstra and checked my IIS for the first time today and found it is not operating.
I cannot see localhost nor 127.0.0.1. 'requested URL not found on this server' message.
I can see my router by inputting my IP (which is a fixed IP).
I have forwarded a port on my router - all the old ones got destroyed when changing routers - but the open port tool says it is not open.
I have an index.php in wwwroot. appending /index.php doesn't help.
net start w3svc seems to indicate IIS is running okay.
win10 is the OS and the firewall is up. I disabled it and found it made no difference.
can anyone help me with a troubleshooting routine to get out of this?
Aug 28, 2017 03:21 AM|Yuk Ding|LINK
So have you tried to ping 127.0.0.1 and localhost? You could try to add a entry in hosts file. If you need to access the website via localhost and 127.0.0.1, please ensure you have a website which is running with such a binding:
<binding protocol="http" bindingInformation="*:80:" />
Then you may need to ensure the 80 port has been enabled in firewall and will not be occupied by another port.
If you are running index.php, just ensure the fastcgi and PHP has been installed and configured.
In addition, please go to IIS log C:\inetpub\logs\LogFiles and ensure the status code is 404.0 not 404.2 or something else.
Aug 28, 2017 04:57 AM|abrogard|LINK
Thanks for your help.
We can leave php out of it for a while because I tried it with an index.html and it still didn't work.
the ping works fine for the 'localhost' and for the IP number.
We should be able to leave the firewall out of it for a while, too, because I have tried it with the firewall disabled and it still didn't work.
I have port 55559 forwarded on the router and that doesn't work either: not just 'localhost' or 'localhost:55559'
I get 'unable to connect' when I use the port number. I get 'not found' without the port number.
My logs don't have a recent logfile. Hasn't been a logfile written in there since 2016 looks like.
I'll try a hosts file entry.
Maybe a reinstall of IIS would be a good thing?
Aug 30, 2017 07:48 AM|Yuk Ding|LINK
I'm not sure whether reinstall IIS could fix this issue, maybe you could try to restore the applicationhost.config in IIS C:\inetpub\history. Please check IIS and httperr log, the error message is important for me to help you fix this issue. So to ensure
works fine, you have to ensure the localhost could be resolved to the right place and then request could be routed to your own site. Secondly, you need a binding to let IIS application pool to handle the request. Please ensure the application pool and site
has been running. In addition, please check whether httperr is listening to 80 port while the netstat -ano should display the 80 port with PID 4.
Aug 30, 2017 10:09 PM|abrogard|LINK
Hello Yuk Ding
still trying to help me even though I didn't do what you first asked? thank you.
I didn't do it because I didn't understand and because I can find no log files and because I wondered about my comments about removing the php factor etc..
Can I start again and say where we are now?
ping will find localhost fine, no problem.
firefox reports 'not found' for localhost and 127.0.0.1
my actual IP finds the router.
the actual IP plus /index.html or /index.php gets 'not found' again.
so I can't find httperr.log
I have some log files in inetpub/logs/logfiles/w3svc1 but the most recent is dated 2016 and there's no httperr. Or is that win10 log? I just thought of that. I'll look. I did a search earlier though and found nothing.
and I don't know how to 'ensure the localhost could be resolved..' and I don't know how to ensure the 'binding to let IIS application pool handle the request..'
I don't know how to ensure the 'application pool and site has been running..' I did that test I told you about which indicated that IIS was running and that's all I know. I've even forgot what that was now and can't see it on the screen right now because
we don't see previous posts when we're writing these replies do we.
I'll go to IIS manager and just look around see what I can find.
And I'll go to the router and open a more common port instead of 55559 Perhaps port 200 might be okay?
And I'll go to wwwroot and rename index.php and index.html and create a new one and put that line in that you showed in your first post.
My index.php used to do this: $user = $_SERVER["LOGON_USER"]; and I vaguely remember I had to implement something or other to make that work. It is not that which is screwing things up now because my test index.html doesn't work either. But anyway
I'll get it all out of there as I say and start anew.
thanks for your help yuk ding. i remember you helped me years ago when i first set all this up.....
Sep 01, 2017 07:20 AM|Yuk Ding|LINK
Considering the firefox has different core from IE explorer. Please try to access the web browser via IE explorer, so we can figure out whehther it is an firefox issue or other configuration issue.
Did you ping localhost with<=1ms? So we can ensure the localhost is always pointing to your own machine.
You need to ensure the IIS manager ->site level->logging has been enabled and then check the ID of your website in IIS manager->site level->advanced setting. If the ID is 5, then you could check the IIS request log in inetpub/logs/logfiles/w3svc5. The last
number of the w3svc folder is site ID. The httperrr listen to HTTP.SYS, the log file is logged in C:\Windows\System32\LogFiles\HTTPERR.
If the IIS have log entry, it should be an IIS configuration issue. However, if only httperr log has error message, you may need to check the server side configuration and network configuration.
In addition, please ensure the website you want to access have a binding like
<binding protocol="http" bindingInformation="*:80:" />
If the steps above is not working, please use command:
To check the 80 port.
Ensure 80 port's PID is 4 and is not occupied by SSRS.
If the issue is still not fixed, try to add the 127.0.0.1 to IP listen list:
netsh add iplisten
Sep 01, 2017 09:55 PM|abrogard|LINK
Thank you for that Yuk Ding.
Might be getting somewhere.
All the pings are < 1ms.
I get the same results in Opera and in Edge.
I stumble around trying to ensure site level logging is enabled but where I got to seems to indicate my default site has an ID of 1
And at that page I found the site was 'stopped' and I found where I could start it but:
binding *:80(http) Status: Stopped (http)
there was an error while performing the operation
the process cannot access the file because it is being used by another process.(Exception from HRESULT:0x80070020)
So that didn't work and maybe the fault is there?
I don't know what 'other process might be using this file so all I could think of was to shut down any browser page looking for localhost. I did that and it didn't help.
Then I did the netstat -ano and I found:
TCP 10.0.0.13:139 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 2252
My machine, this machine, is 10.9.9.13 so it looks like it has ID 4 and port 80 has ID 2252. But I admit I don't really understand this, perhaps I've not done it right.
Sep 07, 2017 08:06 AM|Yuk Ding|LINK
It is obviously that the HTTP.SYS is not listening to the 80 port. Go to task manager to check which process is running with 2252 PID.
If the process is not important, kill it from task manager.
Sep 07, 2017 11:24 AM|abrogard|LINK
Thank you Yuk Ding.
I followed the Microsoft thing and got the result you quoted: 2252 was using port 80
Task manager told me that httpd.exe was using it and that it is Apache HTTP Server using 548K of memory
It also said that httpd.exe was using another process too, 4232 for whatever that means if anything.
I stopped the first process - 2250 - and it didn't help.
Situation right now:
10.0.0.13 (address of this computer on LAN) - Not found
localhost - Not found
Web IP address - router homepage
Web IP + forwarded port - unable to connect
10.0.0.138 - router homepage
I did a netstat -aon and I couldn't find a listing for ports 55559 or 2280. These are two ports I've forwarded on the router. Should i find a listing for them?
I mistrust this router.
Should I give you my IP? Would that help at all?
Sep 08, 2017 02:45 AM|Yuk Ding|LINK
So you are running IIS and apache on the same server? Maybe you need to disable the apache in service manager and kill the process. You don't need to provide the IP address.
Sep 08, 2017 06:18 AM|abrogard|LINK
I am not aware of running Apache. Not aware of having ever installed it or configured it, know nothing about it.
I stopped the task in task manager, it didn't help.
Then I looked for apache in 'remove programmes' and couldn't find it listed.
Just now after reading your post I looked for it in services manager and found it there - but it is listed as 'stopped'.
I will uninstall it completely if I can find how to do it.
I just looked in Task Manager and I see I have three instances of Apache HTTP Server (32 bit) running... three!
Could it be something else is using the apache server without asking/telling me?
If I can't remove Apache perhaps I should go to their website and ask them how I can use the thing: access my localhost via the Apache server!
Sep 11, 2017 09:54 AM|Yuk Ding|LINK
I'm not sure why your machine is running apache and IIS while I can't access your machine. But the port is not occupied by 80 port, you should not be able to access the localhost nor 127.0.0.1. If the listen list doesn't have 80 port with apache.
Maybe you could try to add 80 port to IP listen list.
Sep 11, 2017 10:58 PM|abrogard|LINK
I finally got all that apache stuff out.
Then added a new binding in IIS to 'localhost' with IP 127.0.0.1
Now I can find localhost and log in with the PHP script.
BUT I still can't see my computer via the web IP.
Any ideas where I should look about that?
I just used 'yougetsignal.com' open port checker and it says port 80 is closed!
How can that be? I thought all comms were through port 80? If I'm using the web at all doesn't that mean 80 is open?
Sep 13, 2017 08:46 AM|Yuk Ding|LINK
I test it on my local machine but it report 80 port has been closed as well. So could you find the 80 port with pid in netstat -ano? If you want to access the website via ip address, leave the binding host name to null. In addition, try to add a inbound
rule for your 80 port in FIREWALL.
Sep 13, 2017 09:13 AM|abrogard|LINK
Hello Yuk Ding,
I edited the binding to nullify the name.
I find the 80 port is listened to by SYSTEM
TCP 127.0.0.1:80 0.0.0.0:0 LISTENING 4
PID 4 NT Kernel. System.
I see there are a couple of inbound rules for SYSTEM in the Firewall.
I don't know what to write for the inbound rule you are suggesting. They all seem to quote some application. What app should I quote?
I have IIS on another machine on my LAN : 10.0.0.88 and I forwarded port 3300 to that machine.
I can access the index page on that machine via 10.0.0.88 but when I try the IP + 3300 I get 'connection timed out... too long to respond'
That means to me that it must be a router issue?
Sep 14, 2017 09:00 AM|Yuk Ding|LINK
This link provide the steps to enable inbound rule for windows firewall:
Sep 14, 2017 11:01 AM|abrogard|LINK
That's very good of you, Yuk Ding, thanks for that.
I created a new inbound rule for port 80 and called it '80'.
It has not fixed the problem. I still cannot access via IP + port number.
I can access my index page via 'localhost'.
The bare IP gives me the router.
IP +port gives me 'unable to connect'.
And it does that on two different computers - two different IIS instances - on the LAN.
So I don't think it is an IIS issue.
I think it is the router. What do you think?
NO. Changed my mind. New Evidence. NOT the router. We've come full circle. Back where I started.
I now find I can forward ports to my OTHER machine, other IIS installation, on the LAN and it works perfectly.
So I owe Telstra a lot of apologies and I need to find what's going on here.
Back where I started: perhaps I need an IIS reinstall and even a win10 reinstall.