-Problem-

Windows Vista can’t connect to a Windows XP computer file share. You keep getting a logon unsuccessful error message even though you are using a correct username/password.

-Solution-

Method 1:

NOTE: This method is for Vista Business, Ultimate, and Enterprise versions only. For Vista Home versions see the second method.

1. Open Administrative Tools. (In Control Panel after clicking on “Classic View” on the left side bar)
2. Click Local Security Policy. (click continue on security dialog)
3. In the left pane, click the triangle next to Local Policy.
4. In the left pane, click Security Options.
5. In the right pane about 3/4 the way down, double click “Network security: LAN manager authentication level”.
6. Click the drop down box, and click Send LM & NTLM - use NTLMv2 session security if negotiated.
7. Click OK.
8. Restart the computer.

Method 2: (required for home editions of Vista, not recommended for novice users)

1. Open the Start Menu.
2. In the white line (Start Search) area, type regedit and press Enter.
3. Click Continue on the security dialog.
4. In regedit, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
5. In the right pane, right click LmCompatibilityLevel and click Modify.
NOTE: If it doesn’t already exist, create a DWORD value named LmCompatibilityLevel
6. Set the value to 1
7. Reboot

Repairing “Orphaned Snapshots” in Vmware ESX Server v3.5.

This issue seems to be caused when running a VCB on the VM while it is running. Most notably this seems to be a bigger issue with database servers running in VM’s.

-The Problem-

While running a VCB job a snapshot is created and then should be deleted afterwards. If the process of removing the snapshot fails under certain conditions it can leave what Vmware calls an “orphaned snapshot”

When your snapshots get orphaned, the VM continues to save any new data into a “snapshot disk”. This disk will be physically separated from you VM’s normal disk image file, and will not actually show up as used space on the data store free space calculation. This in turn can cause your data store to become full and not allow your VM to power on correctly.

You can verify if an orphaned snapshot exists in your VM if you look at the virtual disk in the VM settings and see a disk file location that looks like ???-000001.vmdk. This is the snapshot disk being used as the disk image.

-The Solution-

All of the below steps are done from the Infrastructure Client and the command line console. Please read through them and understand each step before you begin, as once you start you must finish.

1. Check to see if you have any snapshots in the snapshot manager. If you do not, continue to step 2. If you do, use the delete all option and see if this resolves the issue (if not go to step 2).

2. Shut down and power off the VM (if it is not off already). You should not shut down the VM with any active snapshots present.

3. After the VM is fully powered off, create a single snapshot of the VM and do not power up after this step.

4. Browse your data store for the VM and look for the numbers on you .vmdk files. The most recent snapshot should only be a few megabytes, and you want the one that is right before that.

5. Go to the command line console and edit the .vmx file for your VM in the data store container. Look for a section similar to the following for each of your virtual disks.

scsi0:0.present = "true"
scsi0:0.fileName = "???-00002.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"

You want to edit the “scsi0:0.fileName =” section to the same file name that you found in step 4. You have to repeat this throughout the file for each virtual disk on your VM.
Save the .vmx file, overwriting the original.

6. Now, this is going to be a long process if the .vmdk files are large (over 20 gigs) and could take several hours. During this process you may loose connectivity to your ESX server on the infrastructure client. What you need to do is run the command below from within the VM’s data store container.

vmware-cmd <your .vmx file> removesnapshots


7. After the previous step is completed check your VM settings in the infrastructure client and verify that your virtual disks are now pointing to the original .vmdk file (does not contain -00001 etc.). If everything completed successfully you should be able to power up your VM.

8. After the VM is powered on and you verify operation, you can delete the last numbered -0000x.vmdk that was created from your snapshot in the third step (should only be a few megabytes). This file should have been ignored by the snapshot removal because you changed the .vmx file.

On my system I noticed the infrastructure client became unresponsive after checking the VM settings (hung on reconfigure virtual machine) and would not let me power on the VM. I had to run service mgmt-vmware restart to restart the management services so I could power it on.