Wireless Network Connection Problem Ok guys, I have 3 computers total(1 desktop, Laptop A and Laptop B). Have a Netgear router as well. The internet comes in via cable modem which is then connected to the router. From there the desktop is hard wired to the router, laptop A is connected via a Netgear wireless card, and Laptop B is connected via "Wireless LAN" built in. All computers have an internet connection, no problem. All firewalls are off now. I have the TCP/IP obtaining IP addresses automatically. All the work done is with the desktop logged into user Name1. I think XP home only has simple flie sharing, so I don't think that's it. For the firewall settings I have IP addresses 192.168.0.2 --> 192.168.0.5 all allowed on each computer's firewall (see below). Router is 192.168.0.1 Here is the following info for each couputer(NAME): All are on the MSHOME workgroup 1. TCP/IP address 2. Subnet Mask 3. Gateway 4. OS 5. Service Pack 6. Users Desktop(Dell) 1. 192.168.0.2 2. 255.255.255.0 3. 192.168.0.1 4. XP Hope 5. Service Pack 2 6. Name1, Name2 Laptop A(Shevans): On this one I also have a network Bridge, not sure if that is doing anything. 1. 192.168.0.3 2. 255.255.255.0 3. 192.168.0.1 4. XP Hope 5. Service Pack 1 6. Name2 Laptop B(Sony) 1. 192.168.0.4 2. 255.255.255.0 3. 192.168.0.1 4. XP Hope 5. Service Pack 2 6. None Here are my results when I ping each computer. I piged by both IP and computer name. Ping Desktop ---> Desktop = 0% loss Ping Desktop ---> A= timed out, 100% loss --- This doesn't make sense as Desktop and A can see eachother Ping Desktop ---> B = 0% loss Ping A ---> A = 0% loss Ping A ---> Desktop = 0% loss Ping A ---> B = 0% loss Ping B---> B= 0% loss Ping B---> Desktop = 0% loss Ping B---> A = 0% loss Some All have XP Home. Here is my problem. I have my printer connected via serial to my desktop. The desktop can see the workgroup and shared files on both laptop A and laptop B without problems. I can connect to the printer with laptop A without any problems. Laptop A can see the workgroup and the shared folders on the Desktop and itself. It doesn't see any Laptop B folders. Laptop B can see the workgroup, but only sees Laptop A and itself. It does not see the desktop and therefore cannot get to the printer. What am I missing here that Laptop B can't see the desktop and doesn't have access to laptop A. When trying to navigate to laptop A I get a "is not accessible. Might not have permissions.....network path not found" error. My main concern is getting B and the desktop to talk as B is the replacement for A. I can't do the replacement till I can get a printer and file sharing between B and the desktop. That being said, both B and the Desktop are on SP2 and each can ping eachother. I still can't get access to the Mshome workgroup from B. Mshome comes up under the microsoft windows network, but when I click on it I get that not accessible/permission/network path error. I reset the B and Desktop workgroup name to MSHOME1 now. Now when I am on B and I try to access the Microsoft Windows Network the MSHOME1 group comes up and when I cluck that the B computer shows up (showing itself). Before I would get the not accessible error. So the B shows itself, but it doesn't show the desktop. So getting closer, at least now I could access the workgroup. When I did this I hadn't changed the Desktop workgroup name yet. On the desktop I showed both the MSHOME and MSHOME1 workgroups, and teh Desktop could access the B computer on MSHOME1 still. When I changed the Desktop workgroup to MSHOME1 I could access and see the B computer as well. When I went back to MSHOME on both computers I ran into the same problem. Getting that not accessible error on MSHOME on laptop B....would there be some setting I'm missing here? Thoughts? Andrew

Put all computers in same workgroup. There was some valid reason for Laptop"A" to drop, or not respond to, incoming ping requests from the Desktop, while allowing outgoing ping traffic. Either in Laptop "A"'s firewall configuration or in the router configuration. 98% of the population is asleep. The other 2% are staring around in complete amazement, abject terror, or both.

It's not computer A that I am having the problem with. The desktop and A can talk fine, it's B and the desktop that I'm having the problem with. Just can't figure out why the desktop can talk to B but B can't talk to the desktop.