>
> Any ideas???
>
Yeah, go to the XP O/S and disable the Wireless Zero Configuration on the
machine. That makes the machine see other networks in your area, and in
general, presents a security risk as malware that could compromise the
machine can use WZC service to get out, even if it doesn't have a
wireless NIC installed. It also can cause problems with the connection
wireless connection at times.
Limit the number of DHCP IP(s) that can be issued to the number of
machines you have connected to the router. It's not 100% because someone
could easily use a static IP. But you'll know something is up if one of
your machines cannot use a DHCP IP, because someone hijacker it.
Use Wallwatcher (free use Google) to review traffic to and from the
router on a routine basis.
Use a sophisticated SSID and rotate/change it on a routine basis.
Change the router's Admin password to something else, since everyone else
in the world knows it too.
Use Active Ports (free) and Process Explorer (free) and look around on
the machines from time to time for yourself to see what's happening.
Use IPsec that's on the XP O/S to further secure the LAN and the Windows
Networking Ports. IPsec can block inbound or outbound by port, IP,
protocol, DNS, etc.
http://www.petri.co.il/block_ping_tr...with_ipsec.htm
http://www.analogx.com/contents/articles/ipsec.htm
You may also want to use VPN connections between machines on the LAN and
setting IPsec to only allow VPN connections from the LAN, preventing any
one not using VPN to be able to access a machine via wireless that is not
using VPN.
The buck stops at the O/S in the security and everything else is
secondary to the O/S, including the router, etc. You should *harden* the
O/S to attack.
http://www.uksecurityonline.com/husdg/windowsxp.php
use the Host
http://mvps.org/winhelp2002/hosts.htm
http://accs-net.com/hosts/HostsToggle/
Duane