I have an issue where port 80 is being blocked by something. My setup is as
- Server 1 win2008 (44.246) Server 2 win2008 R2 (40.219)
- Server 1 is running iis 7
- When I try to access http://server1:80 from server2 the connection times out
- The firewalls are off for both servers 1 and 2
- On server 1 running "netstat -ano | find ":80"" i can see server 2 trying to connect but it just stays on SYN_RECEIVED. Wireshark also shows the connection coming in.
- running "nmap -sT -p 80 --traceroute 192.168.44.246" shows "80/tcp filtered http"
- when i create another website on port 1234 or 9898 everything works correctly.
- port 80 on server 1 is accessible via the internet and works
- port 80 on another server that's on the 44 range works correctly i.e (http://server3:80 (44.231))
There are 3 ports that I'm aware of that are having the same connection issues. The ports are 1111,5555 and 80
what else can i use to see what is blocking these ports?
Thanks
Related
I'm trying to create an express server using node.js but when I start the server on port 80 my friends can't use it. I can select any other port and it will work, but when I try port 80 it doesn't work. I'm using https://www.yougetsignal.com/tools/open-ports/ and https://portchecker.co/check to check if the port is openned, I tried with 3000 and it work perfectly, but I need to get it working in port 80. I have already disabled my firewall and setup my DMZ host in the router.
I believe you are using windows as OS. In it the port 80 could be used as default port for some service. Please check the following -
Skype uses port 80 by default, you can change this in skype options > advanced > connection - and uncheck "use port 80"
Port 80 is the standard HTTP port, so to check which services are using you could run net stop http. It will list the services using port 80 and will ask to whether end them or not.
Port 80 could be occupied by IIS server. Please stop IIS and then re-run the node service.
Some SQL Server Reporting services also use port 80
I have an Ubuntu16.04 VM on Azure, and am trying to run a node server on it. When I bind the port to 80, I am able to access it from my browser (http://a.b.c.d:80). However, if I try to instead bind the server to a different port, such as 3300 or 8080, the browser times out when trying to connect to it. (http://a.b.c.d:3300)
I have ensured that:
There exists an inbound security rule for port 3300 in the NSG
The windows firewall of the machine of the browser allows port 3300 (I have even tried temporarily turning it completely off but to no avail)
I am not using an azure load balancer
I am starting node with root privileges
Node is bound to (port, "0.0.0.0")
I am listening on the correct port (I think?)
netstat -ant | grep 3300 gives
tcp6 0 0 :::3300 :::* LISTEN
I have spent a few hours now researching on the internet how to get it to work and tried everything I could find, but to no avail. If anyone has any input i'd be happy to try it out.
Jason was correct, it was a ufw issue. If anyone comes across this question in the future, I solved it with the command
sudo ufw allow proto tcp from any to any port 3300
I have website working fine on my local machine as host name hml.frontend in the hosts file: 127.0.0.1 hml.frontend
In IIS I have bindings as hml.frontend 127.0.0.1 and hml.frontend 192.168.1.94. The latter I used ipconfig to get my local ip address issued to me by my BT Home Hub 5 router.
In windows 10 firewall I have allowed App/Feature NetLogon service and World Wide Web services (HTTP).
In advanced settings in Inbound Rules I have added a rule which allow the connection from all sources to ports 80 and 443. Scope is any IP addresses.
On my macbook I have added the 192.168.1.94 as hml.frontend to the hosts file.
I can ping hml.frontend OK from the macbook.
However from a web browser the http://hml.frontend site cannot be reached from the macbook.
telnet 192.168.1.94 80 from the macbook says unable to connect to remote host.
Back on the PC I have done netstat -na to see which ports IIS is listening on and 127.0.0.1:80 is there and so is 192.168.1.94:139 and many more ports against that IP address but not port 80.
Any ideas what I can check to get my PC to listen for that website hostname on port 80?
I got it to work, I was on the right track that the IP address was not being listened to.
In order to add the ip address I have to be listened to, I went into cmd as adminstrator, did
netsh
http
show iplisten
'show' result shows that just 127.0.0.1 was being listened on port 80
add iplisten ipaddress=192.168.1.94
show iplisten
quit
'show' result shows that now additionally 192.168.1.94 is being listened on port 80
Then I went back in with
netstat -na
And now I see the line I want:
TCP 192.168.1.94:80 0.0.0.0:0 LISTENING
Some information was gained from this article.
http://windowsitpro.com/windows-server/solve-iis-listener-problems
The site is now reachable from my macbook using the hostname http://hml.frontend
I am using IIS 7.5 on Windows Server 2008 R2.
From this server, I can access the localhost (standard IIS start page is displayed).
But I can't access it from any other machine belonging to the same network.
I have the impression that the problem is that my server is not listening at the address 0.0.0.0:80.
Because when I do a netstat -aon | findstr 80 I get only:
TCP 127.0.0.1:80 0.0.0.0:0 LISTENING 4
TCP [::]:80 [::]:0 LISTENING 4
But if I do netsh http show iplisten I then see (I have added the two last ones manually)
IP addresses present in the IP listen list:
-------------------------------------------
127.0.0.1
0.0.0.0
::
One additional test that I did:
When I try netcat -v xx.xxx.xx.xx 80 on the client, I get the error "Connection refused".
But after doing netcat -l -p 80 on the server, the netcat connection from client works and I can exchange data.
Because of this I don't think that it is a firewall issue.
Do you have any idea on the causes and how to solve the issue?
Thanks a lot in advance for your feedback!
I have a running nodejs based socket.io server on AWS ec2, this server is running on port 90, and i can run the local tests on this server at the same port.
netstat -a shows me the port 90 as open as well for connections
tcp 0 0 localhost:3001 *:* LISTEN
tcp 0 0 *:90 *:* LISTEN
I can vouch for the fact that I have the port 90 open on my security group settings, yet I can not connect at the port 90 to my server.
I am not doing anything as foolish as making my clients connect over the localhost.
I have tried telnet to my server at the port 90 but it doesn't work
I have port 22 and 80 open as well and I can very well telnet to them.