The following fatal alert was generated: 10 EVENT ID 36888

q: We noticed this event in the Server 2008 System Event Logs of a customer system on a very regular basis.

Log Name: System
Source: Schannel
Event ID: 36888
Level: Error
Message: The following fatal alert was generated: 10. The internal error state is 1203.

a: We noticed this was happening at 4am every morning and realized that Spiceworks was configured to scan systems starting at that time.  We have not resolved the error just yet but at least we've associated it to an application.

Server 2008 listening on port 80

q: we have a server that is listening on port 80 but neither IIS nor World Wide Web is installed.

• netstat -ano | find ":80"
• Returns that PID 4 (SYSTEM) is listening on port 80

a: SQL Server is installed on the box and with it came "SQL Server Reporting Services (MSSQLSERVER).  When we stopped that service the server was no longer listening on port 80.

Microsoft AppFabric 1.1 ERRPS024

q: After performing an in place upgrade of AppFabric 1.0 to 1.1 we were unable to run the Grant-CacheAllowedClientAccount command without receiving this response.

Grant-CacheAllowedClientAccount : ErrorCode<ERRPS024>:SubStatus<ES0001>:This co
mmand is not currently allowed. Changes to the cache cluster configuration is r
estricted during a rolling upgrade of the caching service.
At line:1 char:32
+ Grant-CacheAllowedClientAccount <<<<  domain\username
   + CategoryInfo          : NotSpecified: (:) [Grant-CacheAllowedClientAccou
  nt], DataCacheException
   + FullyQualifiedErrorId : ERRPS024,Microsoft.ApplicationServer.Caching.Com
  mands.GrantCacheAllowedClientAccountCommand

a: We finally found the solution on a Russian MSDN Page.

http://msdn.microsoft.com/ru-ru/library/hh343304(v=azure.10).aspx

• Open the Elevated AppFabric PowerShell prompt
• run - Get-CacheHost (Notice the version 3[1,3])

HostName : CachePort Service Name            Service Status Version Info
-------------------- ------------            -------------- ------------
HOSTNAME:22233         AppFabricCachingService UP             3 [1,3][1,1]

• run - Update-CacheHostAllowedVersions -BeginServerVersion 3
• run - Get-CacheHost (Notice the version 3[3,3])

HostName : CachePort Service Name            Service Status Version Info
-------------------- ------------            -------------- ------------
HOSTNAME:22233         AppFabricCachingService UP             3 [3,3][1,1]

• Run - Update-CacheHostAllowedVersions -EndClientVersion 3
• Run - Get-CacheHost

HostName : CachePort Service Name            Service Status Version Info
-------------------- ------------            -------------- ------------
HOSTNAME:22233         AppFabricCachingService UP             3 [3,3][1,3]

• Run - Update-CacheConfigurationStore

WARNING: The changes will take effect only when the hosts are restarted.

• Run - Stop-CacheCluster

HostName : CachePort     Service Name            Service Status Version Info
--------------------     ------------            -------------- ------------
HOSTNAME.gdcii.local:22233 AppFabricCachingService DOWN           3 [3,3][1,3]

• Run - Start-CacheCluster

HostName : CachePort     Service Name            Service Status Version Info
--------------------     ------------            -------------- ------------
HOSTNAME.gdcii.local:22233 AppFabricCachingService UP             3 [3,3][1,3]

View my website in different forms including mobile

q: How can I quickly view my website as seen by various devices (eg: mobile, tablet, etc)?

a: Responsive.is - simply visit this site with your URL after the / and it will wrap your site in a Responsive Web Viewer.  Example: http://responsive.is/fix.lazyjeff.com

Remote Desktop Connection fails - outdated entry in the DNS cache

q: Remote Desktop Connection: The connection cannot be completed because the remote computer that was reached is not the one you specified.  This could be caused by an outdated entry in the DNS cache.  Try using the IP address of the computer instead of the name.

a: Using the IP worked and when we reached the virtual guest we discovered the time was off by 15 minutes.  The easiest way to resolve this is to run the two commands below, logoff, then try to RDP back into the guest using it's name.

• net stop w32time
• net start w32time