Question Help with port forwarding

[fmahannah]

For work I need to host Coldfusion Performance Monitor on my home server to monitor a clients server hosted on AWS. All ports required are open on all firewalls. I have my kinetic router forwarding the ports to my internal network IP from my public IP.

The problem is that the software on my machine needs to listen on the internal IP and publish on the public IP, but also part of the software on my machine needs to be able to send data to the public IP.

From the AWS server I can reach my public IP on the ports needed with no issues (9250 and 9350).

But from my server I need to be able to use the public IP to reach port 9250 and for some reason this fails. Could it be because it creates some sort of loop because of the port forwarding?

Even stranger on my local machine I can use the public IP for ports 80 and 443 with no issues, but it just does not work
for ports 9250 and 9350 even though they are open on my windows firewall and on the router firewall? The only difference
is the 80 and 443 re not being forwarded.

So is there any way to have a port fowarded from a public IP to an internal IP and still be able to reach that port on the same machine using the PUBLIC ip?

Thanks for any help or direction offered. Even stranger this worked before on this same machine with the only difference being that kinetic changed my router.

Just to simplify say on my local server I have a public IP and internal IP.
Remote server can reach port 9250 over my public IP no problem with port forwarding turned on
Local server can't reach port 9250 using my public IP for some reason and the software I am trying to set up requires this part to work.

So remote server to 9250 over public IP works
Local server to 9250 over public IP does not work
Local server to 9250 over internal Ip works, but this will not work for the software in question

Thanks

 

[kanewolf]

For work I need to host Coldfusion Performance Monitor on my home server to monitor a clients server hosted on AWS. All ports required are open on all firewalls. I have my kinetic router forwarding the ports to my internal network IP from my public IP.

The problem is that the software on my machine needs to listen on the internal IP and publish on the public IP, but also part of the software on my machine needs to be able to send data to the public IP.

From the AWS server I can reach my public IP on the ports needed with no issues (9250 and 9350).

But from my server I need to be able to use the public IP to reach port 9250 and for some reason this fails. Could it be because it creates some sort of loop because of the port forwarding?

Even stranger on my local machine I can use the public IP for ports 80 and 443 with no issues, but it just does not work
for ports 9250 and 9350 even though they are open on my windows firewall and on the router firewall? The only difference
is the 80 and 443 re not being forwarded.

So is there any way to have a port fowarded from a public IP to an internal IP and still be able to reach that port on the same machine using the PUBLIC ip?

Thanks for any help or direction offered. Even stranger this worked before on this same machine with the only difference being that kinetic changed my router.

Just to simplify say on my local server I have a public IP and internal IP.
Remote server can reach port 9250 over my public IP no problem with port forwarding turned on
Local server can't reach port 9250 using my public IP for some reason and the software I am trying to set up requires this part to work.

So remote server to 9250 over public IP works
Local server to 9250 over public IP does not work
Local server to 9250 over internal Ip works, but this will not work for the software in question

Thanks

Not all routers support what is called "hairpin NAT". That is the function to use the public IP address from the NAT'ed local IP address space.
What router do you have ?
Also remember that most home public IP addresses CAN CHANGE over time and that you need to setup a DDNS url to handle this.

 

[fmahannah]

My router is from windstream/kinetic and is a T3280.

I did a test by setting up DMZ and it still did not allow my local machine to reach 9250 using Test-Netconnection with the public IP.

I know my IP can change. I had the software working before on this same home server until windstream changed my router to the T3280

Thanks

 

[kanewolf]

My router is from windstream/kinetic and is a T3280.

I did a test by setting up DMZ and it still did not allow my local machine to reach 9250 using Test-Netconnection with the public IP.

I know my IP can change. I had the software working before on this same home server until windstream changed my router to the T3280

Thanks

If the router doesn't support hairpin NAT, you may have no choice but to replace the router.
That router can support bridge mode (act like a modem only) so that you can put ANY router behind it. It is also possible your ISP has disabled this capability.
Here is the how-to from the manufacturer -- https://business.windstream.com/support/business-solutions/modem/bridging-my-modem