Hi, I have a home network setup as follows: DSL> Linksys Wireless-N ADSL2+ Gateway WAG300N connected to 3 PCs IP Add: 192.168.1.1 PC1 Desktop PC with Win XP Home SP2 Connected via wireless G card to router DHCP assigned address from router 192.168.1.101 PC2 Desktop PC with Win XP Home SP2 Connected via ethernet to router DHCP assigned address from router 192.168.1.102 PC3 Laptop PC with Win XP Media Center Edition SP2 Connected via Wireless G Card to router DHCP assigned address from router 192.168.1.105 All PCs have windows firewall turned off All PCs have Grisoft Anti Virus V7.5 (disabled for now) All PCs have the following protocols installed: 1 Client for Microsoft networks 2 File and Printer sharing for Microsoft networks 3 Internet Protocol TCP/IP 4 QoS Packet Scheduler All PCs can access the web All PCs can ping the router (192.168.1.1) The router can ping all PCs All PCs belong to "MSHome" Workgroup PC1 can ping PC2 by IP and Name but cannot ping PC3 at all PC3 can ping PC2 by IP and Name but cannot ping PC1 at all PC2 can ping both PC1 and PC3 by IP and Name The problem lies between PC1 and PC3 who cannot see each other, but can ping and be pinged by other devices! The only common factor between the 2 seems to be that they are both wireless, but i cant see this making a problem for TCP/IP?? The signal strength is excellent and never drops out, ping times are 1ms between other pcs! i have even changed PC1 and PC3 workgroup to another and this does not work, but even then i can still ping PC2 when it is on another worgroup. Anybody have any ideas??

Do you have NetBIOS over TCP/IP enabled on all 3 PC's?

Erm, not sure, where would i check for that?

Ok found it, under wins tab on TCP/IP properties, i have enabled it on all PCs but still the same problem, and now i cant even click on the workgroup, comes up with "MSHOME is not accessible, you may not have permission etc... the list of servers for this workgroup is currently accessible"

Did you run the network setup wizard on each machine, and choose the option that you are connecting to the internet through a residential gateway? If that doesn't resolve the problem, for problematic clients, change their workgroup to something else, change their computer name to something else, and then change the workgroup back, leaving the new name in place. I've seen sometimes that's the only way to get NetBIOS to work right again. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"