Vista - Vista SP2 breaks local share access from XP computer

I have a home (workgroup, not domain) network with a bunch of Vista SP1 PCs
and one XP SP3 PC. Before I upgraded Vista SP1 PCs to SP2, all PCs could see
and share files among each other. After I upgraded two of the Vista PCs to
Vista SP2, the XP PC cannot see their shared folders. The Vista SP2 PCs show
up in the list, but when I try to see the shared folders I get an error
message "\\XP2PC is not accessible. You might not have permission..." etc.
I've rebooted everything including the router.

All the Vista PCs, whether SP1 or SP2, can see each other's shares. The
problem is only with the XP PC -- it appears that SP2 broke something.
Suggestions?

"Radiophile" <Radiophile@xxxxxx> wrote in message
news:9511D83F-6840-441A-87E9-8DBA3B0E220A@xxxxxxWell SP2 is BETA still AFAIK.......

--
Asking a question?
Please tell us the version of the application you are asking about,
your OS, Service Pack level
and the FULL contents of any error message(s)

On 08.05.2009 19:55, Gordon wrote:http://windowsteamblog.com/blogs/win...l-removed.aspx

--
Jostein Klemmetsrud

On the *Vista* machine you are trying to connect to (from the XP machine)
check the Event Log for System Error 2017.

"The server was unable to allocate from the system nonpaged pool because the
server reached the configured limit for nonpaged pool allocations."

If you see this error a number of times and the time-stamp coincides with
the time you were trying to access shared resources from the XP machine I
may be able to help you. I had this problem before with an XP client (the
rest of my home network is a mix of 32-bit and 64-bit Vista) accessing
resources shared on a Vista machine and the problem only manifested on the
XP client. From memory it was the same message as you are getting.

If it is what I think it might be, it's not SP2 that is the cause, although
I haven't tried accessing any Vista machines with SP2 from XP as yet. I only
have SP2 on one Vista machine so far.

Wayne.


"Radiophile" <Radiophile@xxxxxx> wrote in message
news:9511D83F-6840-441A-87E9-8DBA3B0E220A@xxxxxx

Hi Wayne,

Unfortunately before I saw your post I solved the problem by reverting back
to SP1 on the Vista PCs. Since I reverted by restoring the drive images I
made before installing SP2, I can't go back and check the event log.

I think I can probably stay on SP1 until Windows 7 and avoid the issue
entirely.

John

"Abdul69" wrote:

i am having the same issues!~ not cool at all (esp. when we rely on this for
our business!~)
i cannot believe this is an issue! but man oh man was it ever!~~ i had to
revert back to SP1, luckily i was able to. i have searched up and down for a
solution, is no one else having this issue? we have two vista machines, and 8
XP machines, so i was able to try it on many, and sure enough, vista could
share with vista, but not xp, but if it was vista sp1, it could share with
all xp's, but then upgrading to sp2 for vista, broke all shares~
let me know if there is a solution for this. thank you
p

I'm Having the same problems too... additional also a W2K Prof. Workstation
can't access the Shares on Vista PC's anymore. Accounts/Passwords are the
same an all PC's and it worked fine with Vista SP1 before Vista SP2 was
installed.
Any suggested tips like setting permissions on vista shares and files system
(I even inkluded "Everybody"), disabling all firewalls etc. won't work.
XP and W2K PC's can see the Vista PC's but accessing the Vista PC's (like
NET VIEW \\VISTA-PC ) ends with an access violation Code 5.
Using NET USE X: \\VISTA-PC\MYSHARE will reask to enter user and password,
ending up with same result.
Between Vista PC's there are no troubles at all accessing the shares, also
Vista PC's can access XP and W2K PC's and their Shares without any problems.
It's also seem to be not related to a specific Vista version because I'm
using Vista Business and Vista Home Premium and both have the same problems.

Because this all worked fine prior the VISTA SP2 it's definitly a problem
with the service pack. Can any of the Microsoft guy's give a confirmation on
this?

i changed the workgroup name to something else on all my computers in
the network (for instance, change from MSHOME to workgroup 1.) it can be
anything as long as all the PCs share the same workgroup name. and that
solved the problem. sometimes i hate Microsoft, they throw these bugs at
me that have easy solutions. but i normally wouldn't think about the
workgroup name. i hope this works for you guys!


--
TankMetal
------------------------------------------------------------------------
TankMetal's Profile: http://forums.techarena.in/members/138305.htm
View this thread: http://forums.techarena.in/windows-v...rk/1176561.htm

http://forums.techarena.in