Ubuntu

Unable to ssh to a remote computer (works on one client not another)

Asked by Rob Schneider

Yesterday this worked fine, today it does not. On a Ubuntu client machine. No changes to system since yesterday. Trying to ssh -l userid server.name.com to a remote serveer. I get a timeout error. I run -vv and it stalls at the fourth step "Connecting to server.name.com", followed by "Connection Timed Out".

Yet, I try the same command from a Mac running OS/X which is located on the same network using the same outbound broadband router, Mac promptly connects to the remote server.

Any thoughts on what could be wrong with the Ubuntu machine and why it "suddenly" stopped?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Rob Schneider
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

can the troublesome PC ping the server by name?
can the troublesome PC ping the server by IP?
does the troubesome PC connect to more than 1 network?
does the troubesome PC connect to the internet ok?

Revision history for this message
Rob Schneider (rmschne) said : 		#2

Oops. Should have put answers to these questions on original posting. I did check this.

The answer is yes to all questions.

I use the "troublesome PC" (I love that phrasing..well done!) as a server machine an an logging into it via ssh. I confirmed it's network connectivity by pinging and using lynx to connect to google.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

If the troubesome system is on 2 networks you may need to add a route to tell the system to shove the ssh request down the right interface to get to the server.

The command might be:

sudo route add ip.of.ssh.server eth0

replace eth0 with the interface needed and obviously change the IP address. You should hunt around to make sure I got the command right but its something not too dissimilar

Peace

Revision history for this message
Rob Schneider (rmschne) said : 		#4

The troublesome system is not on to networks.

Problem resolved (mostly). Turns out that the DNS settings for the troublesome PC were out of date. I did not now that since it's a server machine I never use for desktop use. I used Lynx to confirm that I could get a connection to Google. Instead, a message from my ISP was presented which pointed out that I was using "legacy" DNS. Have changed to their DNS settings and also to Googles (for tertiary DNS), and it now allows login.

I'm guessing that yesterday these DNS machines at the ISP were shut-down or something. Dunno.

How this works even when I used the IP address to login is still a mystery. but I'll not worry it for the time-being.

Thanks.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#5

You said it was:

"
actionparsnip said 33 minutes ago:
can the troublesome PC ping the server by name?
can the troublesome PC ping the server by IP?
does the troubesome PC connect to more than 1 network?
does the troubesome PC connect to the internet ok?

Rob Schneider said 25 minutes ago:
Oops. Should have put answers to these questions on original posting. I did check this.

The answer is yes to all questions.
"

Plase give accurate information in future. Glad you got the gold
=D