topic Re: Name Resolution Problem in Operating System - HP-UX

Name Resolution Problem

Raj_58 — Tue, 01 Feb 2005 16:17:17 GMT

It looks like i have a name resolution problem. I was cleaning up my / and /usr, /var/tmp file systems as it was becoming full. And after an hour when i tried to ssh into that host, it gives some error like " Temporary failure in Name resolution". The default gateway is pinging and also the host ipaddress. I checked with nslookup and netstat -rn. Any suggestions to fix this?

Thanks
Raj

Re: Name Resolution Problem

Rajiv Singhal — Tue, 01 Feb 2005 16:34:16 GMT

What does /etc/resolv.conf say.

Rajiv

Re: Name Resolution Problem

Raj_58 — Tue, 01 Feb 2005 16:37:11 GMT

Hi,
Now I am not able to talk to the host. So I dont know how to check /etc/resolv.conf

Re: Name Resolution Problem

Rajiv Singhal — Tue, 01 Feb 2005 16:41:49 GMT

Do "cat /etc/resolv.conf" . This file is called upon to search the domains.

Re: Name Resolution Problem

Raj_58 — Tue, 01 Feb 2005 16:46:23 GMT

Rajiv,

FYI:

$ ssh root@sidtest.cup.hp.com
Connection closed by 15.75.200.57

I can't logon to the host.Thats my problem.
Hope now you got my point.

Re: Name Resolution Problem

Raj_58 — Tue, 01 Feb 2005 16:54:38 GMT

$ ssh nancy@sidtest.cup.com
Connection closed by 15.75.200.57

$ ping sidtest.cup.com

Pinging sidtest.cup.com [15.75.200.57] with 32 bytes of data:

Reply from 15.75.200.57: bytes=32 time=24ms TTL=254
Reply from 15.75.200.57: bytes=32 time<1ms TTL=254
Reply from 15.75.200.57: bytes=32 time=1ms TTL=254
Reply from 15.75.200.57: bytes=32 time=2ms TTL=254

Ping statistics for 15.75.200.57:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 24ms, Average = 6ms

$ netstat -rn

Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 11 85 88 44 c7 ...... Broadcom NetXtreme Gigabit Ethernet - Packet
eduler Miniport
0x3 ...00 11 0a 80 ea 4d ...... HP WLAN 802.11b/g W400 - Packet Scheduler Mi
rt
0x4 ...44 45 53 54 42 00 ...... Nortel IPSECSHM Adapter - Packet Scheduler M
ort
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 16.89.40.1 16.89.43.13 20
16.89.40.0 255.255.252.0 16.89.43.13 16.89.43.13 20
16.89.43.13 255.255.255.255 127.0.0.1 127.0.0.1 20
16.255.255.255 255.255.255.255 16.89.43.13 16.89.43.13 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 16.89.43.13 16.89.43.13 20
255.255.255.255 255.255.255.255 16.89.43.13 3 1
255.255.255.255 255.255.255.255 16.89.43.13 16.89.43.13 1
255.255.255.255 255.255.255.255 16.89.43.13 4 1
Default Gateway: 16.89.40.1
===========================================================================
Persistent Routes:
None

$ ping 16.89.40.1

Pinging 16.89.40.1 with 32 bytes of data:

Reply from 16.89.40.1: bytes=32 time=24ms TTL=255
Reply from 16.89.40.1: bytes=32 time<1ms TTL=255
Reply from 16.89.40.1: bytes=32 time<1ms TTL=255
Reply from 16.89.40.1: bytes=32 time<1ms TTL=255

Ping statistics for 16.89.40.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 24ms, Average = 6ms

$ nslookup
default Server: americas.cpqcorp.net
Address: 16.92.3.242

> sidtest.cup.com
Server: americas.cpqcorp.net
Address: 16.92.3.242

Non-authoritative answer:
Name: sidtest.cup.com
Address: 15.75.200.57

>

Any suggestions now to fix this.Hope this will give some detailed thought abt the problem.

Thanks

Re: Name Resolution Problem

Biswajit Tripathy — Tue, 01 Feb 2005 17:08:52 GMT

Raj,

It's not a good idea to post the internal IP addresses
in a public forum, don't you think?

- Biswajit

Re: Name Resolution Problem

Patrick Wallek — Tue, 01 Feb 2005 17:13:32 GMT

You NEED to somehow get logged into that machine. Is SSH your only option to connect? What about telnet?

It appears as if SSH is having a problem and closing the connection. Have your SSH keys changed? You need to verify that SSH is actually still running on that machine.

Re: Name Resolution Problem

Raj_58 — Tue, 01 Feb 2005 17:49:16 GMT

Hi,
I fixed this.
Actually I deleted /var/empty mistakenly.

Now i am able to work with that

Thanks all

Re: Name Resolution Problem

Raj_58 — Tue, 01 Feb 2005 17:56:29 GMT

Please close this thread.

Thanks
Raj