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
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 wlhj
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.
by wlhj
by wlhj
This discussion is closed to new replies.
Trending Linux posts
Sort by Trending