Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have server 2003 and ISA 2004 with IIS 6 on same machnie. Everything worked well till yesterday, when we try to make some new rule in ISA..but this is a long story...

Unfortunatelly something happend with our intranet site. Our site is on the port 80, but if we try to open on this client machines then we got and error page (which error page is our provider):

403-forbidden; Remote host not listening, the remote host is not prepared to acceppt the connection request.

On the server i can open the site with port 80. If i change the port number in the iis and try to open the site with the port, then works well.

I try to shut down IIS and start apache with a simple page. On the server works well but in clients the problem is the same, so i think this is not an IIS related problem.

In the ISA we have a web pub rule, with port 80, no auth.

Im pulling out my hair, please help.


after uninstall and reinstall ISA, de sites work well, till i configure the upstream proxy in the conf/network/web chaining menu and then everything went same...

So something wrong with the web-proxy / upstream function... (all my http request forward to my upstream proxy). That was the set long time ago...but a few day ago somehing went wrong...

I think maybee our ISP spoiled something..tomorrow i try to figure out...

But one more thing: I make a new rule before the default rule in the conf/network/web chaining menu.

  1. Every request go to the server not redirected..
  2. Redirect to upstream server....

So if the request goes to our server (our site) then handled locally, and if not then go to upstream proxy and voilllaaa....i tougth... But unfortunatelly: our website work well, but internet work extreamly slowly..:( Maybee with single adapter i can made this? I have to handle all request locally or i have to send all to upstream? I cant filter it?

share|improve this question

2 Answers 2

It sounds like the problem is that your clients are on a proxy and the proxy is trying to contact the web server on an interface on which it isn't listening on port 80.

Try connecting to the server by the IP that is used on the interface facing the proxy. If you don't get a connection, the server isn't listening and you should adjust it in IIS properties. If you do get one, there is a firewall or the proxy is caching the failure.

If for some reason your IIS server is behind a NAT, verify the port forwarding.

share|improve this answer

Try using tcpview to show you which processes are listening on which ports. IIS typically tries to snag 0.0.0.0:80, meaning if you have other IPs on the server, IIS will grab port 80 on those as well, but use tcpview to verify that the site is listening on port 80 (not just on locahost 127.0.0.1 either)

Since you said when you shut down IIS and run apache the clients experience the same problem, this seems more to be an ISA issue, but maybe not...Here is a breakdown of IIS 403 errors.

share|improve this answer
    
only the localhost i found. i did not find server ip with port 80 –  user57467 Jan 11 '11 at 12:27
    
if i use netstat -bn | findstr serverip:80 then got only a few serverip:8080 TCP record... –  user57467 Jan 11 '11 at 12:28
    
ok if you are able to browse the website on the server and not from a client, the website is probably only listening on localhost. Change the website to listen on the server IP and try from a client again. –  August Jan 11 '11 at 12:57
    
ok. how can i do that? in the iis admin/website - properties website identification - advanced menu i have the server ip address with port 80 and header servername.. is that you tougth? –  user57467 Jan 11 '11 at 13:36
    
website properties, on the "Web Site" tab where it says IP address should list the server's IP address and the TCP port should list "80". The netstat will likely list 0.0.0.0:80 which means all IPs on the server are listening on port 80. Try a different port for the website config and see if clients are able to connect to that. Try tcpview to see what other process may be trying to use port 80 - apache may be fighting with IIS over that port –  August Jan 11 '11 at 14:29

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.