URGENT! Microsoft Server 2003 R2 Suddenly Not Serving

URGENT HELP NEEDED
Our Windows 2003 R2 Server suddenly stopped working. I can ping the gateway but none of the IIS websites respond to ping.

URGENT HELP NEEDED
Our Windows 2003 R2 Server suddenly stopped working. I can ping the gateway but none of the IIS websites respond to ping.

I've tried tracerouts and even pings remotely such as from pingdom.com but only the gateway answers.

I've removed the firewall and AVG security and made certain our IIS servers are set correctly

TCP/IP connections have the correct ip's, gateway, dns, etc.

Nothing is down. Other work stations on our LAN work fine on the same bandwidth.

I rebooted the server several times

Changed NIC connection

Booted the router.

Installed a different connector and disabled the other, back and forth.

No log reports of any trouble on the server.

Actiontec M1424wr router indicates INTERNET is connected and no trouble lights.

I've changed NIC cables just to be sure, made certain they are connected correctly.

All websites in IIS server are running.

I toggled ColdFusion and WWW publishing off/on with no help.

Noting has changed in the IIS setup and the Ip's there are correct.

My dns settings are also correct at my REGISTRAR website. An nslookup on the domains match those in IIS.

DNS is correctly set and our bandwidth provider has not cut us off.

What else can I check? Seems kind of coincidental that MS is ending support for Server 2003 today. I know, just a coincidence I guess.

I sure need help on this one as ASAP.



What else can I check? Seems kind of coincidental that MS is ending support for Server 2003 today. I know, just a coincidence I guess.

I sure need help on this one as ASAP.
Grover McBroomAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Wayne88Commented:
<li> I've tried tracerouts and even pings remotely such as from pingdom.com but only the gateway answers.</li>

Can you pull up the website using it's ip address instead of domain name?  If not what error did you get?  Is it the common 404?

Can you pull up the website directly on the server subtituting the domain name with the server's ip address or "localhost" or the loopback address 127.0.0.1?  This way it's not going through any gateway and I am trying to determine if the problem is local to the server or external (IIS services not running etc.)

A stupid question but are you sure IIS service is running or tried restarting the service?
0
Grover McBroomAuthor Commented:
I cannot ping the ip so of course when I attempt to bring up the site via ip, there is no answer, no 404 of course, just "Unable to connect", depending on the browser I'm using.

Again, the Gateway responds but none of the individual ip's, ping or on port 80, which is open for the site. And again, I took security down as well as the Firewall so it's all open at the moment, if only one of the ip's would respond.

Ideas to try?
0
Wayne88Commented:
Can you try bringing up the webpage from an internet browser installed on the server as mentioned previously?  So you're trying to bring the webpage up directly on the server.  If successful then the problem is dns or firewall related and not the server.

The point is that you want to eliminate server issue vs. external and narrow down from there.
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

Wayne88Commented:
Is the website also available internally?  What happens if you give the server an internal ip address and try to access the website internally to the network?  This why you can determine if the problem is internal or external.

Can you try bringing up the webpage from an internet browser installed on the server as mentioned previously?  So you're trying to bring the webpage up directly on the server.  If successful then the problem is dns or firewall related and not the server.

If no issues internally then you can be sure the problem is from your router and outward.

The point is that you want to eliminate server issue vs. external and narrow down from there.
0
Grover McBroomAuthor Commented:
Good ideas! When entering the website ip in the address bar I get BAD REQUEST (Invalid Hostname).

Get the same for all website ip's.

What could cause this?  Where should I look first?
0
Wayne88Commented:
Sounds like something wasn't entered properly.  Can you try typing in the ip address into the address bar?  Clear the address bar and just put the ip address.  Some internet browsers will automatically instert http:\\ if it sense an http server at the other end and pull up the website that's set as default.
0
Grover McBroomAuthor Commented:
I'm sure I entered the ip correctly. I'm certain of this.

And now I cannot connect to CF Administrator via local host located on the server where I received the  "Invalid Hostname" error! So strange. I was able to do so a few minutes ago but not now. I changed nothing.

