I have a strange (for me) situation on my home (workgroup) network. I have one XP machine, call it DATA, that I'm using as a server with several drives all of which have shares with wide open permission and security settings for Everyone. Call these share1, share2, share3. On share2 there is a folder structure. Call this folder1\folder2. I have 4 other PC's on the network (in same workgroup). 3 are XP and 1 is Win7. From all of these machines I can access any of DATA's shares, including share2 with no problem from Network Neighborhoods or via the appropriate PC icon in Network Neighborhood. I can get to any file in any folder on any of these shares. But, on one particular XP machine, I cannot access share2 (I get the "refers to a location that is unavailable..." message). Interestingly, I can map share2\folder1\folder2 to a network drive from this machine and access anything there with no problems. I just cannot access the share2 in any other way. All the other shares are fine. This situation only happens from one of the machine on my network. All others can access share2 with no issue and no problems. I believe I have the permissions and security settings on DATA the same for all of it's shares so I don't know what might be different there. So, I'm stumped as to why only one and only one particular machine cannot access one and only one particular share on a common machine that all others can get to with no problem. And why that one machine can access anything on this share2 via a network mapped drive to it or any of it's folders with no problem. My only hypothesis is that there is a share2 somewhere on DATA that has previously been assigned to a drive that may no longer exist and for some reason only the one machine is directed to that location instead of the real location of share2. But, I don't know how to confirm this hypothesis or where else to look for a solution to my problem. Can someone suggest an approach to finding root cause and solving this problem? Thanks in advance.