Windows XP cannot access Windows 7 shares

[OVerLoRDI]

I know this is a popular google search but I have followed all the directions there and have had no luck so far. My Windows 7 machine has numerous network shares that are all easily and painlessly accessible by anyone using 7 or Vista. I have 2 Windows XP machines on the network that get access denied errors when I try to access shares on the Windows 7 machine. The Windows 7 machines can access the shares on both the XP machines. All machines have the latest updates.

No machines are running local firewalls
All machines are connected via a wired switch
All machines are under the same User Account without a password
Can access XP shares from Windows 7 but not Windows 7 shares from XP
Windows Vista and 7 machines can properly access shares.

Edit: I got it to work for a while by setting it to work network, but now it stops working after my computer has been on for a day or so. Once I reboot my server it allows XP machines to reconnect, but there is some cut off points after so many hours XP machines can no longer connect.

 

[J3S73R]

ive had to add a username/password specifically for xp or lower machines then map the drives/shares with the selected username etc

 

[OVerLoRDI]

Yeah that looks like what I'll have to do. Very frustrating.

 

[fffblackmage]

There's also something like "Password protected sharing" somewhere...

Here: Go to the control panel > Network and Internet > Homegroup, then click "Change advanced sharing settings." Make sure "Password protected sharing" is off.

 

[JackMDS]

Win 7 has three types of Sharing configuration when configured on peer-to-peer Network.

Home Network = Works only between Win 7 computers, and make it very easy to Entry Level Users to start Network sharing.

Work Network = which is basically similar to the previous methods of sharing that let you control what, how, and to whom folders would be shared with.

Public Sharing = Public Network (like Internet cafe) to reduce security risks.

The Work Network is the one that most of us are going (and need) to use.

Unfortunately, I do not have yet good links for the Win 7 "Work Network" Sharing.

However in principle it similar to Vista (some menu in locations in Win 7 might be in different place, and look a little different, but it should not be a problem for a computer enthusiasts to adopt)

So, maybe this can Help.

