External clients cannot access IIS

alverrier1 · ‎11-10-2008

Customer with 12 1700 switches across a WAN, that connect to a webapp served by IIS. Every Monday the remote sites have no access (404) to the Webapp, and we have to reboot the switch. The remote users can ping the server, and LAN users can access the webapp.

IIS is running, restarting it has no effect, and local users can access it.

A NetStat shows multiple connections to IIS in a TIME_WAIT state.

Giuseppe Larosa · ‎11-11-2008

Hello Al,

you should provide more information in order to get better help.

Is the IIS server actually a cluster, is the switch configured to perform server load balancing ?

You say you need to reload a switch : is this the switch where IIS is connected ?

Remote users can ping the server so this is not a routing issue.

Local users can access it.

Trace the path of remote and local users, what is the difference ?

are the remote users reaching via a firewall ?

Is NAT involved with remote users ?

All these questions should help to point to the device / feature that is blocking the http access to the servers from the remote sites.

Hope to help

Giuseppe

alverrier1 · ‎11-11-2008

Thanks for your response.

The IIS server is single/standalone with one NIC. The server is plugged directly into the switch we are rebooting.

It is not a routing issue.

The local user is connected to the same switch as the IIS server.

Remote users are connected across the WAN.

The site uses all static private address.

Name resolution works fine.

No firewall.

The issue appears to be that there are no available connections to IIS.

Rebooting the switch resets all the network connections and then the remote users can connect again.

Is there a keepalive setting that would maintain a connection to a TCP port?