 | | | routes | routes 2005-04-01 - By Steve Buehler
Back
I have a server on my network with an internal IP address of 172.16.1.12,
netmask 255.255.255.0, internal gateway 172.16.1.1. The external is (lets
say) 123.123.56.52. I have a client with an internal IP of 192.168.51.31,
internal gateway is 192.168.51.2 netmask 255.255.255.0 with an external IP
of (lets say) 123.123.105.201. Yes, they are both on the same Class
B. The first two numbers "123.123" are the same for both external ip
addresses. Only the last two numbers are not the same.
Supposedly the client was, at one time, able to get the the server by
going to the 172.16.1.12 address from his 192.168.51.2 desktop. Now he is
not able to. All of this started when the server had to be rebooted. I am
assuming their was a route setup on the server that allowed this since it
does not have a firewall "on" the server itself and the route was not in
any config files so when the server rebooted, the route disappeared. Does
this sound correct? The only thing a route command shows is:
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.1.0 * 255.255.255.0 U 0 0 0 eth0
If it is a "route" problem, if you could let me know how to add the route,
I would appreciate it. I have never added one before. Well, not that
worked anyway. :)
Any help would be appreciated.
Thanks
Steve
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@(protected)?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
Earn $52 per hosting referral at Lunarpages.
|
|
|