Remember that the website cannot access the resolution process server 80 port problem resolution process

Server test in the company, to be able to normal access within the local area network (LAN), the server hosting the telecom room, telecom requirements after the server and domain name must be put on record, will open the server outside the network port 80 (not the record of the network port 80 closed and cannot be accessed through domain and ip networks outside), after 2 months of the filing process, during the later telecommunications notice said that has launched the network port 80, but when I test still can't visit the website and found that the network and begin to have the following rule out process, we record to share.

Step 1: Turn off the system firewall and other security software. The test finds that it is still inaccessible.
Step 2: Check if port 80 is occupied by another process on the server.

The DOS command is used primarily as follows

netstat -an
netstat -aon|findstr "80"
tasklist|findstr "2448"

And normal server shows that fewer 0.0.0.0:80, more than the 127.0.0.1:80 that, according to the extra 127.0.0.1:80 pid to find the corresponding process is system (normal server 0.0.0.0:80 according to the process of pid find system), so I started to guess, does the server software installed on port 80 to take up, so I started to uninstall the useless software installed on the server, such as anti-virus software, firewall software, QQ etc., after unloading, Restart the server and you still can't access it.

After searching for a period of time on the Internet, I found that SQL SQL Server 2008 service SQL Server Reporting Services occupied port 80, and the server was installed with SQLserver2008r2, so I stopped the service immediately. The test was still unable to access the external network.

Step 3: Rule out the 80 port problem on the server, or the telecom did not give the 80 port to open the external network.

On the Internet to find the 1 days later, found that there is a post telecommunications didn't to open port 80, so I test server port 80 if there is a problem, think of would be pulled the string out of the original, in another 1 the Internet cable, connect 1 laptop, confirm the LAN ip server, such as 192.168.1.222, then on the notebook cmd start menu - > run - > input, enter - "then enter telnet 192.168.1.222 80, if 80 port is not the problem, will immediately replace with a new window of black, Indicates successful connection. If after 20 seconds, "Connect to 192.168.1.222... Cannot open connection to host. At port 80: Connection failed. "Indicates a problem with port 80 on the server. On the laptop, telnet found that the LAN connection to port 80 could not be connected, so I concluded that it was a server problem.

Step 4: Reload the IIS.

I recall that when I tried to install DNS server on the server, the installation failed. I guess the configuration of iis was changed due to this reason. So I uninstalled IIS and then reinstalled it.

Solutions to save time and effort:

1, take 1 network cable, 1 end is connected to the server, 1 end is connected to the laptop, the LAN test server port 80 whether there is a problem, see the above step 3, you can also do not bind the website domain name, direct access to ip, see whether the website can be opened;
2. If it is confirmed that the port 80 of the server cannot be connected, try whether the port in step 2 above is occupied. If not, reinstall IIS. If it's not a server 80 port problem, consult the telecom configuration port mapping technician to see if port mapping has been done (the server has a router).

Due to the lack of experience, at the beginning 1 thought it was the problem of telecom. When telecom said it had opened port 80, general 1 would not be so unreliable. If they said it had been opened, general 1 would not be their problem.

Most recently, it may have been caused after the server ran the command

netsh http show iplist #check if the 127.0.01 is listed
netsh http add iplisten 127.0.0.1

https://social.technet.microsoft.com/Forums/zh-CN/d719a3f9-56bb-4964-90df-1e21f3d51fd5/-winrm-?forum=windowsserversystemzhchs

Solution run - > cmd- > Enter enter to:

netsh http delete iplisten ipaddress=127.0.0.1

Recently, iis 7.5 has been frequently dropped and updated with the latest patch to solve the problem perfectly.