XP cannot access Win 7 shares

MobileTechie

Well-Known Member
Reaction score
32
Location
UK
Sorry for few details but I'm on site and don't have much time so please bear with me

Win 7 Pro 64bit machine sharing folder. Other win7 and win 8 machines can access share fine. No XP 32 bit machines can (have sp3)

Win 7 is set up to share permissions to everyone as are NTFS

Win 7 sharing set up:

network discovery on
file and print sharing on
puvlic folder haring on
media sharing off
enable file sharing for devices use 40 or 56 bit encryption on
password protected sharing - tried on and off, currently off
homegroup: ser user accounts and passwords to connect to other systems ticked

current profile: WORK

same settings for Private and Public networks

Firewalls off at this point

error: can see the win 7 PC in the workgroup but when click on it get "\\SERVER is not accessible. You might not have permission to use this network resource......The network path was not found"



also does not work if I try to hit a specifc share, e.g. SERVER/Data
 
Try \\IPADDRESS instead. Could be an issue on the XP's end with Local name resolution. Also check event log for Master Browser errors, as could be related...
 
Last edited:
Sorry for few details but I'm on site and don't have much time so please bear with me

I wish I had an answer for you but I had the same issue at an accountants office a few months back. XP was reliably accessing Win 7 shares for 2 years and then one day failed. I finally gave up after 3 hours of troubleshooting and had the client buy a Win 7 box.
 
1) Ensure all machines are on same workgroup.

2) Remove the XP box from the workgroup / change the workgroup name. Reboot. Add to same workgroup as Win7 machines. Reboot and try again.

3) A while ago I ran into a similar issue. My tech & I both tried everything we knew. As I recall, my research showed me that this is a known issue that many other people have. You may have no choice other than to replace the XP machine with a win7 box.

MS is stopping all support for XP in April anyway.
 
Also, FWIW, I always set the network profile in Win7 to "Home" unless it is on a domain. I believe the sharing settings are a little less strict than with "Work" and make sharing a touch easier....I think.....
 
Try \\IPADDRESS instead. Could be an issue on the XP's end with Local name resolution. Also check event log for Master Browser errors, as could be related...

I think this is the problem.

It works with the IP so it's name resolution based. I didn't mention it but these machines were part of a domain originally. Maybe they have some DNS or WINS settings that are stopping proper name resolution.

Thanks for the pointers guys.
 
I think this is the problem.

It works with the IP so it's name resolution based. I didn't mention it but these machines were part of a domain originally. Maybe they have some DNS or WINS settings that are stopping proper name resolution.

Thanks for the pointers guys.

So used to be Domain? But not anymore? Properly removed while DC was still operable? or after DC was (hopefully) properly demoted?
I bet this is a Master Browser Issue, as the when on a Domain, the DC is always the Master Browser, and therefore supplies all locally accessible machines. If DC is unreachable, an election is held between all local-net machines. However, this system fails regularly. Unfortunately, the only fix I know of (outside of running down endless event logs and log files), is to map the drive via IP and move on.
Vista and above don't use the Master Browser system, can't remember what they use, but I think its just local awareness. When an XP machine tries to hold an election with machines that don't participate in the election, this can sometimes break the system, as the XP's nominate the 7 box as Master Browser, and 7 say Nope! You can manually force an election to temporarily fix this, you'll have to look up the cmd as I don't remember it off-hand, and the issue will most likely reappear in the future.

Could also be a problem with WINS server that no longer is in-place, but thats easy to identify by investigating the IP settings, or determining where the DHCP comes from. Since it "used to be" a domain, my guess is DHCP is not on a server, therefore WINS is typically not usable.
 
So used to be Domain? But not anymore? Properly removed while DC was still operable? or after DC was (hopefully) properly demoted?
I bet this is a Master Browser Issue, as the when on a Domain, the DC is always the Master Browser, and therefore supplies all locally accessible machines. If DC is unreachable, an election is held between all local-net machines. However, this system fails regularly. Unfortunately, the only fix I know of (outside of running down endless event logs and log files), is to map the drive via IP and move on.
Vista and above don't use the Master Browser system, can't remember what they use, but I think its just local awareness. When an XP machine tries to hold an election with machines that don't participate in the election, this can sometimes break the system, as the XP's nominate the 7 box as Master Browser, and 7 say Nope! You can manually force an election to temporarily fix this, you'll have to look up the cmd as I don't remember it off-hand, and the issue will most likely reappear in the future.

Could also be a problem with WINS server that no longer is in-place, but thats easy to identify by investigating the IP settings, or determining where the DHCP comes from. Since it "used to be" a domain, my guess is DHCP is not on a server, therefore WINS is typically not usable.

I had exactly the same issue and it WAS a master browser problem. I wish I had in my notes the registry entries. I had to force a reelection so to speak and stop 7 from being the Master from what I recall as well... anyway I think you're right Jbartlett for this issue..
 
Back
Top