Did a disk2vhd of our online production Windows Server 2008R2 server that runs an IIS7 Web Server that serves up our business application:
Launched the VHDX in a Hyper-V VM on a new Windows Server 2016 server.
Gave the VM its own public IP address.
Repointed one of our unused domain names in DNS to point to the VM's public IP address.
In the VM - edited the IIS7 site's bindings - removed the old bindings - and added the bindings for the new domain name.
Port 80 is open to the VM on our Cisco firewall.
The VM's Windows Firewall is turned OFF.
We can ping/RDP/SSH/etc. the VM with no issues!
The problem is that we cannot connect to the IIS web server at all - we get "Refused Connection" [ERR_CONNECTION_REFUSED] errors - (NOT 404 errors).
localhost... We cannot connect to the IIS Server in the VM via localhost (gives a 404 error) - but since we cannot connect via localhost in the production server either, I don't think that matters (also gives a 404 error).
Running out of ideas... help?
[...edit... IIS site binding information for this new server VM]
Remember, this VM is a copy of our real server - so...
I deleted all of the previous domain specific bindings for the IIS site.
I kept the standard bindings (but changed localhost private IP address):
type: host name: port: binding info.:
--- --- --- ---
http localhost 80 10.10.10.99
net.tcp 808:*
net.pipe *
net.msmq localhost
msmq.formatname localhost
And I added the entries for binding this copy of the IIS site to the new domain name - (not worried about https yet):
http domain.com 80 *
http www.domain.com 80 *
[...edit... Hyper-V network]
In Hyper-v manager we created a new "External" virtual switch.
We added a "Network Adapter" to the VM, but never got anywhere... so we changed to a "Legacy Network Adapter" and tried everything again... and still no IIS connection.
And, as I said... all other network services that we need to use against our server (RDP, etc.) work... that makes me believe it's only IIS that is the problem.
CBruce
Found it...
Our consultant was trying to test with localhost after we first loaded the VM - (he didn't know at that time that the production server did not work with localhost).
He forgot that he had changed the HTTP IP listener from 0.0.0.0 to 127.0.0.1 while testing. Therefore, a connection attempt was never getting to the IIS Server - it was being blocked at the interface.
Related
I recently bought a domain. Let's say my domain is "domain.com", and I made a website in visual web dev. using ASP.NET and VB.NET. I also have an old computer that I turned into a home server so I installed windows server 2008 R2 SP2. So I uploaded my website to a folder and went to the IIS manager. There I added a website, set the sitename to "domain.com" application pool to "ASP.NET v4.0". Then the physical path to: "c:\websites\wwwroot\domain.com" then in the bindings I added 3 different things.
type hostname port IP adress
http www.domain.com 80 my IP found at www.what'smyip.com
http domain.com 80 my IP found at www.what'smyip.com
http *blank* 80 192.168.1.6(my server's internal IP)
I made sure port 80 is open in my router and I added a firewall inbound rule for port 80.
When I connect using 192.168.1.6 I get my website and everthing works like it should.
However when I connect using domain.com or www.domain.com I see a 404 page. http://prntscr.com/42ynf4
Also when I change my bindings and I change the IP for domain.com and www.domain.com like displayed below:
type hostname port IP adress
http www.domain.com 80 192.168.1.6(my server's internal IP)
http domain.com 80 192.168.1.6(my server's internal IP)
http *blank* 80 192.168.1.6(my server's internal IP)
It works just like it's supposed to?
I have done a DNSlookup on the domain and it's active. I'm a little bit stuck on this and I know you guys aren't experts on hosting but you all probably have more knowledge about this then I do.
You should check what is the server IP address (netstat), because you could use a proxy and then the Internet IP info will be not correct.
Also, make sure that you set the correct home page in IIS.
I want to access to my localhost from another computer on the network ! I used my pc's IP and created a inbound rule for my port on windows firewall.
This is my localhost address: localhost:2523/StartUpPage.aspx I use my host system's IP 192.168.0.101 so when I use 192.168.0.101:2523/StartUpPage.aspx
I solved The HTTP 400 bad request hostname Error using this link
and I solved The 503 error on remote machine using this link
However now I can access the project on both local and remote system only for few seconds and then get the Unable to lunch IIS express web server Error popup from Visual studio!
Note: I'm running my local host on Visual studio 2012 using IIS Express!
How can I solve this problem?
Thanks in Advance!
Your IIS Express web server is configured to access from localhost by default.
You can change configuration or you can use VS Development server.
To use VS development server:
1. select "Use Visual Studio Development Server" from "Website" menu.
2. from properties of your website project, configure to use static port
3. you can use port forwarder to forward default http port to your server's port
I'm new to Windows Server 2008 and IIS, so please be patient.
I want to access my sites from outside my network.
I can browse my sites from the localhost, it's working.
I've added a binding to my site, Type: http, Host Name: www.dev.com, port: 80.
I have a static IP from my ISP, and my router is forwarding http requests to my server.
If I remove the Host Name and access directly using my network IP address, I get my site, but I want to provide a host name to the site because I'm going to add another web sites.
I've added www.dev.com to the DNS with my IP address.
What should I do next?
Thanks
I found the answer to what I was looking for, I should've done this:
create virtual application www.dev.com under default website on IIS,now I can access the website using STATIC_IP_ADDRESS/www.dev.com .
I am trying to set up a simple website on an IIS 7 server on my home machine. It is going to have light traffic and will only be up for a little while so I don't want to go the commercial hosting route. I am having trouble accessing the site from outside of my local network. So far my setup is:
IIS 7 with the default iis7 page (this is sort of my control/test page)
Static IP
port forwarding on port 1108 from my extermal ip:1108 to my static internal ip:1108
Any idea what could be wrong? My friends who are trying to connect say that they are not getting a "could not connect to server" error on their end.
Thanks!
If this is a standard iis install it is running on port 80 and not 1108.
Also check if "windows firewall" is enabled on your network connection. If the firewall is on it should allow http traffic (under 'allowed programs and features')
I want to run an ASP.Net application on Windows Server 2003 and access it over a LAN.
Like http://serverIP/sitename.com
How do I do this? What configuration changes should I make to IIS?
There are 2 scenarios (assuming you want/have to use IP's in the URL):
You site is the only web-site running on your web-server - you can set up your site with the default port 80 binding, i.e. you don't specify a host name or IP address. This means any request on port 80 will route to your site (remember to stop or delete the "Default" web site, as it normally has the default port 80 binding)
You have multiple sites running on your server - you need to assign an additional IP address for that server and specifically use that IP in the http binding for you site.