Thanks for suggesting trying to get the website to respond directly via IP. Perhaps that points to the main problem. What can cause the Invalid Hostname error?
0
Wayne88Commented:
How do I Fix a “Bad Request (Invalid Hostname)” Error on a Webpage using IIS?Typically when a web site is displaying the follow error it means that the site is not listening on the correct IP or the host headers are missing. Bad Request (Invalid Hostname) To access the host headers and address issues for a site follow these steps. Start by logging into the web server where the site is hosted. Now open up IIS Manager. Expand the web sites folder to display all of the sites in the right hand frame. Now right click on the domain name and select “Properties”. The default tab is the Web Site tab, click the Advanced button next to the IP address. This will display all the host headers for the site. Click the “add” button to add a host header to the site. In this example we are going to add a www host header since it is missing. Now select the same IP address as the domain is running on enter port 80 and input the www version of the domain name. Click Ok three times and the host header should be successfully added.

http://www.serverintellect.com/support/iis/fix-bad-request-invalid-hostname/
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Grover McBroomAuthor Commented:
The Host Headers are correct and have not changed, default domain plus www and all on port 80. This cannot be the problem.

Remember that I have tried to ping the ip associated with the website dns and no service I selected remotely can ping any of the ip addresses, just the gateway. That seems to override host headers and other such concerns.

It is as though those ip's are not responding or not binded to the network. But they are or should be but I. I've carefully checked that all the required ip addressed have been entered into the tcp/ip properties of the NIC card currently being used. The other NIC is turned off. This server has dual nic cards.

I can ping all ip's just fine from the local server machine. But nowhere else on my network, or on the internet.

With that info, what does anyone suggest? Where should I look? I'd sure like to get this server back up. It's a NEWS server and pretty active.
0
Wayne88Commented:
You said you were getting "Invalid Hostname" error but I am not sure where this occurs.  Have you tried accessing the webpages directly on the server?  You should be able to, if not it's IIS that maybe the issue.
0
hieloCommented:
For the sake of clarity, let's say you have:
{Machine A - the server} and {Machine B - a client machine}.  From the discussion above, it is not clear if you have attempted to open your site via a browser from Machine A which is what Wayne88 was suggesting in order to rule out the Server.

Also, on the control panel of Machine A, do you see any "yellow exclamation mark" on the network devices.  I previously encountered the situation where the network card driver was corrupted.  I fixed it by uninstalling the network card's driver and reinstalling it.
0
Grover McBroomAuthor Commented:
I did say, "When entering the website ip in the address bar I get BAD REQUEST (Invalid Hostname)."  Sorry for any confusion as I did not explain what "address bar" is.

This ended up having nothing to do with Bad Request (Invalid Hostname or at least I have no idea why wrong connections on the router would give that error. Perhaps the Actiontec was in a way, set up backwards.

It appears the  problem may be related only to the Actiontec router or its setup or connections.

I was able to get everything working by bypassing the Actiontec router and connecting our Ethernet host bandwidth from Frontier directly to our Cisco 2950 router.

I then had to feed output from the Cisco router back to the WAN input on the Actiontec. From the Actiontec router I was then able to feed the rest of our workstations connectivity because those same workstations would not resolve at all from the Cisco router, even tho the server would. So, only the Server would resolve from the Cisco router. Very strange. Must be a simple explanation but it's beyond me, was ready to step into the path of a speeding car ...

I'd rather this work as it should, whatever that is, but later. Do you all suggest I open another ticket with Routers as a main topic or would that probably be a waste of time?

Thanks for all the suggestions.
0
Wayne88Commented:
Sorry, not sure what to suggest but I would consider this topic closed since you narrowed down the problem to be the router.  We all were under the assumption that the problem was with the server not serving the website(s) and if that's the case then querying the website directly on the server as I suggested would've clearly indicate that the problem wasn't with the server because it would have brought up the page open (providing the URL is referred to correctly).
0
Grover McBroomAuthor Commented:
> I would consider this topic closed

Wanye: I already closed the topic and graded it with an A, so not sure about your last post.

My input on the browser address bar was just as you suggested, reported it to you exactly as shown. It's not your fault so no explanation is necessary. I'll need to fix this later as a router problem, or inept operator. Again, its close and thanks, no further suggestions or reply needed.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.