Server 2003 Blocking Port 80

Hello,

I am having an issue with using server 2003 as a web server. At this point,
I have a a blade web server that receives thousands of web calls a day from
devices that access a site to upload data to my system. This is TECHNICALLY
on load balancing, however the other server has been down and needs repair,
but even when it was active, this issue occured.

What is happening: we are losing devices. they get TCP timeout errors when
trying to connect to the website.

What I have done: replaced firewall/router (cisco ASA), tried to replicate
the problem on a 2000 cluster that is still active elsewhere in the company
(problem did not occur there, but this site will be shut down shortly),
researched like you wouldn't believe on the internet. took one of my 2000
servers and placed in the same location as my 2003 cluster(could not
duplicate problem), contacted my isp (was told my traffic was not curtailed
port 80 and that they were not blocking anything coming into my router),
verified that the devices in the field reporting into us were completely
functional.

What I am running: Windows server 2003 on a dell blade server with load
balancing using cold fusion mx 7.

I am wondering if anything has any ideas, I'm at a dead end.....
--
Thanks for replying
~ZSA

"I may as well have a 24 hundred dollar deck of cards cause all I do on that
thing is play solitare"
~Larry the Cable Guy

Try disabling NLB and see if it happens again. Chances are ISP's bandwidth is significantly lower than 1GB :D so you won't hit a bottleneck.

ok pulling it off load balancing and assigning it the load balancing ip did not work. all tried changing the nat on the the ASA to point to the primary nic on the server, but that didn't work.

--
Thanks for replying
~ZSA

"I may as well have a 24 hundred dollar deck of cards cause all I do on that
thing is play solitare"
~Larry the Cable Guy

Servers are not my main forte, but it occurred to me, have you checked that the server is serving on port 80? It might be configured for 8080, or you have something configured for port 80 which is grabbing it before IIS can....

thanks for the advice

I did double and triple check the port iis is serving just to be sure i didn't miss anything in that department and "sadly" it was not as simple as that.

I'm tracking the usage of port 80 via an app to see if the second part of that is happening.

Is ISA firewall running on the network? What about the basic firewall in server 3003? I know these are simple sounding but sometimes the little stuff can get over looked ;) Also I would make sure DNS is good I use http://dnsstuff.org/ they have loads of tools to test DNS.

there is no isa firewall running on the network. when we set this up, the firewall in server 2003 was disabled as a service so it can't run unless the service is enabled.

as far a the dns. i was just going over the config files stored by the devices in the server. the ones that are working since a percentage of them are, are using both the nat ip address and the dns name, so i can conclude that this is probably not the issue as it would affect the global usage of the server to publish a usable website.