SS - I have not had an opportunity to work with Wi-Fi, however you should be able to specify the box to which you wish to solely communicate. A more complex solution would be to further protect your transmissions by using IPSEC, which adds Kerberos encryption and allows you to specify that you will only accept packets that have been authenticated. This would have the benefit of offering very secure transfers, and limiting the box(es) to which you wish to communicate. I know that this doesn't really answer your questions, but I will think on it for you.

Esquilax

============================================================
The above post is true, and by true I mean "false". It's comprised of lies, but they are entertaining lies and in the end, isn't that the real truth? The answer is "no".

I honestly don't think this setup is going to work without a hardware router. i don't think the ethernet adapter in the gateway PC is going to handle the transition from DHCP to NAT. 'course u COULD try 2 ethernet adaptors, I've bodged it like that before, but this is the old story, u either get the internal network or the internet but not both.

have u been running some software routing stuff? cos that's all cr*p too, never bl**dy works. Only hardware works properly and consistently.

Must and Esq are right, u need to know what IP address u'v had assigned by the ISP, u also need the domain ur logging onto & a hostname (which can be anything u like as long as u use it every time on each machine) then u need to put this in ur router config and ALSO the starting IP address of ur internal network. Then u can use simple static IP addressing for each subsequent machine. At the moment Card, u aint giving us enough info to work with and we're filling in the gaps as best we can.