I have a 2 comp. workgroup with XP Pro and XP Home systems. They both use the Windows Firewall. They both have shared folders on them that I like to use once in a while. The XP Pro machine has a shared printer on it. They are connected through a router and I can see them both in DHCP all the time. They can ping each other all the time. However, when I try to access their shared folders, it is very hit and miss, usually miss though. The XP Home machine seems to be able to access the XP Pro's folders a little more often. The printer works more often than the shared folders, although not all the time either. When I do a search for them using Start, Search, Computers or People, nothing turns up. When I go to Start Run, //(name of computer) nothing turns up (returns the error "Windows cannot find *name of computer* Make sure you typed the name correctly....). Both computers are using TCP/IP. Again, I can see the XP Pro resources on the XP Home machine rather than vice versa but there still seems to be a problem with the XP Home machine. I have tried to compare the 2 comps, and can't find any answers? Any idea why Network Neighbourhood won't work? Its funny why Start, Run won't find them either.

They both use the Windows Firewall. Well there's your problem. Start Run, //(name of computer) nothing turns up It's "\\". Not "//".

I turned off Windows Firewall on both... no improvement. BTW... \\ is what I had tried. Sorry. Any other ideas?

Have you tried accessing them by just their IP? If you can get to them via ip and not name, you have a DNS issue. ex. \\192.168.1.100 You can find the ip of each pc by start>run>cmd>ipconfig

Using the IP seems to work. So why do you think using the names won't work? Thanks

DNS converts recognizable names to ip addresses. So when you enter a computer name or url, that name gets looked up in a table (usually DNS server) or host file and makes the translation to an ip address. Several things to check. In Network Places, view connections and then right click the connection (usually local connection) and select properties. You will see the connection properties and select TCP/IP and then properties button. You will want to ensure that obtain ip address automatically and DNS server address is selected. Next run ipconfig/all from the command prompt and post the results if no changes were made. I'm assumming that your router connects to an ISP?

Alright this is the readout from ipconfig /all. I turned on DNS to look to the router, and yes, the router is connecting to the ISP. Windows IP Configuration Host Name . . . . . . . . . . . . : dan-f0d82a223e7 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : Yes Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller Physical Address. . . . . . . . . : 00-13-D4-29-F3-43 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.0.104 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 Lease Obtained. . . . . . . . . . : Wednesday, November 14, 2007 1:17:51 PM Lease Expires . . . . . . . . . . : Wednesday, November 21, 2007 1:17:51 PM Thanks