topic Re: Telnet error in Operating System - HP-UX

Telnet error

Grayh — Tue, 30 Sep 2008 15:37:32 GMT

I am able to telnet to the IP address of the sysrtem but however I cant telnet to the hostname

I have it in /etc/hosts and /etc/rc.config.d/netconf

Re: Telnet error

Alex Glennie — Tue, 30 Sep 2008 15:46:07 GMT

I suggest you post the error you recieve along with the output from

nslookup &
nslookup

also can you ping the remote servername ?

sounds like the error *could* be a dns issue if this is configured.

Also what's the contents of /etc/nsswitch.conf ?

lastly the entry from /etc/hosts.

Re: Telnet error

Ivan Krastev — Tue, 30 Sep 2008 15:47:21 GMT

If you want to telnet by name from server1 to server2 check for entry in /etc/hosts for server2.
Check also permissions of the /etc/hosts, /etc/resolv.conf, /etc/nsswitch.conf files.

regards,
ivan

Re: Telnet error

Gokul Chandola — Tue, 30 Sep 2008 15:48:43 GMT

Hi,
This is DNS clearly issue...
Or there is issue with routing..

Regards,
Gokul Chandola

Re: Telnet error

Ganesan R — Tue, 30 Sep 2008 16:01:51 GMT

Hi,

First thing you should check is /etc/nsswitch.conf. Look for the entry hosts. It will be like this..

hosts: files [NOTFOUND=continue] dns

if files is first, then add the entry in your local /etc/hosts file.

if dns is first the entry should be added in DNS server.

Change the /etc/nsswitch.conf as per your requirement.

Re: Telnet error

Grayh — Mon, 06 Oct 2008 16:04:11 GMT

# nslookup HP2087
Using /etc/hosts on: HP2087

looking up FILES
Name: HP2087
Address: 12.5.98.17

# nslookup 12.5.98.17
Using /etc/hosts on: HP2087

looking up FILES
Name: HP2087
Address: 10.3.90.98

# cd /etc
# ll nss*
-r--r--r-- 1 bin bin 566 Sep 3 2003 nsswitch.compat
-r--r--r-- 1 bin bin 391 Sep 3 2003 nsswitch.files
-r--r--r-- 1 bin bin 615 Sep 3 2003 nsswitch.hp_defaults
-r--r--r-- 1 bin bin 481 Apr 7 2005 nsswitch.ldap
-r--r--r-- 1 bin bin 551 Sep 3 2003 nsswitch.nis
-r--r--r-- 1 bin bin 604 Sep 3 2003 nsswitch.nisplus

I am still unable to telnet to the hostname... but able to telnet to the server ip

Re: Telnet error

OldSchool — Mon, 06 Oct 2008 16:28:42 GMT

"# nslookup HP2087
Using /etc/hosts on: HP2087

looking up FILES
Name: HP2087
Address: 12.5.98.17

# nslookup 12.5.98.17
Using /etc/hosts on: HP2087

looking up FILES
Name: HP2087
Address: 10.3.90.98"

OK, so you've two servers, HP2087 and FILES?

You did and nslookups above on HP2087?

I take it that "telnet FILES" is the one that doesn't work?

Telnet 10.3.90.98 does work?

In any event, get into the other server and do the nslookups there as well...post the results...

If you are supposed to be running DNS, then you will need to set up the nsswitch.conf file. You can use one of the existing ones as a model....

Then check the post above about the host file / dns issue from Ganesan.

Re: Telnet error

Torsten. — Mon, 06 Oct 2008 16:32:55 GMT

You did all this on the same host - but you cannot telnet from this host to itself?

Re: Telnet error

Grayh — Mon, 06 Oct 2008 16:38:29 GMT

telnet is working....

when I do telnet -->it works

When i do telnet ---->Dosen't work

Re: Telnet error

Torsten. — Mon, 06 Oct 2008 16:49:30 GMT

