Context
We’re upgrading from Windows Datacenter 2016 to Datacenter 2022 using IIS 10 and .NET 4.6. I’ve gone through the old server and copied the configuration to the new server, but I’m running into an issue that’s not making sense to me.
Issue
If I’m on the new server, I can open the site from IIS and make it to the landing page. When I point my PCs host file to the new servers IP and ping the site, I get back that same IP. However, when I go to the site through the browser it instead downloads a file. If I change the URL path to go to a static page, it will pull up that static page no problem, but if I click on any links then it downloads another file.
Troubleshooting
I’ve double checked that ASP.NET and ISAPI filters were installed under server roles and features. I double checked that that MIME types in IIS are correct for HTMLs and HTMs (they are mapped to text/html). I’ve looked at the web.config file too and don’t think that’s it either…
I did some testing between the old and new servers. This is what the IIS logs show when I point my host file to the old server
- GET, /, -,
- GET, /wps/myportal, -,
- POST, /samlsps/wps/, -,
- GET, /wps/myportal/, -,
- GET, /wps/myportal/xx/home/…
This is what the IIS logs show when I point my host file to the new server:
- GET, /, -,
- GET, /wps/myportal, -,
I looked on the old and new servers I don’t see folders for /samlsps/ or /xx/home/. I’m not sure what triggers the POST on the old server but not the new one.
A systems admin was helping troubleshoot this with me and this is what we’ve checked so far.
- Under Server Manager > IIS > Services. All of the services and their states match the old server.
- In IIS under Sites > MySite > Actions Panel > Bindings all the site bindings match and the SSL certificates are good for the sites on port 443.
- We checked the folder structure in the inetpub folder. This was copied from the old server and wasn’t changed. There were no differences or missing items.
- We did a few nslookups. One to the server, one to the site. We tested this for both our dev environment and our production environment. Here’s what I can provide for the results.
>nslookup New Server IP
Server: server.domain.com
Address: IP “n”
Name: NewServer.domain.com
Address: New Server IP
>nslookup environment.name.com
Server: server.domain.com
Address: IP “n”
Name: AnotherServer.domain.com
Address: IP “m”
Aliases: environment.name.com
The landing page for login that I should hit when go to the site is hosted by a different team. The system admin thinks that I need to setup a new virtual IP address for the landing page. I’m not sure that’s what’s needed here but I’m also not sure if that was setup on the old server or not.
I remember one of our devs had said that once this is setup is complete, we’d need to switch the DNS to the new server, but I can’t image that would cause this issue. Has anyone else dealt with this before?
