Why would you want them to see each other at all? If they need to map a drive, you should still be able to do that using the old \\ip-address\share
Nope. Not with client-client communication disabled and all clients configured so that they think they are on the same subnet. Disabling client-client on a subnet breaks the way that IP expects layer2 to behave.
To give an example: Client1 10.0.0.2 netmask 255.255.255.0 gw 10.0.0.1 Client2 10.0.0.3 netmask 255.255.255.0 gw 10.0.0.1
If you type \\10.0.0.3\share on Client1, it will try to send packets directly to Client2 (it will first send an ARP asking for the MAC of 10.0.0.3, and then try to send ethernet frames with that MAC as the destination). With client-client communication disabled, the AP will drop the packets instead of forwarding them.
Roger - the client will only send packets to the router behind the AP if it is configured to do so. Put each client on a different subnet and configure the router to forward packets between the subnets.
Client1 10.0.0.2 netmask 255.255.255.252 gw 10.0.0.1 Client2 10.0.0.6 netmask 255.255.255.252 gw 10.0.0.5 Configure router with IPs 10.0.0.1 and .5, netmask 252 on the interface connected to the AP and enable routing between them.
When Client1 now types \\10.0.0.6\share, his computer will look at the netmask and see that it needs to send the packet through 10.0.0.1.
This is horribly inefficient with regards to address space, though. If you are using public IPs, you're using 4 addresses per client! This is one of the reasons why some of us prefer to use PPPoE.
TCP/IP Illustrated Vol. 1 by Stevens or Internetworking with TCP/IP by Comer is recommended.
-- LarsG
The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org
