(I see this being suggested - I have the same issue, but there were no accepted answers to that question)
We have a new dedicated server (Windows Server 2016
) with our hosting provider. They've just allocated a few more IPs, which I've added to the network adapter with the correct subnet/gateway/etc values. However, there are issues accessing things remotely:
(I'm using the IIS 'Default Web Site' for now to eliminate [as the cause of the issue] any user permissions required by IIS for site paths).
When I bind the site to the primary IP of our server, I'm able to access it locally and remotely - it displays the IIS landing page as expected. However when I bind the site to any of the alternate IPs, I'm only able to access it locally from the server.
I noticed that I don't get ping responses from any of our new server's IPs, but I did with our old server's. AFAIK, the hosting provider has set up some external firewall for us. Perhaps they've just set it up to block ping requests.
This is possibly an issue with the provider but I'm wondering if there's something I could configure my side while I wait for their response.