I can successfully SSH into my server if I connect that PC directly to my ISP provided router (point 1 below), with port forwarding etc.
However I need to connect another router as an access point first, and then connect my server PC to that router(point 2 below).
Thus the connection changes from:
1. ISP router - LAN cable - Server PC
TO:
2. ISP router - LAN cable - access point router - LAN cable - Server PC.
I just plug the LAN cables in as in the second scenario above, and internet etc works on all my PC's, including the Server PC. I have tried changing IPv4 settings, port forwarding on both routers etc.
You either:
port forward (1) from your ISP router to your AP router and port forward (2) from your AP router to your sever PC (fixed IP)
or you inform the ISP router of the subnet created by the AP router, by adding the subnet to the ISP's routing table (if you've access to the routing table).
Or, unless you really need the AP to act as a router, check if you can configure it as a regular switch so the whole network will be one subnet. Doing so, you can stick to your initial setup.
Related
i know there are lots of similar questions about but no one help me.
I have a linux server running nginx reverse proxy in docker, a duckdns domain created,opened my router port 80 and 443. I can't access from outside with my domain name or public ip, it seems like my router refuses external request. I tried with lots of configuration, follow lots of guides on web... I get crazy to solve this problem.
I think problem is before nginx, so i not post my nginx conf. If can help, I will post it.
Hope someone can help me. Thank you so much
There are several things that could be causing the issue with your router refusing external requests. Here are a few things to check:
Make sure that your router's firewall is configured to allow incoming connections on ports 80 and 443. Some routers have a built-in firewall that needs to be configured to allow traffic through specific ports.
Confirm that your router is properly forwarding incoming requests to the correct IP address and port on your network. This is typically done through a feature called port forwarding.
Check your router's security settings to ensure that it is not blocking incoming requests based on the source IP address or domain name. Some routers have the option to block incoming requests from specific IP addresses or domain names.
Confirm that your Linux server is properly configured to handle incoming requests. This includes checking that your Nginx reverse proxy is running and properly configured to forward requests to the correct IP address and port.
Verify that your DNS is pointing to the right IP address, you can use online tools like https://www.whatsmydns.net/ to check this.
Check if your router have any VPN or proxy service enabled, which could be affecting the incoming request.
Check if your ISP is blocking incoming connection to your public IP address.
It's also possible that there might be a problem with your router's firmware or hardware, in that case, you may need to contact the manufacturer for further assistance.
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've fake IP in local network for some IOT, like 192.168.1.11, 192.168.1.15 etc. My LAN connect to Internet via provider with fake IP too, like 10.10.10.15. I've task connecting (REST) to my IOT-device through Internet. For that I want use DO droplet with real IP(for sample 178.62.209.11) and setup OpenVPN on it. For my home LAN I've buy the Mikrotik Router RB951Ui-2HnD which must allow setup the OpenVPN client. So, my LAN with DO Droplet must be VPN.
And now my question is how to do traffic translation from MY SERVER 178.62.209.11 to LOCAL device IOT 192.168.1.11? I understand that my server have only one IP, but I look that may be port forwording! For sample, if I want send request to my IOT device by 80 port, then I can use for that port forwards, like 178.62.209.11:1234 <=> 192.168.1.11:80, and for second IOT device 178.62.209.11:1235 <=> 192.168.1.15:80, and etc.
I found how to set OpenVPN to DO Droplet, I found how adjust OpenVPN client on the router, but can not found how get simple access to my device. Can you help?
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!