Windows XP can't access Server 2012 File Cluster

I ran into this one today and it took me all morning to finally find a fix for it.  It appears this is a known issue with Microsoft and even though they have a supposed "hot-fix" for it you can install on the 2012 file servers that doesn't fix it.

There is however a work around that immediately fixed the problem for me once I found it out about it.

The text of the error follows:

You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Logon Failure: The target account name is incorrect.

I also noted in the event log on the client a kerberos event failure every time the share was attempted to be accessed.

Event Type: Error Event Source: Kerberos

Event Category: None

Event ID: 4

Date: 14/05/2013

Time: 08:27:30

User: N/A

Computer: XPClient

Description:

The kerberos client received a KRB_AP_ERR_MODIFIED error from the server fileservernode$. The target name used was cifs/Server.domain.int. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (Domain.INT), and the client realm. Please contact your system administrator.

Open Failover Cluster Manager

Go to Roles - Resources Tab - File Server

Right Click the File Server role - Take Offline

Wait for it to go offline, then Right Click - More Actions - Repair

Wait for it to come back online

This seems to take care of the problem....also while you're at it upgrade from XP.  :)

Fix VSS Errors Windows XP and Server 2003

Installing a backup device that uses a backup agent means the VSS writers have to be free of errors.  You can fix this by opening a command prompt (administrator level if needed) and typing in "vssadmin list writers".  This will run for a few seconds then list all of the writers on the system.  They should all show as "stable and ready".  If they are not, below are the steps you can take to fix this problem.

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions

3. On the Edit menu, click Delete, and then click Yes to confirm that you want to delete the subkey.

4. Exit Registry Editor.

5. Click Start, click Run, type services.msc, and then click OK.

6. Right-click the following services one at a time. For each service, click Restart:

• COM+ Event System
• COM+ System Application
• Microsoft Software Shadow Copy Provider
• Volume Shadow Copy

7. Click Start, click Run, type cmd, and then click OK.

8. At the command prompt, type vssadmin list writers, and then press ENTER.

9. If the VSS writers are now listed, close the Command Prompt window. You do not have to complete the remaining steps. If the VSS writers are not listed, type the following commands at the command prompt. Press ENTER after each command.

• cd /d %windir%\system32
• net stop vss
• net stop swprv
• regsvr32 ole32.dll
• regsvr32 oleaut32.dll
• regsvr32 vss_ps.dll
• vssvc /register
• regsvr32 /i swprv.dll
• regsvr32 /i eventcls.dll
• regsvr32 es.dll
• regsvr32 stdprov.dll
• regsvr32 vssui.dll  (does not work in Windows XP)
• regsvr32 msxml.dll
• regsvr32 msxml3.dll
• regsvr32 msxml4.dll

Note The last command may not run successfully.

10. At the command prompt, type vssadmin list writers, and then press ENTER.

11. Confirm that the VSS writers are now listed.

12. At the command prompt, type vssadmin list shadows and then press ENTER.

13. Confirm that there are no errors listed.  On Windows XP you should see: No shadow copies present in the system.

14. Congratulations your machine should work again with any VSS compatible programs.