• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1791
  • Last Modified:

IIS server is not responding to external request

Hi everyone,

For a unknown reason, one of our IIS server stops responding to external request after a couple of minutes/hours.
The only way i can make the IIS works fine is to open a web browser and then browse to a web site.
After that, ping and request to the IIS server coming from the external works.
It looks like the server is in hibernation or something like this but it is not.
Even if I reboot the server or restart the IIS services, it won't work either, i really need to browse to a web site to wake up the server.
I tried to Disable and then Re-enable the external NIC, but same thing.

What i'll try is to ask our web programmer to rollback to the previous version in case he changed something that affect the server, but he doesnt think it is possible (might worth a try).

I need some advices about this.

Thank you

0
Vision_Globale
Asked:
Vision_Globale
  • 4
  • 2
  • 2
2 Solutions
 
robrandonCommented:
Perhaps get in touch with your networking team to see how it is configured on the network.  Next time it happens, instead of browsing outside, just try to ping a public address like www.google.com.  I'm curious if any network traffic enables the in/out communication again.

0
 
giltjrCommented:
You stated that it stops responding to external requests.  Does that mean it responds to internal requests?

When you open a web browser and open a web page, are you doing this on the IIS server?

Is there a firewall, or some other device providing NAT services?  It sounds almost like a NAT is getting dropped and somehow accessing a website gets the NAT back.
0
 
Vision_GlobaleAuthor Commented:
Thank you for those quick replies.

Perhaps get in touch with your networking team to see how it is configured on the network.  Next time it happens, instead of browsing outside, just try to ping a public address like www.google.com.  I'm curious if any network traffic enables the in/out communication again.
I already tried to ping a website and it responded correctly to the ping, but the website was still down from external after this.

You stated that it stops responding to external requests.  Does that mean it responds to internal requests?
Exactly, it stop responding to external requests only.  All request from Internal or in the DMZ works just fine.

When you open a web browser and open a web page, are you doing this on the IIS server?
Yes, directly on the IIS server.

Is there a firewall, or some other device providing NAT services?
The server has a static public IP address and is not NAT.  There is a filtering firewall in front but it has been setup for a while and the problem begun only this monday.  By the way, the IIS server has been there for a while also, it just arrive in a sudden.  


Another information is that our provider had a huge failure in his network last friday and it took more than 8 hours to repair the defective link.  I'm not sure if it is related, but i call them to explain my problem and they say that all the switches are good on their side.
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
Vision_GlobaleAuthor Commented:
Correction : A ping from the IIS server to an external website make it work.
So it means that any traffic generated will re-activate the link for the external.

But still can't see what can cause that.
0
 
giltjrCommented:
Unless the IIS server has two (or more) NIC's and one is used for inside and one for outside, I would say that the problem has nothing to do with the IIS server itself, but with something that is between the IIS server and the Internet.  Most likely the firewall.

What you should do next time is get in contact with the network provider and have them trouble shoot their part of the network.

You may want to use a packet capture utility (MS's Netmon would work just fine for this if you have it installed) and try and capture packets when the problem is occurring to verify if traffic is getting to the IIS server and that the IIS server is responding.  If you don't have Netmon installed I would recommend using Wireshark (http://www.wireshark.org).  In my opinion it is much easier to use and a lot better.
0
 
robrandonCommented:
This really sounds like a network issue.  Do you maintain your router/firewall or is it something your ISP does?

If it's your's connect a computer just outside your router/firewall.  The next time the problem happens, try to connect to your server from that computer.  If it doesn't work, it's a problem with your router/firewall.  Otherwise it's the ISP.

0
 
Vision_GlobaleAuthor Commented:
We have our own firewall, so i'll test it probably tomorrow.

Thank you  
0
 
Vision_GlobaleAuthor Commented:
You are right, it was a problem with our ISP.
Thank you!
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now