unable to ping windows servers

[Jerry_109]

HP-UX B.11.11 U 9000/800/L3000-7x

Hello HP,

I am unable to ping a windows server ( 192.168.13.5 ). I can ping other windows servers on "192.168.13" subnet. The windows folks are insisting the problem is on my side.
I have executedthe following :

**************************************
other windows servers on 192.168.13
#grep 192.168 /etc/hosts
192.168.13.5 HOAdobeApp.scif.com HOAdobeApp # Internal network in STC, Domain A
192.168.13.151 hodc01.scif.com hodc01 # Win 2k3 Dom Contr/DNS Server, STC, Domain A ( Pri )
192.168.15.20 nadc01.scif.com nadc01 # Win 2k3 Dom Contr/DNS Server, STC, Domain A ( Sec )
192.168.13.161 hosf01.scif.com hosf01
192.168.13.51 fdcv01.scif.com fdcv01
************************************
successful ping to other 192.168.13 subnet

#ping 192.168.13.51 64 2
PING 192.168.13.51: 64 byte packets
64 bytes from 192.168.13.51: icmp_seq=0. time=1. ms
64 bytes from 192.168.13.51: icmp_seq=1. time=0. ms

----192.168.13.51 PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/1/1
root@hohp230[/var/adm]
#
root@hohp230[/var/adm]
#ping 192.168.13.161 64 2
PING 192.168.13.161: 64 byte packets
64 bytes from 192.168.13.161: icmp_seq=0. time=1. ms
64 bytes from 192.168.13.161: icmp_seq=1. time=0. ms

----192.168.13.161 PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/1
root@hohp230[/var/adm]
#
root@hohp230[/var/adm]
#ping 192.168.13.5 64 2
PING 192.168.13.5: 64 byte packets

----192.168.13.5 PING Statistics----
2 packets transmitted, 0 packets received, 100% packet loss
************************************
traceroute information

#traceroute 192.168.13.151
traceroute to 192.168.13.151 (192.168.13.151), 30 hops max, 40 byte packets
1 10.254.200.1 (10.254.200.1) 0.464 ms 0.163 ms 0.154 ms
2 hodc01.scif.com (192.168.13.151) 0.451 ms 0.295 ms 0.223 ms
root@hohp230[/var/adm]
#
root@hohp230[/var/adm]
#traceroute 192.168.13.5
traceroute to 192.168.13.5 (192.168.13.5), 30 hops max, 40 byte packets
1 10.254.200.1 (10.254.200.1) 3662.723 ms !H 3999.343 ms !H 3999.869 ms !H

******************************************
netstat -rn & ifconfig
#netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
10.254.110.230 10.254.110.230 UH 0 lan0 4136
10.254.0.0 10.254.110.230 U 2 lan0 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 10.254.200.1 UG 0 lan0 0
root@hohp230[/var/adm]
#
root@hohp230[/var/adm]
#ifconfig lan0
lan0: flags=843
inet 10.254.110.230 netmask ffff0000 broadcast 10.254.255.255
******************************************


We suspect there is a problem with the default/gateway setup on 192.168.13.5 ? I have requested a copy of the "ipconfig /all" for both :
192.168.13.151
192.168.13.5

Jerry Sims
415 565-1630

[Mel Burslan · Accepted solution]

One question begs to be asked:

is there a firewall between your network and this other network where the windows machines are located ? if yes, I'd strongly suggest talking to the firewall admin(s).

Also tell the windows forls to get on to a command prompt and ping this 10.254.200.1, which is where your traceroute seems to be stopping at.

[Jerry_109]

sorry, I forgot to add. The windows staff has
indicated they can successfully ping our UNIX server. I will check on the firewall
question. I know the domains are separated
ie UNIX domain & windows domain. The network
folks connect the domains via VLAN.

[John Dvorchak]

Since you can ping others on that subnet one would think that the problem is with the one WINDOW$ machine 192.168.13.51 but they insist that it's a problem with your system. I don't understand that line of thinking, and I would love to hear the resulting torrent of dis-information from thier explanation of why it's your fault.

Logic would dictate that the problem is, as you suspect, with the default route or netmask on the windows machine. Have them ping/traceroute (they spell it tracert) your box from that machine. I'll bet it doesn't work.

I don't know what you are asking it looks like you have it figured out. Good going!

[John Dvorchak]

I clicked submit before I read your last comment about the ping working from their end and the vlan. I think you would want to see a tracert from their end to confirm that the packets are routed where they think they are going. This almost looks like a duplicate IP address problem.

[Jerry_109]

Is there a way to determine if someone really
sent a ping to my server ?

[Bill Hassell]

ping is handled at a very low level in the network code so there is no way to log such an occurance. NOTE: It is very common for network admins to disable ping to (and through) a router. Try a ping to your local router that will take you to the problem network. If it fails, it isn't Windows, it's good old network security. This can also cause HP-UX to disable routes due to a dead gateway. This feature was introduced at 11.0 and the symptom is that a network card seems to go dead after a few minutes. Use this command to verify the gateway:

ndd -get /dev/ip ip_ire_status | grep -e IRE_GATEWAY

If you see DEAD, then the route has been disabled because the router does not respond to pings. To get the system working temporarily:

- ndd -set /dev/ip ip_ire_gw_probe 0
- route delete default 192.168.1.1
- route add default 192.168.1.1 1

(fill in your own IP numbers)

It's possible that the router is asymmetrical, that is, ping works one way and not the other. Also try pinging other network boxes on the problem network, like LAN printers, non-Windows boxes, etc

[Dexter Filmore]

Can you ping the windows server from another box? Test from a box on your subnet and on the subnet of the windows server.

All the best.

[Jerry_109]

Problem resolved. Incorrect network configuration on the windows side. All is fine now.

[Florian Heigl (new acc)]

Jerry,

for christmas, make them a small present like... TCP/IP illustrated.
Windows admins love that.
:>