Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1422
  • Last Modified:

IIS 6.0 can't run ASP pages - config has been verified!

Hi guys, MAJOR problem! Our web server won't server ASP pages! We're running Windows Server 2K3 Web Edition fully patched w/ IIS 6.0.

Basically, when a user accesses an ASP web page, the page doesn't load -- it just times out and gives a 404. This has been happening for 4 DAYS!!! Crazy downtime!

I've restarted the machine and IIS several times. The email server running on the same machine works great. ASP and ASP.NET 1.1 and 2.0 as well as SSI are enabled in Web Service Extensions. The default documents are set correctly as well as everything else. Static HTML documents work fine.

Also, I checked permissions and other settings such as documents/everything else an IIS admin checks. I've never seen this before.

One other thing that I find interesting is that the machine can't access regular web pages like MSN.com and Google.com -- at least on Google everything loads execpt the logo. On MSN it seems nothing loads except the basic code -- no linked CSS files or images or other content. I'm assuming this is part of the problem or is related, because this is exactly what we're experiencing with the sites being served.

What's going on?
0
Pugglewuggle
Asked:
Pugglewuggle
  • 3
1 Solution
 
divinewind80Commented:
Is this IIS servicing an Intranet page or Internet page (inside or outside a network, more or less)?  How many websites is it running?  Just this one?
0
 
PugglewuggleAuthor Commented:
Internet primarily, but we also access the pages from inside the network too.

It is hosting 6 websites, all have the correct host headers put in.
0
 
PugglewuggleAuthor Commented:
The problem has been resolved. What was actually happening is that the Cisco IPS router we have on the DMZ was filtering the HTTP traffic and killing the connection - after the TCP handshake happened, nothing else did. Basically I fixed the config on the router and the problem went away! It had something to do with the DNS query conflicting with the HTTP headers - that's why it still wasn't accessible on the local machine, at least that's what Cisco TAC said any ways.

I'm just glad our server is back up. :-)

Thanks so much! I REALLY appreciate the help.
0
 
PugglewuggleAuthor Commented:
MODERATOR - PLEASE CLOSE THIS QUESTION.

Thanks,
JB
0
 
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

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