I have port fortforwarded both port 80 and 150 to try and connect to my wampserver/webpage.
When I check if the port is open on https://www.yougetsignal.com/tools/open-ports/ or a software I use it says that the port is open. However when I try to connect the server/webpage I can not reach it.
If I check if the port is open while I am trying to connect/reach the website, it suddendly says that the port is closed.
Then if I stop the loading of the page/close the tab, and check if the port is open. It says that the port is open again.
I have an RT-N12D1 router.
My ISP also says the both ports should be able to be connected to/open
Disabling the firewall in the routers settings stopped the port from closing automatically.
Related
I'm running a FTB Revelation server on my Synology-NAS and I can connect in the intranet, but when my friends or I want to connect with my public-ip, they can't connect.
A portforwading tester says, that the port is closed.
I'm using a fritzbox and my ports are opened.
What could be the problem?
I had this issue too. You probably need to call your Internet Provider and ask if you have a dedicated IP. Port forwarding for ipv4 only works with dedicated IPs.
You can use NGROK (https://ngrok.com/) to "bypass" port forwarding, but server's IP will change every time you restart NGROK, and you will not be able to see player's true IPs in the server (You will see, for example, 0:0:0:0:0:0:0 instead of 93.22.22.22)
I am using Windows 10 with IIS 10.0
I am publishing website on IIS and I need to reach it with public ip.
What I did;
* Port forwarding through router
* Adding DMZ with my local IP
* Turning off firewall
* Adding port to firewall inbound rules with allow edge traversal
I can connect with internal IP like 192.168.1.75:81
I get "System.Net.Sockets.SocketException A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond from [MYPUBLICIP]" when I try to reach it like MYPUBLICIP:81
What are the possible scenarios that blocks to port?
Thanks.
As far as I know, the error message means there is no server listening at specified ip/port that you are trying to connect to.
In my opinion, you should firstly make sure your client machine could access your server by using this MYPUBLICIP address.
Then I suggest you could try to make sure the port 81 is your IIS web application port.
Besides, I suggest you could try to open your event viewer to find out the details error message.
i have few questions..
I am using Windows7 and I just wanted to open telnet port.
So, I did check telnet client box and open telnet port(23) on the firewall
and I did open command box and typing netstat-an but, I could't find the telnet port
What is the wrong with it??
Did I wrong to do?
help me out...
You allowed services/daemon to listen (receive TCP packages) on this port. But there is no service running, so netstat-an got nothing to show.
I'm using a dedicated server on aruba with ZyWall firewall. I have two ports listening in the server, using telnet from inside I can connect to both the ports. If I try to telnet from outside I can access only to one of them.
I have not internal firewall, and I don't understand how I can see if the ZyWall is blocking the port access or it is forwarding all connections to that port to another ip.
Have you any suggestion?
I found the solution. I accessed the firewall web interface from a firefox installed in the dedicated server behind the firewall (the web interface is not accessible from outside), then I made two steps:
I added a rule on which I permit the access to the target port. I made this using the "Service" tab in the Security->Firewall menù.
In the matrix between LAN, WAN, DMZ etc.. I modified the rule "from WAN to LAN" and I added the rule made in the previous step.
Now it works!
Hi I'm receiving an SSL issue on my rails app on my local server:
An error occurred during a connection to localhost:3000.
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)
and was told that opening port 443 would fix the problem. I've looked around everywhere but there doesn't seem to be an answer. Could someone go through the process of how I would open port 443?
So, someone is advising you to open that port in your firewall. I don't think this will help, since you're connecting to port 3000, but it might be that you're running a proxy on port 3000 that needs to connect to port 443.
Instead of opening that port I would suggest disabling your firewall and retrying that. If it works, then you should look into making an exception for that port. Here's how to disable the firewall: (Which will open that port)
Open System Preferences->Security->Firewall and click "Stop". Don't forget to turn it back on when you're done testing.