Discussion Locked

Unix box not able to ping routers

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I work for a public library. We are currently replacing our 3Com routers with Cisco routers. We have a 2621 at the main branch and 1720's at the branches. We have a channelized T1 coming in from the branches. We use NAT addresses for the workstations at the branches and have a class C license for our main library. After installing the Cisco equipment, we can get on the internet, and ping all of our workstations, routers, and servers from the branch. We cannot ping or telnet to a UNIX server at the main library. This server cannot ping the branch either. We can ping the UNIX server from the 1720 located at the branch but the UNIX server cannot ping the 1720. All of the workstations and servers at the branches and the main library are running Windows NT 4.0. Cisco has looked at our configuration and says it is set up properly. There are currently no access lists enabled. Everything is wide open on the routers. The vendor that is responsible for the UNIX box (this box runs our card catalog system and is totally controlled by our vendor, Innovative Interfaces) claims the problem is with the network and not with their box. We are stuck in the middle. Does anyone know what might be causing this problem? I can be reachedat wlhj@hotmail.com Bill Huffman

7 replies

by bradleyr

I do not know - kind of interesting though, hope this helps. Ok, if everything worked properly before, my guess it is not the Unix box (unless ip addresses are different on the 3coms and Cisco routers). You say that Unix can't ping 1720. Assumingthose 2 are on the same network,
1. What equipment is between Unix box and 1720?
2. Can Unix box ping other nodes on the same network as 1720?
3. If it can and Unix box and 1720 are on the same subnet, I do not think your Unix box has a problem (2 reasons - it worked before and it can ping other nodes)

This is pretty basic of course, shoot me an email if you'd like with your phone number (bradleyr@taxidivision.com)

by wlhj

The 3coms and ciscos do have different Ip's. Just talked to the vendor and they have a routing table set up in the UNIX box. I am trying to decifer it. They have no networking people left.

by vinnyd

You can add a temp route in Unix by using the command:

/etc/route add default ipaddress

This command works until the unix computer is rebooted. Then the command has to be done again.

To make the change permanent I believe that you have to edit one of the rc.d files so that the route is added each time the Unix system boots up.

by stillatit

Your vendor may have to check some of this, but here are things to check:

- How is the UNIX box getting its IP address? If it is hard-wired (not DHCP), is the address on the same subnet as the inside port of the router? Is it unique? Is the maskcorrect?

- In /etc/hosts, does the UNIX box have a correct entry for itself? For the router? For other stations on your net?

- Is the UNIX box default route set correctly. Type the command
netstat -r
and look for the "default" entry. It should point to the inside port of the 1720.

- Checking for silliness, trace the cables from the UNIX box to the router, and make sure that everything is plugged in. If there is a hub involved, make sure that the UNIX box is NOT plugged into an uploadport on the hub (typically the first or last), or if it is, that the switch is set for normal use. Try moving to a different port on the hub.

Good luck.

This discussion is closed to new replies.