Hello Kevin,
Wednesday, February 20, 2002, 3:06:37 AM, you textually orated:
KC> Dear Jack and all,
KC> Jack, I was tried to config the sysctl.conf and reboot the machine after.
KC> But the problem still the same - is client side can't browse Intereting
KC> when I assign a
KC> different range of IP (10.0.0.1) to them (p.s. Server IP Address is
KC> 192.168.13.222). If I change the IP (192.168.13.223) for client, they
KC> haven't any problem at all. So I think there is something need to do on IP
KC> forwarding.
KC> Do you know what I can do to solve this problem ? Also,below is what I
KC> change from my server:
Assuming this is your network topology...
Internet(0.0.0.0)
|
Server-External Interface(xxx.xxx.xxx.xxx)
|
Server-Internal Interface(192.168.13.222)
| |
Client A(192.168.13.xxx) |
|
Client B(10.10.10.xxx)
In this scenario, Client B will NOT be able to connect to the server. It is
not on the same "network" (it is physically, but not in networking terms).
Client A will be able to connect.
You need to add another IP address to the server (it can be virtual) to
allow this to happen or you need to change the server's internal interface
to be on the same network. No "tricks" will allow you to bypass this
fundamental networking principle.
Have fun,
--
_________________________________________________________________
Brian Ashe CTO
[EMAIL PROTECTED] Dee-Web Software Services, LLC.
http://www.dee-web.com/
-----------------------------------------------------------------
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
