We\u2019re changing the IP address range on the firewalls so we\u2019re adding in the new NAT rules in addition to the old ones for a smooth transition.\u00a0 <\/p>\n
We started with a web server.\u00a0 The site uses DotNetNuke.\u00a0 We tested the new IP and the server wouldn\u2019t load the page on clients.\u00a0 Luckily we\u2019d kept the old IP and could confirm the site was OK on that.\u00a0 I ran Network Monitor 3.3 on the server (NetMon part of my standard server installation package) and on my client to check things out.\u00a0 Our network engineer started looking at router and firewall traces.\u00a0 I could see traffic coming into TCP 80 but the conversation was short.\u00a0 On the client end I could see the same.\u00a0 I compared with a working conversation on the old IP address and saw that there was a different HTTP status code at the start.\u00a0 The failing server was giving me a 302.\u00a0 In fact, my client was loading localhost instead of the site on the new IP address; that was the 302 code redirect.<\/p>\n
I swapped in a default IIS7 site and tested.\u00a0 It worked perfectly.\u00a0 The site bindings were the default norms on the hosted site so it wasn\u2019t that.<\/p>\n
I decided to google (I cannot bring my self to say I binged or bonged something, Microsoft) for DotNetNuke redirecting to localhost.\u00a0 Badda-bing!\u00a0 It appears DotNetNuke has it\u2019s own site binding configuration in a SQL table called PortAlias.\u00a0 I added in a row and added in the new IP address to test.\u00a0 That worked perfectly.<\/p>\n
I now need to have a long shower after doing developer work \ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":"
We\u2019re changing the IP address range on the firewalls so we\u2019re adding in the new NAT rules in addition to the old ones for a smooth transition.\u00a0 We started with a web server.\u00a0 The site uses DotNetNuke.\u00a0 We tested the new IP and the server wouldn\u2019t load the page on clients.\u00a0 Luckily we\u2019d kept the … Continue reading “DotNetNuke Site Redirects To Localhost”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"_wpcom_ai_launchpad_first_post":false,"footnotes":""},"categories":[21],"tags":[],"class_list":["post-9727","post","type-post","status-publish","format-standard","hentry","category-iis"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t