"Page cannot be found," "Bad Request (Invalid Hostname)," and "Failed to configure IIS" errors
Last Updated October 05, 2006
When trying to run NSSetup or trying to open the Altiris Console using "localhost," the computer name, or IP address 127.0.0.1 (loopback IP address) in the URL, the browser returns the error, "Page cannot be found," "Bad Request (Invalid Hostname)," or "Failed to configure IIS."
Using the computer's IP address in the URL allows you to run NSSetup and open the Altiris Console.
Note: Pinging the Notification Server by "localhost," "127.0.0.1," computer name, or computer IP address all work. The C:\Windows\System32\Drivers\etc\host file includes "localhost" mapped to IP Address 127.0.0.1.
In the Internet Information Services (IIS) Manager, the Default Web site is set to the computer's IP address, and not the "All Unassigned" entry. When the computer's IP address is used, it only uses the listed IP address which precludes using the computer name, localhost, or the loopback IP address of 127.0.0.1.
Open Internet Information Services (IIS) Manager.
Click SERVERNAME (local computer) > Web Sites. Right-click Default Web Sites and click Properties to open the Default Web Site Properties window.
Click the Web Site tab and change the value in the IP Address box to "(All Unassigned)" and click Apply.
Imported Document ID: TECH25384
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe