Ubuntu Server SSH 16.04 “no route to host”
up vote
0
down vote
favorite
I have a fresh install of Ubuntu server 16.04,
I have setup static ip
I have set up ssh, I can connect from LAN fine, but whenever I try and connect externally I get error "failed to connect to 81.159.21.93: no route to host"
I can ping the server fine externally and have disable UFW. I have added port forwarding to the router and check forums but cannot find a solution.
I am trying to connect directly using the public ip.
I feel like I am probably doing something stupid, maybe someone can help.
> `~$ ifconfig
enp3s0 Link encap:Ethernet HWaddr 00:1b:78:9d:c9:62
inet addr:192.168.1.96 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:78ff:fe9d:c962/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5098 errors:0 dropped:0 overruns:0 frame:0
TX packets:1429 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1476981 (1.4 MB) TX bytes:263130 (263.1 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:6122 errors:0 dropped:0 overruns:0 frame:0
TX packets:6122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:385128 (385.1 KB) TX bytes:385128 (385.1 KB)`
networking server ssh configuration connection
asked Nov 23 at 14:18
Andy EcoNat
1
add a comment |
up vote
0
down vote
favorite
I have a fresh install of Ubuntu server 16.04,
I have setup static ip
I have set up ssh, I can connect from LAN fine, but whenever I try and connect externally I get error "failed to connect to 81.159.21.93: no route to host"
I can ping the server fine externally and have disable UFW. I have added port forwarding to the router and check forums but cannot find a solution.
I am trying to connect directly using the public ip.
I feel like I am probably doing something stupid, maybe someone can help.
> `~$ ifconfig
enp3s0 Link encap:Ethernet HWaddr 00:1b:78:9d:c9:62
inet addr:192.168.1.96 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:78ff:fe9d:c962/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5098 errors:0 dropped:0 overruns:0 frame:0
TX packets:1429 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1476981 (1.4 MB) TX bytes:263130 (263.1 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:6122 errors:0 dropped:0 overruns:0 frame:0
TX packets:6122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:385128 (385.1 KB) TX bytes:385128 (385.1 KB)`
networking server ssh configuration connection
asked Nov 23 at 14:18
Andy EcoNat
1
Since you can connect from within the LAN, your Ubuntu system (and your server) seem to be clearly working properly. Troubleshooting your router settings and other network quirks do not seem Ubuntu-related.
– user535733
Nov 23 at 14:47
That was my initial thought, However I previously had ubuntu 18 on this machine and I could connect fine through the same network. I can also ping the machine ok from external. I feel I messed something up when configuring static IP.
– Andy EcoNat
yesterday
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a fresh install of Ubuntu server 16.04,
I have setup static ip
I have set up ssh, I can connect from LAN fine, but whenever I try and connect externally I get error "failed to connect to 81.159.21.93: no route to host"
I can ping the server fine externally and have disable UFW. I have added port forwarding to the router and check forums but cannot find a solution.
I am trying to connect directly using the public ip.
I feel like I am probably doing something stupid, maybe someone can help.
> `~$ ifconfig
enp3s0 Link encap:Ethernet HWaddr 00:1b:78:9d:c9:62
inet addr:192.168.1.96 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:78ff:fe9d:c962/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5098 errors:0 dropped:0 overruns:0 frame:0
TX packets:1429 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1476981 (1.4 MB) TX bytes:263130 (263.1 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:6122 errors:0 dropped:0 overruns:0 frame:0
TX packets:6122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:385128 (385.1 KB) TX bytes:385128 (385.1 KB)`
networking server ssh configuration connection
asked Nov 23 at 14:18
Andy EcoNat
1
I have a fresh install of Ubuntu server 16.04,
I have setup static ip
I have set up ssh, I can connect from LAN fine, but whenever I try and connect externally I get error "failed to connect to 81.159.21.93: no route to host"
I can ping the server fine externally and have disable UFW. I have added port forwarding to the router and check forums but cannot find a solution.
I am trying to connect directly using the public ip.
I feel like I am probably doing something stupid, maybe someone can help.
> `~$ ifconfig
enp3s0 Link encap:Ethernet HWaddr 00:1b:78:9d:c9:62
inet addr:192.168.1.96 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:78ff:fe9d:c962/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5098 errors:0 dropped:0 overruns:0 frame:0
TX packets:1429 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1476981 (1.4 MB) TX bytes:263130 (263.1 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:6122 errors:0 dropped:0 overruns:0 frame:0
TX packets:6122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:385128 (385.1 KB) TX bytes:385128 (385.1 KB)`
networking server ssh configuration connection
networking server ssh configuration connection
asked Nov 23 at 14:18
Andy EcoNat
1
asked Nov 23 at 14:18
Andy EcoNat
1
asked Nov 23 at 14:18
Andy EcoNat
1
asked Nov 23 at 14:18
Andy EcoNat
1
asked Nov 23 at 14:18
Andy EcoNat
1
1
Since you can connect from within the LAN, your Ubuntu system (and your server) seem to be clearly working properly. Troubleshooting your router settings and other network quirks do not seem Ubuntu-related.
– user535733
Nov 23 at 14:47
That was my initial thought, However I previously had ubuntu 18 on this machine and I could connect fine through the same network. I can also ping the machine ok from external. I feel I messed something up when configuring static IP.
– Andy EcoNat
yesterday
add a comment |
Since you can connect from within the LAN, your Ubuntu system (and your server) seem to be clearly working properly. Troubleshooting your router settings and other network quirks do not seem Ubuntu-related.
– user535733
Nov 23 at 14:47
That was my initial thought, However I previously had ubuntu 18 on this machine and I could connect fine through the same network. I can also ping the machine ok from external. I feel I messed something up when configuring static IP.
– Andy EcoNat
yesterday
Since you can connect from within the LAN, your Ubuntu system (and your server) seem to be clearly working properly. Troubleshooting your router settings and other network quirks do not seem Ubuntu-related.
– user535733
Nov 23 at 14:47
Since you can connect from within the LAN, your Ubuntu system (and your server) seem to be clearly working properly. Troubleshooting your router settings and other network quirks do not seem Ubuntu-related.
– user535733
Nov 23 at 14:47
That was my initial thought, However I previously had ubuntu 18 on this machine and I could connect fine through the same network. I can also ping the machine ok from external. I feel I messed something up when configuring static IP.
– Andy EcoNat
yesterday
That was my initial thought, However I previously had ubuntu 18 on this machine and I could connect fine through the same network. I can also ping the machine ok from external. I feel I messed something up when configuring static IP.
– Andy EcoNat
yesterday
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1095395%2fubuntu-server-ssh-16-04-no-route-to-host%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Since you can connect from within the LAN, your Ubuntu system (and your server) seem to be clearly working properly. Troubleshooting your router settings and other network quirks do not seem Ubuntu-related.
– user535733
Nov 23 at 14:47
That was my initial thought, However I previously had ubuntu 18 on this machine and I could connect fine through the same network. I can also ping the machine ok from external. I feel I messed something up when configuring static IP.
– Andy EcoNat
yesterday