You are already on HP2087 and do

HP2087# telnet HP2087

What message do you get?

Re: Telnet error

Grayh — Mon, 06 Oct 2008 16:55:51 GMT

I am able to login when I do that

#telnet is working

#telnet is also working

Re: Telnet error

OldSchool — Mon, 06 Oct 2008 17:07:37 GMT

Once again:

I take it that "telnet FILES" is the one that doesn't work? and "telnet 10.3.90.98" does work?

In any event, get into the OTHER SERVER and do the nslookups there as well...post the results...

If you are supposed to be running DNS, then you will need to set up the nsswitch.conf file. You can use one of the existing ones as a model....

Then check the post above about the host file / dns issue from Ganesan.

Re: Telnet error

OldSchool — Mon, 06 Oct 2008 17:10:00 GMT

Once again:
I take it that "telnet FILES" is the one that doesn't work? and "telnet 10.3.90.98" does work?

In any event, get into the OTHER SERVER and do the nslookups there as well...post the results...

If you are supposed to be running DNS, then you will need to set up the nsswitch.conf file. You can use one of the existing ones as a model....

Then check the post above about the host file / dns issue from Ganesan.

Re: Telnet error

Grayh — Mon, 06 Oct 2008 17:37:31 GMT

Ok... Now I have logged into other server here also it is the same

# nslookup HP11
Using /etc/hosts on: HP11

looking up FILES
Name: HP11
Address: 10.3.90.98

# nslookup 10.3.90.98
Using /etc/hosts on: HP11

looking up FILES
Name: HP11
Address: 10.3.90.98

Actually FILES is not a server.. I have only one server here

Re: Telnet error

Torsten. — Mon, 06 Oct 2008 17:43:33 GMT

What I still not understand is - do you telnet

from server1 to server1

or

server1 to server2 ???

on server1 -> does nslookup server2 work?

(same for the other server?)

If not, check if server2 is in /etc/hosts of server1 and vice versa.

Re: Telnet error

OldSchool — Mon, 06 Oct 2008 17:56:07 GMT

okay, so the servers are:
HP2087 at ip 12.5.98.17 -and-
HP11 at ip 10.3.90.98 ?

and you can telnet from HP2087 to HP2087?
and you can telnet from HP2087 to 10.3.90.98?
and you *can't* telnet from HP2087 to HP11?

while logged in to HP2087:

nslookup HP11
nslookup 10.30.90.98

while logged in to HP11:

nslookup HP2087
nslookup 12.5.98.17

are you *supposed* to be running Domain Name Services as well?

Re: Telnet error

OldSchool — Mon, 06 Oct 2008 17:57:56 GMT

oh, yeah....one other point. as requested above:

*Exactly* what error message(s) do you get when *telnet doesn't work*?

Re: Telnet error

Grayh — Mon, 06 Oct 2008 17:59:49 GMT

I do not the want to telnet from server1 to server2....

on the windows cmd propmt... I type telnet hostname.... dosent work

telnet server ip works

Server 1#telnet server1 works
telnet hostanme works

Re: Telnet error

Torsten. — Mon, 06 Oct 2008 18:03:06 GMT

Now windows ????

You should really better explain the situation!

A windows PC will probably ask DNS to resolve the hostname.

Check with - guess what - nslookup from your PC!

If this gives no result -> DNS doesn't know your server -> use IP or make the server known to DNS!!!

Re: Telnet error

OldSchool — Mon, 06 Oct 2008 18:14:05 GMT

for purposes of this discussion....the windows box can be considered a server, a client or whatever.

The POINT is that your are telnet'ing between two boxes...not back to the client itself.... now if you would get on with answering the questions posed instead of arguing semantics, this might get fixed......

so.....on the windows box, when you do

telnet hostname

WHAT EXACTLY DOES IT SAY!!!

same for
nslookup hostname

and

ping hostname