Make sure that the Software Firewall on each computer allows free local traffic. If you use 3rd party Firewall On, Vista/XP Native Firewall should be Off, and the active Firewall has to adjusted to your Network IP numbers on what is some time called the Trusted Zone (consult your 3rd Party Firewall instructions.

General example, http://www.ezlan.net/faq#trusted

Vista File and Printer Sharing- http://technet.microsoft.com/en-us/library/bb727037.aspx

Windows XP File Sharing - http://support.microsoft.com/default.aspx?scid=kb;en-us;304040 http://support.microsoft.com/default.aspx?scid=kb;en-us;304040

Printer Sharing XP - http://www.microsoft.com/windowsxp/using/networking/expert/honeycutt_july2.mspx

Windows Native Firewall setting for Sharing XP - http://support.microsoft.com/kb/875357

Windows XP patch for Sharing with Vista (Not need for XP-SP3) - http://support.microsoft.com/kb/922120

When finished with the setting of the system it is advisable to Reboot all the hardware including Router and all computers involved.

 

[OVerLoRDI]

Thank you so much JackMDS, it worked perfectly after I switched it to work network. This new sharing system is a bit too confusing for its own good.

 

[JackMDS]

I drove cars for 40 years without GPS.

When I got my New car it was confusing to learn the GPS too. :sneaky:

But you are right, Microsoft marketing guys are so enthusiastic to point to the New Thingies (the individual "trees") and they forget about the the total picture (the "forest").

 

[Modelworks]

Networking is one of my most disliked features of win7. I really hate the way it is implemented. Especially if you are someone who swaps devices out a lot. You have to sit and wait while windows decides what kind of connection it is before it will let you have any say.

 

[OVerLoRDI]

Well it worked for a while.... But now it stopped working. If I reboot my server it works once again but there is some strange cut off point where after a day or so my XP machines can no longer connect. Any ideas?

 

[BlueWeasel]

Jack:

Thanks for the Home/Work distinction in Windows 7. I've been having some issues connecting my Win7 shares to other devices (XBMC Samba specifically) and this may fix it.

 

[rigfennid]

Check your network card configuration. Go to Network Connections and right-click your ethernet connection and choose Properties. Under where it shows the card, there is a Configure button. On (IIRC) the last tab, there is a checkbox for "allow this device to be turned off to save power" or something to that effect. Remove the check, click "OK" several times to confirm the change, and you should be done with the "timeout" issue.

 

[Shik]

Well it worked for a while.... But now it stopped working. If I reboot my server it works once again but there is some strange cut off point where after a day or so my XP machines can no longer connect. Any ideas?

I have this same problem and I can't believe other people don't? After I reboot my Windows 7 desktop, my windows XP clients can connect to shares on the Windows 7 machine, with their saved username/passwords. After 1-3 days, the shares stop working with the error "the specified server cannot perform the requested operation". My Vista clients can continue to connect to the Windows 7 shares. My Windows 7 machine can connect back to shares on the Windows XP clients. My Windows XP clients can connect to other Windows XP clients. My windows XP client is running an RDP to the Windows 7 machine, but can't access the shares!

anyone?

 

[famfam]

I have this same problem and I can't believe other people don't? After I reboot my Windows 7 desktop, my windows XP clients can connect to shares on the Windows 7 machine, with their saved username/passwords. After 1-3 days, the shares stop working with the error "the specified server cannot perform the requested operation". My Vista clients can continue to connect to the Windows 7 shares. My Windows 7 machine can connect back to shares on the Windows XP clients. My Windows XP clients can connect to other Windows XP clients. My windows XP client is running an RDP to the Windows 7 machine, but can't access the shares!

anyone?

I also am experiencing the very same problem. If I reboot the Windows 7 machine, all network shares are accessible again from Windows XP. After a period of time (sometimes a couple of hours), only the Windows XP machines are unable to access the Windows 7 shares. Other Windows 7 machines on the same network are still able to access the Windows 7 shares. Anyone resolved this issue?

 

[Perryg114]

Are all machines on the same workgroup? I just ran into this. Windows XP always installs stuff into Workgroup. Well my home computers are on a different workgroup. It seems that the wizards don't always ask what you want your workgroup name to be. Also XP does not reconize homegroup. My Windows 7 machines did not care if the server and computers were on different workgroups but XP would not let me open shared folders on a different workgroup.

Even if you are setup using a work network in Win 7 you still got to make sure that all the machines are in the same workgroup. It seems that every different OS has different default workgroups etc. The problem is that even when the workgroups are not the same it sorta kinda maybe sometimes works depending on which OS you are using. XP won't let you share with other workgroups at least not by default.

Perry

 

[famfam]

Are all machines on the same workgroup? I just ran into this. Windows XP always installs stuff into Workgroup. Well my home computers are on a different workgroup. It seems that the wizards don't always ask what you want your workgroup name to be. Also XP does not reconize homegroup. My Windows 7 machines did not care if the server and computers were on different workgroups but XP would not let me open shared folders on a different workgroup.

Even if you are setup using a work network in Win 7 you still got to make sure that all the machines are in the same workgroup. It seems that every different OS has different default workgroups etc. The problem is that even when the workgroups are not the same it sorta kinda maybe sometimes works depending on which OS you are using. XP won't let you share with other workgroups at least not by default.

Perry

Hi Perry,

Yes, all the servers are on the same workgroup including the same character casing (all caps). Also, disabled all firewalls. Like I mentioned earlier, everything works good for a while. Then all of a sudden all XP machines cease to connect to Windows 7 server shares. Only way to resolve is to reboot the Windows 7 servers. Rebooting the XP machines does not resolve the issue. Not sure what can be wrong, but seems something on the Windows 7 side. Given that I have no issues with Windows 7 clients, I am looking into upgrading the XP machines to Windows 7.

Any other thoughts will be appreciated...

 

[Zargon]

this thread is very helpful!

 

[willis888]

. . . The Work Network is the one that most of us are going (and need) to use . . .

THANK YOU!

I've been fighting to get XP boxes connected to Windows 7 shared folders for weeks.

 

[Blazer]

leave the homegroup and donot rejoin, by default it active in W7.

 

[muddevil]

Hi Perry,

Yes, all the servers are on the same workgroup including the same character casing (all caps). Also, disabled all firewalls. Like I mentioned earlier, everything works good for a while. Then all of a sudden all XP machines cease to connect to Windows 7 server shares. Only way to resolve is to reboot the Windows 7 servers. Rebooting the XP machines does not resolve the issue. Not sure what can be wrong, but seems something on the Windows 7 side. Given that I have no issues with Windows 7 clients, I am looking into upgrading the XP machines to Windows 7.

Any other thoughts will be appreciated...

Has there been a resolution found for this problem? I've been dealing with this for months - very frustrating! Can access shares for a while, but then (usually overnight) they can no longer be accessed from the XP box. Reboot the Win 7 machine and all is working again.

Help!!!!

 

[bogibogi]

:thumbsup::thumbsup::thumbsup:
I think the SOLUTION for this Windows-share-problem is explained here:
http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017

Finally, I solved my XP-to-Win7 share problem --- Test passed OK

((
"You need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly..."
Set the following registry key to ’1′:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache
and set the following registry key to ’3′:
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size
After making these changes and restarting, I haven’t seen this issue arise again.
))

 

[lowrider69]

Mine is set to home network and I have no problem with my XP machine seeing shares and vice versa. I have homegroup disabled.

 

[WhyWindows]

I have 3 PCs on a wireless home network-one running Win7 (lets name it Win7) and two running XPsp3 (named XP1 and XP2). Win7 can see shares on both XP1 and XP2. XP1 can see shares on Win7 and XP2. XP2, however, could only see shares on XP1 and not Win7. I probably went through most if not more of what has been mentioned above. Connection properties, workgroups, registry values (for ipconfig /all), etc. were identical for XP1 and XP2.

Only thing different was that XP2 required a user logon password when booting up. I removed the requirement for a logon password on XP2 and bingo it now sees shares on Win7 as well as XP1 (sort of a "hail-mary" only option left; and no thanks to MS support for the answer in this case). Why a password protected logon on XP1 would block access to Win7 and not another XP PC is beyond me, let alone how difficult its to find an answer (witness this thread and similar forums); but then, that's Windows. The conspiracy theory in me says such issues are purposeful by MS to bury XP.

 

[lupi]

ugh, came bowsing the forum just now after another shitty vista file share experience to see if they improved it in 7 (cause god forbid it worked fine in XP so why not see just how fucked up we can make in it every version after) and see that there seems to be no improvement.

 

[chillywinter]

I know this is a popular google search but I have followed all the directions there and have had no luck so far. My Windows 7 machine has numerous network shares that are all easily and painlessly accessible by anyone using 7 or Vista. I have 2 Windows XP machines on the network that get access denied errors when I try to access shares on the Windows 7 machine. The Windows 7 machines can access the shares on both the XP machines. All machines have the latest updates.

No machines are running local firewalls
All machines are connected via a wired switch
All machines are under the same User Account without a password
Can access XP shares from Windows 7 but not Windows 7 shares from XP
Windows Vista and 7 machines can properly access shares.

Edit: I got it to work for a while by setting it to work network, but now it stops working after my computer has been on for a day or so. Once I reboot my server it allows XP machines to reconnect, but there is some cut off points after so many hours XP machines can no longer connect.

Same problem here 2 PCs on Win7, and 2 PCs on XP on the same workgroup called mshome. When 1 xp PC stops being able to access a shared HDD on a win7 PC, you can rest assured the other xp PC (my BOXEE media centre) stops accessing the win7 shared HDD also.

I have everything set to least amount of protection you can possibly have (to the point where any linux hacker could have better access to my network than I do), and still I lose connectivity to my shared drives for seemingly no reason.

I agree MS are avoiding providing a solution to this one to persuade upgrades to win7.

I haven't tried the registry hack above yet - might try that now.