ssh doesnot work with wifi but work fine with wired connection
I have Ubuntu 13.10.
I use ssh to connect to a remote computer in the university using ssh xxxx@ws.hpc.unipg.it. It is working fine when I am using wired connection but when I try to connect through wifi using the same command it doesn’t work and gives me this error :
ssh: connect to host ws.hpc.unipg.it port 22: No route to host
I hope that someone can help me.
wireless ssh
edited Dec 22 '13 at 15:52
falconer
12.3k22653
asked Dec 22 '13 at 15:01
user227849user227849
612
add a comment |
I have Ubuntu 13.10.
I use ssh to connect to a remote computer in the university using ssh xxxx@ws.hpc.unipg.it. It is working fine when I am using wired connection but when I try to connect through wifi using the same command it doesn’t work and gives me this error :
ssh: connect to host ws.hpc.unipg.it port 22: No route to host
I hope that someone can help me.
wireless ssh
edited Dec 22 '13 at 15:52
falconer
12.3k22653
asked Dec 22 '13 at 15:01
user227849user227849
612
When you're connected to WiFi, can you access the internet? Give us some context on the difference between the WiFi and wired connection. For example, are both at your home? Or is the WiFi somewhere else?
– Alaa Ali
Dec 22 '13 at 15:08
add a comment |
I have Ubuntu 13.10.
I use ssh to connect to a remote computer in the university using ssh xxxx@ws.hpc.unipg.it. It is working fine when I am using wired connection but when I try to connect through wifi using the same command it doesn’t work and gives me this error :
ssh: connect to host ws.hpc.unipg.it port 22: No route to host
I hope that someone can help me.
wireless ssh
edited Dec 22 '13 at 15:52
falconer
12.3k22653
asked Dec 22 '13 at 15:01
user227849user227849
612
I have Ubuntu 13.10.
I use ssh to connect to a remote computer in the university using ssh xxxx@ws.hpc.unipg.it. It is working fine when I am using wired connection but when I try to connect through wifi using the same command it doesn’t work and gives me this error :
ssh: connect to host ws.hpc.unipg.it port 22: No route to host
I hope that someone can help me.
wireless ssh
wireless ssh
edited Dec 22 '13 at 15:52
falconer
12.3k22653
asked Dec 22 '13 at 15:01
user227849user227849
612
edited Dec 22 '13 at 15:52
falconer
12.3k22653
asked Dec 22 '13 at 15:01
user227849user227849
612
edited Dec 22 '13 at 15:52
falconer
12.3k22653
edited Dec 22 '13 at 15:52
falconer
12.3k22653
edited Dec 22 '13 at 15:52
falconer
12.3k22653
12.3k22653
asked Dec 22 '13 at 15:01
user227849user227849
612
asked Dec 22 '13 at 15:01
user227849user227849
612
asked Dec 22 '13 at 15:01
user227849user227849
612
612
When you're connected to WiFi, can you access the internet? Give us some context on the difference between the WiFi and wired connection. For example, are both at your home? Or is the WiFi somewhere else?
– Alaa Ali
Dec 22 '13 at 15:08
add a comment |
When you're connected to WiFi, can you access the internet? Give us some context on the difference between the WiFi and wired connection. For example, are both at your home? Or is the WiFi somewhere else?
– Alaa Ali
Dec 22 '13 at 15:08
When you're connected to WiFi, can you access the internet? Give us some context on the difference between the WiFi and wired connection. For example, are both at your home? Or is the WiFi somewhere else?
– Alaa Ali
Dec 22 '13 at 15:08
When you're connected to WiFi, can you access the internet? Give us some context on the difference between the WiFi and wired connection. For example, are both at your home? Or is the WiFi somewhere else?
– Alaa Ali
Dec 22 '13 at 15:08
add a comment |
2 Answers
2
active
oldest
votes
Assuming your wifi is working, this probably means the ssh port is blocked on the wifi network. Or possibly that there is a firewall in front of the server which doesn't recognise the wifi IP addresses as valid.
It's possible that you are on some kind of guest wifi network, and you might be able to get better access by registering for another wifi network.
answered Dec 22 '13 at 15:16
Robin GreenRobin Green
4301523
add a comment |
It means that you don't have internet in your wifi (or at least, that host isn't accessible from your wifi). So, how to diagnostics? You can use ping and nmap, but let me tell you, apparently that host isn't public available:
ping -c2 ws.hpc.unipg.it
PING ws.hpc.unipg.it (141.250.16.254) 56(84) bytes of data.
--- ws.hpc.unipg.it ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1008ms
Here it said that the host didn't asnwer my pings
nmap -p22 ws.hpc.unipg.it
Starting Nmap 6.40 ( http://nmap.org ) at 2013-12-22 11:10 AST
Stats: 0:00:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 50.00% done; ETC: 11:10 (0:00:01 remaining)
Nmap scan report for ws.hpc.unipg.it (141.250.16.254)
Host is up (0.19s latency).
rDNS record for 141.250.16.254: gw.hpc.unipg.it
PORT STATE SERVICE
22/tcp filtered ssh
Nmap done: 1 IP address (1 host up) scanned in 2.34 seconds
Here it says that the port is filtered (it could be dropping my packets), hence is very likely I can't connect. When I try to connect, it will timeout my request. So, how to solve this? Contact your system administrator for guidance.
answered Dec 22 '13 at 15:16
BraiamBraiam
51.7k20136221
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f394345%2fssh-doesnot-work-with-wifi-but-work-fine-with-wired-connection%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Assuming your wifi is working, this probably means the ssh port is blocked on the wifi network. Or possibly that there is a firewall in front of the server which doesn't recognise the wifi IP addresses as valid.
It's possible that you are on some kind of guest wifi network, and you might be able to get better access by registering for another wifi network.
answered Dec 22 '13 at 15:16
Robin GreenRobin Green
4301523
add a comment |
Assuming your wifi is working, this probably means the ssh port is blocked on the wifi network. Or possibly that there is a firewall in front of the server which doesn't recognise the wifi IP addresses as valid.
It's possible that you are on some kind of guest wifi network, and you might be able to get better access by registering for another wifi network.
answered Dec 22 '13 at 15:16
Robin GreenRobin Green
4301523
add a comment |
Assuming your wifi is working, this probably means the ssh port is blocked on the wifi network. Or possibly that there is a firewall in front of the server which doesn't recognise the wifi IP addresses as valid.
It's possible that you are on some kind of guest wifi network, and you might be able to get better access by registering for another wifi network.
answered Dec 22 '13 at 15:16
Robin GreenRobin Green
4301523
Assuming your wifi is working, this probably means the ssh port is blocked on the wifi network. Or possibly that there is a firewall in front of the server which doesn't recognise the wifi IP addresses as valid.
It's possible that you are on some kind of guest wifi network, and you might be able to get better access by registering for another wifi network.
answered Dec 22 '13 at 15:16
Robin GreenRobin Green
4301523
answered Dec 22 '13 at 15:16
Robin GreenRobin Green
4301523
answered Dec 22 '13 at 15:16
Robin GreenRobin Green
4301523
answered Dec 22 '13 at 15:16
Robin GreenRobin Green
4301523
4301523
add a comment |
add a comment |
It means that you don't have internet in your wifi (or at least, that host isn't accessible from your wifi). So, how to diagnostics? You can use ping and nmap, but let me tell you, apparently that host isn't public available:
ping -c2 ws.hpc.unipg.it
PING ws.hpc.unipg.it (141.250.16.254) 56(84) bytes of data.
--- ws.hpc.unipg.it ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1008ms
Here it said that the host didn't asnwer my pings
nmap -p22 ws.hpc.unipg.it
Starting Nmap 6.40 ( http://nmap.org ) at 2013-12-22 11:10 AST
Stats: 0:00:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 50.00% done; ETC: 11:10 (0:00:01 remaining)
Nmap scan report for ws.hpc.unipg.it (141.250.16.254)
Host is up (0.19s latency).
rDNS record for 141.250.16.254: gw.hpc.unipg.it
PORT STATE SERVICE
22/tcp filtered ssh
Nmap done: 1 IP address (1 host up) scanned in 2.34 seconds
Here it says that the port is filtered (it could be dropping my packets), hence is very likely I can't connect. When I try to connect, it will timeout my request. So, how to solve this? Contact your system administrator for guidance.
answered Dec 22 '13 at 15:16
BraiamBraiam
51.7k20136221
add a comment |
It means that you don't have internet in your wifi (or at least, that host isn't accessible from your wifi). So, how to diagnostics? You can use ping and nmap, but let me tell you, apparently that host isn't public available:
ping -c2 ws.hpc.unipg.it
PING ws.hpc.unipg.it (141.250.16.254) 56(84) bytes of data.
--- ws.hpc.unipg.it ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1008ms
Here it said that the host didn't asnwer my pings
nmap -p22 ws.hpc.unipg.it
Starting Nmap 6.40 ( http://nmap.org ) at 2013-12-22 11:10 AST
Stats: 0:00:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 50.00% done; ETC: 11:10 (0:00:01 remaining)
Nmap scan report for ws.hpc.unipg.it (141.250.16.254)
Host is up (0.19s latency).
rDNS record for 141.250.16.254: gw.hpc.unipg.it
PORT STATE SERVICE
22/tcp filtered ssh
Nmap done: 1 IP address (1 host up) scanned in 2.34 seconds
Here it says that the port is filtered (it could be dropping my packets), hence is very likely I can't connect. When I try to connect, it will timeout my request. So, how to solve this? Contact your system administrator for guidance.
answered Dec 22 '13 at 15:16
BraiamBraiam
51.7k20136221
add a comment |
It means that you don't have internet in your wifi (or at least, that host isn't accessible from your wifi). So, how to diagnostics? You can use ping and nmap, but let me tell you, apparently that host isn't public available:
ping -c2 ws.hpc.unipg.it
PING ws.hpc.unipg.it (141.250.16.254) 56(84) bytes of data.
--- ws.hpc.unipg.it ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1008ms
Here it said that the host didn't asnwer my pings
nmap -p22 ws.hpc.unipg.it
Starting Nmap 6.40 ( http://nmap.org ) at 2013-12-22 11:10 AST
Stats: 0:00:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 50.00% done; ETC: 11:10 (0:00:01 remaining)
Nmap scan report for ws.hpc.unipg.it (141.250.16.254)
Host is up (0.19s latency).
rDNS record for 141.250.16.254: gw.hpc.unipg.it
PORT STATE SERVICE
22/tcp filtered ssh
Nmap done: 1 IP address (1 host up) scanned in 2.34 seconds
Here it says that the port is filtered (it could be dropping my packets), hence is very likely I can't connect. When I try to connect, it will timeout my request. So, how to solve this? Contact your system administrator for guidance.
answered Dec 22 '13 at 15:16
BraiamBraiam
51.7k20136221
It means that you don't have internet in your wifi (or at least, that host isn't accessible from your wifi). So, how to diagnostics? You can use ping and nmap, but let me tell you, apparently that host isn't public available:
ping -c2 ws.hpc.unipg.it
PING ws.hpc.unipg.it (141.250.16.254) 56(84) bytes of data.
--- ws.hpc.unipg.it ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1008ms
Here it said that the host didn't asnwer my pings
nmap -p22 ws.hpc.unipg.it
Starting Nmap 6.40 ( http://nmap.org ) at 2013-12-22 11:10 AST
Stats: 0:00:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 50.00% done; ETC: 11:10 (0:00:01 remaining)
Nmap scan report for ws.hpc.unipg.it (141.250.16.254)
Host is up (0.19s latency).
rDNS record for 141.250.16.254: gw.hpc.unipg.it
PORT STATE SERVICE
22/tcp filtered ssh
Nmap done: 1 IP address (1 host up) scanned in 2.34 seconds
Here it says that the port is filtered (it could be dropping my packets), hence is very likely I can't connect. When I try to connect, it will timeout my request. So, how to solve this? Contact your system administrator for guidance.
answered Dec 22 '13 at 15:16
BraiamBraiam
51.7k20136221
answered Dec 22 '13 at 15:16
BraiamBraiam
51.7k20136221
answered Dec 22 '13 at 15:16
BraiamBraiam
51.7k20136221
answered Dec 22 '13 at 15:16
BraiamBraiam
51.7k20136221
51.7k20136221
add a comment |
add a comment |
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.
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%2f394345%2fssh-doesnot-work-with-wifi-but-work-fine-with-wired-connection%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
When you're connected to WiFi, can you access the internet? Give us some context on the difference between the WiFi and wired connection. For example, are both at your home? Or is the WiFi somewhere else?
– Alaa Ali
Dec 22 '13 at 15:08