The Windows Filtering Platform has blocked a bind to a local port.
I recently came across this problem while reviewing auditing logs on a Server 2008 SP2 machine - but to my surprise this was a false alarm.
The Windows Filtering Platform has blocked a bind to a local port.Application Information: Process ID:Â Â 976 Application Name:Â \device\harddiskvolume1\windows\system32\svchost.exeNetwork Information: Source Address:Â Â fe80::58b4:5ea5:fc97:b422 Source Port:Â Â 546 Protocol:Â Â 17Filter Information: Filter Run-Time ID:Â 0 Layer Name:Â Â Resource Assignment Layer Run-Time ID:Â 38
As you can see, Filter Run-Time ID is equal to 0. Also, the layer name is Resource Assignment.
According to Biao Wang over on MSDN, this is a bug discovered in Windows Filtering Platform:
http://social.msdn.microsoft.com/Forums/en-US/wfp/thread/774026e6-a771-418a-b531-22183ef399f8/
Also this KB article details the symptoms, as well as a hotfix:
http://support.microsoft.com/kb/969257
The root cause is the Windows Filtering Platform is still used by other parts of the OS, like IPSec, even when the firewall service is disabled. Furthermore, firewall filtering rules will still be in effect.
Many of us are accustomed to disabling the Windows Firewall service to disable the firewall, rather than going through firewall.cpl.
The easiest way to resolve this in our environment was to re-enable the Windows Firewall service, and this run firewall.cpl and select Turn Windows Firewall on or off and click "Off (Not Recommended)".
Create NAS datastore Error – NFS Setup on ESX 4.1
Trying to mount  an NFS datastore in vCenter I got the following Errors:
vCenter error dialog:
Operation failed, diagnostics report: Unable to complete Sysinfo operation. Â Please see the VMkernel log file for more details.
/var/log/vmkernel errors:
NFS: 149: Command: (mount) Server: (10.0.0.10) IP: (10.0.0.10) Path: (/mnt/servers/vmdk/vmdk) Label: (DEV-SERVERS) Options: (None)WARNING: NFS: 946: MOUNT RPC failed with RPC status 13 (RPC was aborted due to timeout) trying to mount Server (10.0.0.10) Path (/mnt/servers/vmdk/vmdk)NFS: 160: NFS mount 10.0.0.10:/mnt/servers/vmdk/vmdk failed: Unable to connect to NFS server
This turned out to simply be caused by the filer, in this case OpenFiler, not being able to resolve the hostnames of the ESX hosts. The DNS servers it referenced were returning Data network IPs instead of Storage network IPs, which don't cross-talk in our environment.
The fix was to simply add entries to /etc/hosts on OpenFiler with the correct IPs:
10.0.0.54 esx1 esx1.domain.local 10.0.0.55 esx2 esx2.domain.local 10.0.0.56 esx3 esx3.domain.local
Web sites hosting the patch definitions and patches cannot be accessed or have no patch data
VMware Update Manager gives the following error:
Download patch definitions
hostname.domain.local
Web sites:
https://hostupdate.vmware.com/software/VUM/PRODUCTION/ind-
ex.xml; hosting the patch definitions and patches cannot be
accessed or have no patch data. Check the Internet connectivity.
DOMAIN\user
hostname.domain.local
2/9/2011 4:31:18 PM
2/9/2011 4:31:18 PM
2/9/2011 4:32:55 PM
Check to make sure you can access that xml file in IE from the vcenter server
Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.
I experienced this problem in my environment because we use Backup Exec. When I deployed VMWare Data Recovery, it uses VSS to quiesce the file system before taking a backup snapshot.
Well, as it it turns out... Backup Exec's Remote Agent also includes a VSS component, and they break each other when a VSS request comes in.
Here is the VMWare article I found, which was MOST useful. It includes links to Symantec's articles on the same issue, and even resolution steps with all caveats documented. Read carefully at the bottom of the Symantec articles, there is good info there.
Set all user’s home directories with PowerShell
Get-ADUser -SearchBase "OU=Users,DC=test,DC=ad" | % { Set-ADUser $_ -HomeDrive "H:" -HomeDirectory ('\\fileserver\home\' + $_.SamAccountName) }
Let me explain how this works briefly:
Get-ADUser = Get users from AD-SearchBase "ldap" = Root of the tree in AD to get users from| = Pipe, provide input of query to...% = ForEach item piped from querySet-ADUser = Write changes to AD$_ = item piped from query-HomeDrive "X:" = Sets home drive letter, requires colon and quotes!!-HomeDirectory = Home drive path$_.SamAccountName = item piped from query's property "SamAccountName" aka username.
We chose to use the username for the folders in the home directory storage, you don't necessarily have to.
Notice the (paranthesis) which tell Powershell to take my string \\fileserver\home\ and variable $_.SamAccountName and mush them together, passing both as the final string to -HomeDirectory
Thanks #powershell on Freenode and MS documentation examples
Technet on Set-ADUser: