IIS server not able to connect through non-ssl

[ck1402]

I have a server that i had to create a VM and move to a different site. It is not living on a Host machine. The original server is still running until i can get this working properly.This server houses a website with an SQL database, and i am having difficulty accessing the webpages that are not https. This server has 3 different websites that are living on it.

Once i am able to access it i will be doing a SQL replication from the current live server. Once everything is synced together that server will be decommissioned.

All of the settings are identical to that of the machine that is currently live. Except for the NIC address which is changed to adapt to the new network it is housed on.

I am able to ping all of the ip addresses and get responses from them. However the webpages are just not showing.

It is running IIS 6.0
I get a Bad Host name in chrome
I get Error 400 server could be contacted however webpage is unavailable.

I am doing this all by IP addresses. I am trying to access the site locally on the network.
I do have port forwarding done to access the site from outside and the only site i can access is the https site.

All suggestions are welcome questions are welcome i am sure i have missed a few things.

 

[ck1402]

Forgot to mention a biggie. The firewall is a Sonicwall.

 

[YeOldeStonecat]

Just to confirm, if you log into another computer on the new servers LAN...and try to access that new IIS box locally on the LAN....you are still unable to open up a .80 page? The Sonicwall should not be in the picture here unless you have the IIS box in an orange zone...but if it's on the regular LAN...reaching across the LAN would not get the SW in the mix.

Or are you trying to access it through a VPN tunnel 'tween the sites?

How about browsing the .80 page from the IIS server itself? If you're in IIS manager...drill down to that http site...can you explore/browse it from within IIS manager?

 

[OaksLabs]

Try on the server in question (if possible) to go

http://127.0.0.1/PathToWebPage

and see if the page displays properly on the server. If so, work backwards from the server until you find the issue.

 

[ck1402]

Just to confirm, if you log into another computer on the new servers LAN...and try to access that new IIS box locally on the LAN....you are still unable to open up a .80 page? The Sonicwall should not be in the picture here unless you have the IIS box in an orange zone...but if it's on the regular LAN...reaching across the LAN would not get the SW in the mix.

Or are you trying to access it through a VPN tunnel 'tween the sites?

How about browsing the .80 page from the IIS server itself? If you're in IIS manager...drill down to that http site...can you explore/browse it from within IIS manager?

Yes i am unable to bring up any .80 page
When i attempt to browse within IIS manager they all come back error 400
It's not in a orange zone.
When i attempt explore i can see the sites and file directory
When i browse i get the same error on all of the pages

When i log into the the server that the VM was created from it works just as it should with in the IIS browser.

I have went between both machines and have all of the settings identitcal i just am not sure where i am going wrong.

When i try the 127.0.0.1/
it does not work on either server. The live one or the VM.

Both of these are on different networks.
They are not connected in any way.

 

[OaksLabs]

If it does not work on the server, it sounds like an issue with IIS. Any web page should be visible from the server itself. I'm no expert on IIS, but carefully look at your configuration and see if you can find the issue.

 

[Markverhyden]

If it does not work on the server, it sounds like an issue with IIS. Any web page should be visible from the server itself. I'm no expert on IIS, but carefully look at your configuration and see if you can find the issue.

^^^ This. Testing from the hosting machine is the starting point.

 

[ck1402]

I will go back through all the configurations and see what is going on and let you guys know if i find anything different. This IIS has 3 different webpages on it. When i look at the live machine only one of those three are viewable through the IIS browse, however it is fully functional.

 

[YeOldeStonecat]

Yes i am unable to bring up any .80 page
When i attempt to browse within IIS manager they all come back error 400

So you can eliminate any firewall(sonicwall) or networking issues...the issue is within the local IIS config itself.
Start grooming over permissions, certificates, .NET base, all of those properties and security settings. Side by side comparison in great details, every toggle switch, every check box, every drop down menu, all tabs, etc.

 

[Markverhyden]

When i try the 127.0.0.1/
it does not work on either server. The live one or the VM.

Both of these are on different networks.
They are not connected in any way.

Did you use the loopback address alone or what @OaksLabs said. I do not know IIS at all either. But his point is to drill down to the main page, index.html, whatever. So would be inetpub\wwwroot or something similar. Also, did you try http://localhost on the server as well.

 

[freedomit]

Check the site bindings maybe? Could the site be somehow bonded to old IP?

 

[ck1402]

Here is a little update. I went to the live server and exported the config files. I then imported them into the VM. Once I did this I was able to browse them within IIS. Now the big issue is getting them functional to view. It's still the same issue of not being able to view through the .80

The settings are exactly the same on both servers within the IIS.

This is progress however.

 

[ck1402]

Still not able to access the website through .80
I can browse it just fine in IIS manager...

 

[ck1402]

Alright guys, i am an idiot apparently.

Since the one website is live the domain is being thrown to it.
It was all in the headers, once i changed the headers to a temp domain bam it worked perfectly.
The site isn't setup to be dualhomed hence the issue...

All in the headers...

 

[Markverhyden]

Details, details.....