receiving 502 Bad Gateway error when attempting to connect to IIS server... BUT can connect with IP Address fine!

Hello experts.

I cannot connect to my server using  http://www.quiss.com.au/knob (502 Bad Gateway error)

but I can connect using http://202.134.235.46/quiss/knob

I can't connect to anything on the server at all

e.g.

http://www.quiss.com.au/knob

http://www.quiss.com.au/quiss/knob

The zone file on my ISP/registrar's server seems to be fine and when I ping http://www.quiss.com.au it seems to pick up the IP.

I'm guessing it has something to do with firewall or IIS settings on my server. Please help!



LVL 7
Clever_BobAsked:
Who is Participating?
 
bignewfConnect With a Mentor Commented:
Hi Clever Bob,

I will need more info on this-  IIS logs which will show connection errors
Windows event logs on IIS server
and try WC3 Extended logging
Also, protocol analyzer such as wireshark to analyze http requests
Is there a proxy or ISA server upstream in this network?
Have your changed the IP address on the IIS virtual directories
or made any changes and not restarted IIS?
As a test, you could try opening port 53 (DNS) outbound in your firewall to allow DNS requests through
0
 
Praveen DMConnect With a Mentor Infra Team LeadCommented:
Hi...
Plz check thi for a possible solution...

http://www.checkupdown.com/status/E502.html
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.