Min Chien Lim wrote: >>My system has no problems accessing (telnet/pinging) systems with >>129.146.210.xxx or 129.146.xxx.xxx IP addresses but when the IP > > looks > >>like 129.xxx (something other than 146) .xxx.xxx, it cannot >>ping/telnet to it. Doing a ypmatch on 129.xxx.xxx.xxx has no >>problems. Any clues? > > > What does your routing table look like? > > netstat -rn > > Paul. > > It looks like > > -bash-2.05b# netstat -rn > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window > irtt Iface > 129.146.210.0 0.0.0.0 255.255.255.0 U 0 0 > 0 eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 > 0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 > 0 lo > 0.0.0.0 129.146.210.250 0.0.0.0 UG 0 0 > 0 eth0 You can send packets to 129.146.210.* because your are directly connected to that network. Packets for anywhere else go to your router at 129.146.210.250 so you'd need to check out the netmasks and routing tables on that router to find out what was happening. (I'm assuming that "/sbin/ifconfig eth0" on your machine would show an IP address somewhere in 129.146.210.* and a netmask of 255.255.255.0). Paul. ---------------------------------------------- The problem may not pertain to the routing table. I cannot ping/telnet to the hostname but I can ping/telnet to the IP address. And ypmatch returns the correct results. Ping/telnet to the hostname results in a "unknown host ..." Min Chien _______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com
