Internet working, but intranet is not? (telnet/ssh issues)

R00ts · 02-11-2005, 04:31 PM

Short Version

This doesn't work:

Code:

pegasos@debian:~/metrix/results$ telnet p43-2
telnet: could not resolve p43-2/telnet: Name or service not known
pegasos@debian:~/metrix/results$ ssh p43-2
ssh: p43-2: Name or service not known

I can't figure out why. Help!

Detailed Version

I'm at work on a Debian PowerPC machine and I'm having trouble getting telnet or ssh to respond. This machine has two Debian distros, one with a 2.4.x kernel and one with a 2.6.x kernel. Previously the 2.6.x could not boot into gui, but could telnet/ssh onto other machines on our intranet. The 2.4.x kernel could boot into a gui, but had no net access (telnet/ssh, nor web browser capabilities). I did an apt-get upgrade from the 2.4.x kernel image (and there were *a lot* of packages outdated) and I updated them all.

Now the following happens:
2.4.x: still boots into gui, can access websites and other internet services. Can not telnet/ssh to machines
2.6.x: still can not boot into gui, and now also can not telnet/ssh to machines.

Here's the output:

Code:

pegasos@debian:~/metrix/results$ telnet p43-2
telnet: could not resolve p43-2/telnet: Name or service not known
pegasos@debian:~/metrix/results$ ssh p43-2
ssh: p43-2: Name or service not known

Even if I specify the full machine path-name (which I shouldn't have to), I get the same error. I googled and I couldn't find any solution to my problem. Can anyone provide me guidance? Thanks

PS: The reason I'm not asking the IT department is because this particular machine is for our group alone, and the IT dept. hasn't messed with it.

sigsegv · 02-11-2005, 05:08 PM

Quote:

Originally posted by R00ts
Even if I specify the full machine path-name (which I shouldn't have to), I get the same error. I googled and I couldn't find any solution to my problem. Can anyone provide me guidance?

Short version:
Your system's resolver is configured incorrectly

Detailed version:
You have to use the machines FQDN (Fully Qualified Domain Name -- path-names are a filesystem thing) unless you have a search domain(s) set in /etc/resolv.conf. This is the file that you need to start with. If you don't know how that file works, man resolv.conf

R00ts · 02-11-2005, 05:11 PM

Quote:

Originally posted by sigsegv
Short version:
Your system's resolver is configured incorrectly

Detailed version:
You have to use the machines FQDN (Fully Qualified Domain Name -- path-names are a filesystem thing) unless you have a search domain(s) set in /etc/resolv.conf. This is the file that you need to start with. If you don't know how that file works, man resolv.conf

I thought that I had already tried the FQDN before and it didn't work, but I just tried it in 2.4.x (GUI version) and it worked! Thanks a lot for your help.

I feel like an idiot now for not trying that eariler