Machine cannot ping itself

[jimktrains]

We have a customer with SCO unix 5.0.5 that cannot ping itself using the ip address or name. It can ping localhost and users are connected to it via telnet. I can ping the users that are connected and they say they can ping the server from other machines. When I ping it's ip address, it just comes back with "Host is down."

I am not sure what could be the problem as I was there a few weeks ago and I didn't notice a problem.

Any help is much appreciated.

 

[motoslide]

Not sure where to start here.

Please post the output of these commands:
# ifconfig -a
# netstat -rn
# cat /etc/resolv.conf
# hostname

Also note any entries in /etc/hosts which have the same IP and/or hostname.

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[jimktrains]

# ifconfig -a
net0: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.2 netmask ffffff00 broadcast 192.168.2.255
perf. params: recv size: 24576; send size: 24576; full-size frames: 1
ether 00:02:a5:93:06:b1
lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
perf. params: recv size: 57344; send size: 57344; full-size frames: 1
atl0: flags=404a<BROADCAST,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 0.0.0.0 netmask ff000000
perf. params: recv size: 4096; send size: 8192; full-size frames: 1

# netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface
default 192.168.2.254 UGS 13 4289 net0
127.0.0.1 127.0.0.1 UH 2 24 lo0
192.168.2 192.168.2.2 UC 1 0 net0
224 192.168.2.2 UCS 0 0 net0

# cat /etc/resolv.conf
nameserver 192.168.2.3

# hostname
humsrv.xit

All entries in /etc/hosts have different IPs.

 

[pknoz]

/etc/hosts should have an IP address followed by machine name.

Like this
192.168.2.2 humsrv humsrv.xit

Are you using DNS for resolution? Who is controling DNS entries?

 

[pknoz]

Also the resolv.conf should have an entry of search order;
hostresorder local bind

Are you running a firwall on this server?

 

[motoslide]

I agree with pknoz, you should have a 192.168.2.2 entry in your /etc/hosts file.
You can try renaming "/etc/resolv.conf" to temporarily disable that function.

# mv /etc/resolv.conf /etc/resolv.save

See if that changes your symptoms.
Shouldn't the "hostname" return more? I don't know if it's absolutely required, but I expected something like:
humsrv.xit.com (something with 3 values instead of 2).



"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[jimktrains]

192.168.2.2 humsrv humsrv.xit is in the /etc/hosts file.

I renamed resolv.conf and no change in the results.

DNS is not used for naming and there is no firewall on this server that I am aware of.

It owuld show humsrv.xit.com if xit.com was the domain name but it is not.