I am publishing a .NET application to a webserver. For test purposes, I have had a test website set up at http://lee.interyx.net and am going to try to publish to it.
I get the following error:
"ERROR: Failed to connect to http://lee.interyx.net/NetSched with the follwoing error: Unable to create the web 'http://lee.interyx.net/NetSched/'. Could not find a web server at 'lee.interyx.net' on port 80. Please check to make sure that the web server name is valid and your proxy settings are set correctly. If you are sure that everything is correct, the web server may be temporarily out of service."
I then go through the following steps:
1. Create a new folder in C:\inetpub\wwwroot. Then open IIS and create a virtual directory with an alias of TestSide and point it to the folder. Still unable to browse to the test site in a web browser.
2. On the web server, open a command window. Browse to C:\Windows\Microsoft.NET\Framework\
Run aspnet_regiis -i
This should make sure that asp is registered AFTER the framework is installed
Still not able to browse to the website.
3. Make sure that IIS is running (I know, a little late in the game, but better late than never, and at this point, I was hoping it was just something dumb like this that was overlooked). It was running. :(
4. Reinstall the .NET framework, just to make sure it was installed correctly.
5. Change the publishing location to use the internal address of 10.0.10.20. I am able to browse to the website if I use http://10.0.10.20/NetSched, just not http://lee.interyx.net/NetSched.
Now, I get a new error:
"Failed to connect to 'http://10.0.10.20/NetSched' with the following error: Unable to create the web 'http://10.0.10.20/NetSched'. The web server does not appear to have the FrontPage server extensions installed".
6. Double check to make sure the FrontPage server extensions are installed. They are.
About this time, the entire network went down. Apparently Qwest had a line cut between here and Denver and VCN went down too. When everything came back up, I was able to connect. Hmmm...I don't know what the exact resolution was, as I had gotten other people involved and can not say for sure if they also changed a setting that I do not know about.