I have a wireless network with several vista home basic machines, several XP machines, and one vista ultimate machine. My network is a workgroup rather than a domain, so there is no server and every user has a matching account on every computer that they need to access over the network.
The vista ultimate machine was recently repartitioned so that it's network share lives on its own partition. Before this change all networking was working perfectly. The new network share has the same name meaning that the change should have been invisible to the rest of network. This was true of the other vista machines on the network, they all connected to the new share seamlessly. The XP machines could not find the new share at first, but after about an hour they found it and connected without a problem. However, one XP machine is being stubborn.
Let's call the Vista Ultimate machine "Alpha", it's network share "Alpha\Share", and the stubborn XP machine "Bravo". Bravo cannot see or connect to Alpha. Bravo cannot browse to Alpha, and if I type "\\Alpha\Share" into file explorer I get an error saying that the location cannot be found. Alpha is explicitly trusted in my Noton Firewall, but as a precaution I disabled the firewall. After doing this Bravo could not see Alpha in its network places, but if I typed "\\Alpha\Share" into the address bar of file exlorer, then Bravo would connect to Alpha. At this point I could turn the firewall back on and everything would be peachy. However, if I log off from Bravo or restart I am back to square one - not being able to see or connect to Alpha. The only way to connect is to turn off the norton firewall and type the "\\Alpha\Share" into file explorer. So I have two questions.
1) Why is norton firewall blocking my connection to Alpha even though its IP address is explicityly trusted?
2) Why can't I browse to Alpha from Bravo, even after I've connected by turing off the firewall and manually typing its share name?