I have problem connecting server that is in internal network(e.g wifi network).Im using rad studio idtcpclient
IdTcpClient1.Host:='ip'
IdTcpClient1.Connect;
But with what I need replace ip to connect this server?
If the client is inside the same WiFi network as the server, the client can connect to the server's LAN IP address directly.
If the client is outside of the WiFi network, the client cannot connect to the server's LAN IP address directly. It must connect to the WiFi router's public WAN IP instead, and the router must be configured with port forwarding enabled to pass inbound connections to the server. If the router supports uPNP, the server app can dynamically create port forwarding rules for itself, otherwise the router admin must configure them manually.
Related
I have Wamp 3.1.7 running on a Windows 10 machine. The goal is to have the projects on this server accessible via the internet.
The server is available and working as expected over LAN when accessed with the LAN IP, e.g.
http://10.0.0.3/.
The server runs behind my router, which has its web interface running on port 80, so when I access my public IP, traffic on port 80 goes to the router login page.
Steps taken to try and solve the issue:
change the port my server is listening to from 80 to 8080. (this is working, both locally and over LAN, accessed with http://10.0.0.3:8080)
Add inbound rules on windows firewall for port 8080, set to allow all.
Add port forwarding on the router settings (forward incoming traffic on port 8080 to local IP 10.0.0.3:8080 as per https://portforward.com/d-link/dsl-g2562dg/)
Using PFPortChecker, it says that port 8080 on public_ip is open and able to send data.
I remain unable to access my server. When I go to public_ip:8080, I get ERR_CONNECTION_TIMED_OUT.
As stated above, going to public_ip just displays the router login page.
So as far as I can tell: port 8080 is open, my server is accessible over LAN on port 8080.
What am I missing? Where else could my traffic be blocked?
Stupid mistake on my side.
Answer found here: Public IP Web Page "Connection Timed Out" When Connected To
The issue was that you cannot access the server with the public_ip if connected the LAN the server is running on.
I have an ASP.Net MVC project that is running under IIS. I can reach it using local IP and port. I bind it with my IP and port.
What should I do to reach it with my public IP and port like http://PUBLICIP:PORT
When I try to reach it says connection error with code 502.
This is what I tried so far.
Adding my local IP to router's DMZ Adding
Port forwarding with port and my local IP
Add inbound and outbound rules to Firewall, inbound rules allow edge
traversal.
Turning off firewall, windows defender etc.
Do I need any features to install when I try to reach IIS externally?
Thanks all.
I'm trying to establish a connection with a diameter server. That server has a restriction parameter of "peer port"
Which means source port of my outgoing traffic should be restricted to a specific port.
Since I'm using an erlang diameter client, I didn't find any parameter to specify the outgoing port. It will initiate the connection with a random port to the destination ip:port.
Is there a way to translate my outgoing traffic to that ip locally to a specific port from linux?, so that the external server will see my source port as the allowed port.
You should apply a NAT at the sender side. Read this thread, it explains how to do it with iptables.
I cannot reach the Server using the IP-Adress, but if I use the FQDN or the hostname itself, the connection can be established.
My Firewalls are all disabled.
Which reasons could lead to this result?
I have a silverlight->server communication system up that uses port 4530 among others. I've used no-ip.org to redirect traffic to my home server. Is there anyway to use no-ip (or is there another service like it?) to allow me to ping off an ip at port 4530 etc, and send it to my dynamic ip?