IIS Redirect failing

We have two websites.  The default website runs our customer’s data entry website on port 443.  Our security system  is brought up by entering http://www.prorizon.com/account/login or  https://www.prorizon.com/account/login.

If someone only enters http://www.prorizon.com our security system redirects the request to the second website Info (http://www.info.prorizon.com).   The bindings for each site are listed below.  External DNS is setup by our provider for each of the URL’s.

Internally this process works flawlessly.  Externally, if the user goes to one of the account/login URL’s it works perfectly.  But it they try the www.prorizon.com they get a 404 – bad request error message.  All the articles we’ve read mention correcting the host headers.  But as far as we can tell, they all look correct and we’re not sure why it works as expected internally, but not
IIS-Issue.png
sfletcher1959VPAsked:
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.

Dan McFaddenSystems EngineerCommented:
From the outside, I can resolve both IPs for the URLs above.  So it could be something with how you are handling the public to private IP mapping.


Non-authoritative answer:
Name:    www.prorizon.com
Address:  209.195.9.68

Non-authoritative answer:
Name:    www.info.prorizon.com
Address:  209.195.9.81

- how are you NAT-ing/mapping the public IP to the private IP of 192.168.200.68 address?
- what device is doing the redirect?  Load balancer, etc.?

1. I would put a appropriate Host Name on the port 80 bindings on all hosted sites on the server.
2. using wildcards in IIS bindings can sometimes result in unexpected responses.  I recommend placing the actual IP that the site is desired to respond on, on all active bindings, 80 & 443.

Can you post an example of the http logs when you see the 404 message in the logs?  A few lines before and after would be helpful.

Dan
0
sfletcher1959VPAuthor Commented:
This is the error and information that is on the error page.

This error (HTTP 400 Bad Request) means that Internet Explorer was able to connect to the web server, but the webpage could not be found because of a problem with the address.
0
Dan McFaddenSystems EngineerCommented:
There is more detail in the http logs.  Plus, you're original post mentioned a 404 error and above you are mentioning a 400 error.

Which error is it?

Can you answer my questions above as well?

Dan
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
sfletcher1959VPAuthor Commented:
As you may have guessed it was a NAT issue.  I stared at it for days and didn't see where the mapping was off, until you mentioned it above.  It is corrected and working.  Thanks for the help.
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
Microsoft IIS Web Server

From novice to tech pro — start learning today.

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.