Unable to connect to public IP

[MewingFugur]

So I've read these forums for years but never had to post until now. I recently got a raspberry pi and setup several basic servers (ftp, vnc, ssh tunneling, etc) and can connect to it perfectly fine while on the network. But I wanted to connect to it remotely by port forwarding and connecting to my public ip address but I am encountering problems. I've verified my public ip through various methods including the basic websites like whatsmyip.org but whenever I try to connect to my network through any means it simply doesn't connect. I've even try pinging my public ip and have 100% packet loss. And before anyone asks, yes I am on a separate network when attempting to connect. Any thoughts or ideas that I'm skipping over? Thanks in advance, I'm somewhat new to this stuff.

 

[BuddhaSkoota]

So I've read these forums for years but never had to post until now. I recently got a raspberry pi and setup several basic servers (ftp, vnc, ssh tunneling, etc) and can connect to it perfectly fine while on the network. But I wanted to connect to it remotely by port forwarding and connecting to my public ip address but I am encountering problems. I've verified my public ip through various methods including the basic websites like whatsmyip.org but whenever I try to connect to my network through any means it simply doesn't connect. I've even try pinging my public ip and have 100% packet loss. And before anyone asks, yes I am on a separate network when attempting to connect. Any thoughts or ideas that I'm skipping over? Thanks in advance, I'm somewhat new to this stuff.

Check the IP address assigned to the WAN side of your network in the router (modem/router) GUI. It should be a public IP address that matches the address found on whatsmyip.org.

If it doesn't match, your ISP may be assigning you a private IP. It is entirely dependent on the ISP's architecture and how they deliver your service (MIFI, WISP, or shared/private network). You won't be able to establish a server based on IP address.

If it does match, your router or ISP may be blocking ping or other incoming requests. You should provide specifics about your ISP and modem/router, and any other relevant details about your network.

 

[MewingFugur]

So I've read these forums for years but never had to post until now. I recently got a raspberry pi and setup several basic servers (ftp, vnc, ssh tunneling, etc) and can connect to it perfectly fine while on the network. But I wanted to connect to it remotely by port forwarding and connecting to my public ip address but I am encountering problems. I've verified my public ip through various methods including the basic websites like whatsmyip.org but whenever I try to connect to my network through any means it simply doesn't connect. I've even try pinging my public ip and have 100% packet loss. And before anyone asks, yes I am on a separate network when attempting to connect. Any thoughts or ideas that I'm skipping over? Thanks in advance, I'm somewhat new to this stuff.

Check the IP address assigned to the WAN side of your network in the router (modem/router) GUI. It should be a public IP address that matches the address found on whatsmyip.org.

If it doesn't match, your ISP may be assigning you a private IP. It is entirely dependent on the ISP's architecture and how they deliver your service (MIFI, WISP, or shared/private network). You won't be able to establish a server based on IP address.

If it does match, your router or ISP may be blocking ping or other incoming requests. You should provide specifics about your ISP and modem/router, and any other relevant details about your network.

So I checked my modem's page and it does match the same IP address as whatsmyip gives me. I have a ATT Netgear 7550 which ATT (my ISP) provided me with. I'm not sure what all other details I should provide, so let me know and I'll find them.

 

[BuddhaSkoota]

So I checked my modem's page and it does match the same IP address as whatsmyip gives me. I have a ATT Netgear 7550 which ATT (my ISP) provided me with. I'm not sure what all other details I should provide, so let me know and I'll find them.

The 100% packet loss indicates the router can't be reached from the Internet, is set to not reply to ping requests, or ISP is blocking ping requests. I'd suggest looking in the router settings to determine if anything is set to deny requests (ping or ICMP).

Have you forwarded the FTP port on your router to the RaberryPi's IP address? Have you attempted to reach the RasberryPi's FTP service?

 

[MewingFugur]

So I checked my modem's page and it does match the same IP address as whatsmyip gives me. I have a ATT Netgear 7550 which ATT (my ISP) provided me with. I'm not sure what all other details I should provide, so let me know and I'll find them.

The 100% packet loss indicates the router can't be reached from the Internet, is set to not reply to ping requests, or ISP is blocking ping requests. I'd suggest looking in the router settings to determine if anything is set to deny requests (ping or ICMP).

Have you forwarded the FTP port on your router to the RaberryPi's IP address? Have you attempted to reach the RasberryPi's FTP service?

So with your help, I managed to fix it! Thanks! I found a setting that was indeed blocking ping attempts to its public address so I unchecked it and that fixed the pinging problem. Next I realized that the reason none of my port forwards were working was because I had another (better) router plugged up before handing out IP address to each device on the network. So I had to forward ports to the router then to the raspberry pi instead of directly to the raspberry pi. I don't know if I did it the most efficient way, but it works so I'm not complaining. I can't believe I totally forgot about the other router but oh well. Thanks for the guidance.