Windows June 2011 Update: Breaks network share?
Suddenly a WinXP client machine couldn't see a NAS shared by workgroup it has been accessing for years. Other machines - Win7, Win2003, and WinXP - could still see the NAS.
I investigated "everything" without finding a clue. Finally I did a system restore to Jun. 14th morning ... and voilá, the network drive was back!
Anyone else have seen this? I've searched on Google hi-and-lo without finding anything at all which I find a bit strange.
/gustav
I investigated "everything" without finding a clue. Finally I did a system restore to Jun. 14th morning ... and voilá, the network drive was back!
Anyone else have seen this? I've searched on Google hi-and-lo without finding anything at all which I find a bit strange.
/gustav
johnb6767
Which update?
ASKER
The automatic updates for June 2011.
/gustav
/gustav
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This seems to be have been tracked down to the KB2536276 update. It breaks unencrypted Samba from at least Windows XP.
http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/why-is-update-kb2536276-causing-a-block-in/4b3536b7-b6b4-43fc-a973-c75ea478c7ca?tm=1308409382437&page=1
Does this make sense to you?
Don't know how that explains issues in network without Samba.
/gustav
http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/why-is-update-kb2536276-causing-a-block-in/4b3536b7-b6b4-43fc-a973-c75ea478c7ca?tm=1308409382437&page=1
Does this make sense to you?
Don't know how that explains issues in network without Samba.
/gustav
ASKER
ASKER
Did a rollback (cancel) of the System Restore and the sharing issue returned.
Did a uninstall of KB2536276 and reboot and the issue was removed.
So KB2536276 is the source of this misbehaviour.
Thanks for your debuggin input which I didn't know about.
/gustav
Did a uninstall of KB2536276 and reboot and the issue was removed.
So KB2536276 is the source of this misbehaviour.
Thanks for your debuggin input which I didn't know about.
/gustav
ASKER
Remove the KB2536276 update until further notice.