500 internal server error

Do you use a Proxy Server?

Because 500 is a application error on a web server, not a network level error.

Chris

No proxy server in use that I'm aware of. That's whats throwing me.
I unchecked the "Show freindly messages" in IE but still get the 500 error instead of anything more specific. All was working well at this place on Friday, but they say on Monday it started giving this. I installed Terminal Services last week, and now can't access TS from remote locations either

I ran Firefox and it gives the same 500 error.

Very odd, that doesn't make much sense. There's no proxy running from auto-configuration and such?

Sorry to be a bit fixated on the proxy angle, but there's no way you can get that error from anything but a server-side application. You'd expect to see if it someone made a coding error on a application driven web-site.

Chris

I logged in again to see what I could ascertain from things. An employee has installed the Logmein Hamachi client on the server (kind of a rouge individual). Could this be causing any issues with DNS??

I am not quite sure of the way it works, but I was just on Logmein site reading about Hamachi and it appears that it runs a type of proxy in the way it works...could this be a problem. Since I have no real control since I'm the outsource person and so it's always a battle at this place to fix things as they get broke.

Yeah, it could well be it. I've not used it myself so I'm not completely familiar with it.

We can test the DNS sub-system, on the command line run "nslookup www.google.com" and see which IP you get back?

Chris

C:\Documents and Settings\Administrator>nslookup www.google.com
Server:  flexsrvr.flextech.local
Address:  192.168.12.100

DNS request timed out.
    timeout was 2 seconds.
*** Request to flexsrvr.flextech.local timed-out

That's not so good :)

Can you see if the server has Forwarders configured at all? If so, try removing them and retry the query.

Chris

C:\Documents and Settings\Administrator>nslookup www.google.com
Server:  flexsrvr.flextech.local
Address:  192.168.12.100

Non-authoritative answer:
Name:    www.l.google.com
Addresses:  64.233.167.99, 64.233.167.104, 64.233.167.147
Aliases:  www.google.com


C:\Documents and Settings\Administrator>

That's after removing Forwarders?

If so, do you still suffer from browsing problems on the PCs? I kind of suspect you do given the previous error you were receiving.

Chris

Yes, after removing forwarders I still get the "500 error"

Henry

Figures.

Okay, so name resolution is not to blame. What to clients use as their default Gateway? Does everything route through the server?

Chris

When I go to Root Hints and try to resolve NS to IP it gives me an error mesage that it can resolve to IP

This help any???

Henry

Not through the server,  the way they have it setup is a Fortigate VPN/Router acts as DCHP and it's used as the gateway

Okay, that makes a lot of sense.

Clients presumably don't have a Proxy hard-configured in their settings?

Do you see the same when using third-party browser like Firefox?

Chris

On Friday last week all worked, then Monday morning this started so whatever is going on seemed to occur over the weekend while they are closed

Heres the IPCONFIG from server adapter:

> Ethernet adapter Local Area Connection 4:
> 
>   Connection-specific DNS Suffix  . :
>   Description . . . . . . . . . . . : TEAM : Flextech
>   Physical Address. . . . . . . . . : 00-15-17-2E-9E-0B
>   DHCP Enabled. . . . . . . . . . . : No
>   IP Address. . . . . . . . . . . . : 192.168.12.100
>   Subnet Mask . . . . . . . . . . . : 255.255.255.0
>   Default Gateway . . . . . . . . . : 192.168.12.1
>   DNS Servers . . . . . . . . . . . : 192.168.12.100
>                                       192.168.12.1
>                                       4.2.2.2
>                                       199.60.229.2
>

FireFox gives same error

Henry

Perhaps just try this one.

Open the command prompt, type:

telnet www.google.com 80

It'll give you a blank screen. Type "GET" and return.

We want to see 400 Bad Request in the returned HTML, it is a bad request, but anything is better than 500.

Chris

It's not related, but it causes problems so frequently it's worth mentioning:

In AD terms this is bad configuration:

>                                       192.168.12.1
>                                       4.2.2.2
>                                       199.60.229.2

The first is the router, the second belongs to Verizon, the third to direct.ca (the ISP?).

The DC, and all clients, should only ever refer to DNS servers that can answer requests for the AD Domain. Not doing so can cause slow logons and general authentication failures.

Chris

Chris

This is what came back from that and now the internet is working????????


<html><head>
            <meta http-equiv="content-type"
content="text/html;charset=utf-8">
                                                                             
  <t
itle>400 Bad Request</title>
                            <style><!--
                                       body {font-family: arial,sans-serif}
                                                                           div.n av {margin-top: 1ex}
                    div.nav A {font-size: 10pt; font-family:
arial,sans-serif}
                                                                             
  sp
an.nav {font-size: 10pt; font-family: arial,sans-serif; font-weight: bold}
                                                                          div.na v A,span.big {font-size: 12pt; color: #0000cc}
                                              div.nav A {font-size: 10pt;
color:
 black}
       A.l:link {color: #6f6f6f}
                                A.u:link {color: green}
                                                       //--></style>
                                                                    <script><!--

var rc=400;
           //-->
                </script>
                         </head>
                                <body text=#000000 bgcolor=#ffffff>
                                                                   <table border =0 cellpadding=2 cellspacing=0 width=100%><tr><td rowspan=3 width=1% nowrap>
                                                                             
<b><
font face=times color=#0039b6 size=10>G</font><font face=times color=#c41200 siz e=10>o</font><font face=times color=#f3c518 size=10>o</font><font face=times col
or=#0039b6 size=10>g</font><font face=times color=#30a72f size=10>l</font><font face=times color=#c41200 size=10>e</font>&nbsp;&nbsp;</b>
                                                         <td>&nbsp;</td></tr>
                                                                             
 <tr
><td bgcolor=#3366cc><font face=arial,sans-serif
>color=#ffffff><b>Error</b></td>
</tr>
     <tr><td>&nbsp;</td></tr></table>
                                     <blockquote>
                                                 <H1>Bad Request</H1>
                                                                     Your client  has issued a malformed or illegal request.

                                           <p>
                                              </blockquote>
                                                           <table width=100% cel lpadding=0 cellspacing=0><tr><td bgcolor=#3366cc><img alt="" width=1 height=4></
td></tr></table>
                </body></html>


Connection to host lost.

Henry

Okay, that's just the response we wanted.

It tells us that at the most basic level TCP/IP is working and you can chat to remote web servers as you should be able to. If clients start repeating the 500 issue it's worth having another look at potential proxy software running on the network.

Chris

Thanks for all your help...you deserve the points for all your effort. Got to poke some more to see what the heck caused things to go south

Henry