IIS is not responding intermittently

[sam.s...@gmail.com]

Hello!

We're running IIS 6.0 on Win2k Server.
It's been fine until today.

Randomly it doesn't respond for about 30 seconds.
During the period, I can ping to it but cannot telnet into 80 port.
(Terminal Service is disconnected.)
But after 30 seconds, it works fine again.

I checked the server and event logs didn't show anything suspicious.
In the processes, there are 2 DLLHost.exe and one of them is taking
120M memory.
It's suspicious.
We are running pure asp scripts and no user-defined COM.

Can anybody guess what's wrong?

Thanks.
Sam

[Dominic Ryan]

What are your worker process recycle settings?
--
Dominic Ryan
http://www.it-hq.org
IIS MVP, MCSA, MCSE

[David Wang [Msft]]

Does the web server log files show that requests are being made to the web
server but disconnect somehow, or are the requests not even making it to the
web server at all?

Right now it sounds like you are on the brink of resource exhaustion so
*some* things work while other things fail.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

<sam.s...@gmail.com> wrote in message
news:1145299383.5...@v46g2000cwv.googlegroups.com...

[sam.s...@gmail.com]

Hi, David!

David Wang [Msft] wrote:
> Does the web server log files show that requests are being made to the web
> server but disconnect somehow, or are the requests not even making it to the
> web server at all?
>
> Right now it sounds like you are on the brink of resource exhaustion so
> *some* things work while other things fail.

I found what causes the problem.

The server has 2 adapters for 2 different web sites.
And each adapter is connected to a router which functions as a
firewall.

Windows 2k Server
Adapter1(192.168.0.2)
connected to DLink router
bound to www1
Adapter2(192.168.1.2)
connected to Linksys router
bound to www2

The problem was with www1.
And I found that Adapter2 was set default gateway when I checked "route
print"
I disabled Adapter2 and www1 worked fine.
I enabled Adapter2 back and now Adapter1 is the default gateway.
Now it's like the following. (Look at the last line for default
gateway)

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000004 ...00 40 05 82 7b 21 ...... D-Link DFE-530TX+ PCI Adapter

0x2000003 ...00 13 20 cf 44 da ...... Intel(R) PRO/100 VE Network
Connection
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2
1
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2
1
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2
1
192.168.1.0 255.255.255.0 192.168.1.2 192.168.1.2
1
192.168.1.2 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.2 192.168.1.2
1
224.0.0.0 224.0.0.0 192.168.0.2 192.168.0.2
1
224.0.0.0 224.0.0.0 192.168.1.2 192.168.1.2
1
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2
1
Default Gateway: 192.168.0.1
===========================================================================

Now probably www2 has the problem but www2 is not as important as www1.
Do you know how to fix the problem?

Thanks.

Sam

[David Wang [Msft]]

Ah, this sounds like the networking routing problem with multi-homed
servers. It's a server-misconfiguration - you basically set the "important"
one as default and then add static routes to the smaller networks. Attached
is a prior discussion of this.

----- 8< ---------- 8< ---------- 8< ---------- 8< ---------- 8< -----

I've seen this at least a dozen times and in every case, the users having
the
problem had the following setup:

1. two NICs going to disjoint networks.
2. each of the two NICs have a default gateway defined - either statically
or via DHCP.
3. Internal users and users on the same external subnet had no problems
accessing the site.
4. most had the problem after installing SP1, but others have had the
problem without SP1

If your setup is like above, it is NOT a problem with SP1, rather it's a
problem with your setup. This is a routing issue as the result of having
mutiple default gateways pointing to a disjoint networks. The W2K3 TCP/IP
Implementation Guide states:

"When a computer is multihomed with NICs attached to disjoint networks
(networks that are separate from and unaware of each other, such as a
private
network using private addressing and the Internet), routing problems may
arise. It is often necessary to set up static routes to the private networks
in this situation.

When configuring a computer to be multihomed on two disjoint networks, the
best practice is to configure the default gateway on the interface connected
to the largest and least-known network, in which the default route
summarizes
the most destinations. Then, either add static routes or use a routing
protocol to provide connectivity to the hosts on the smaller or better-known
network. Avoid configuring a different default gateway on each side; this
can
result in unpredictable behavior and loss of connectivity. "

See:

http://www.iis-resources.com/modules/newbb/viewtopic.php?topic_id=1638&forum=9&post_id=7934#forumpost7934

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/networking/tcpip03.mspx

----- >8 ---------- >8 ---------- >8 ---------- >8 ---------- >8 -----

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

<sam.s...@gmail.com> wrote in message
news:1145377511....@t31g2000cwb.googlegroups.com...