Remote Desktop stopped working after KB926122

[richecker]

We have 8 servers running windows server 2003. I recently installed the latest updates which included KB926122 (denial of service for remote code execution). Now all of those servers are on a domain however the workstations are rarely ever attached to that domain. Most of the workstations are developer stations and they simply dont need to be joined to a domain (we are a small outfit) and I usually am not attached to the domain as well. I usually run remote desktop to connect to the servers and after installing the latest update, it is not working now. What is the best solution? Should I uninstall the update? Or is there a better workaround? I would rather keep the update as these servers are connected to the internet and for security purposes.

[cluberti]

I would suggest removing the update on one or two of the servers and rebooting, to see if removing the update resolves the issue - if not, then it was something done before the reboot that caused the issue. However, if the update removal does resolve the issue, contact microsoft and tell them the update broke remote desktop - you'll get a free case to troubleshoot, and we can help you figure it out as well.

[richecker]

I already removed the update and it did work. I forgot to mention it.

[cluberti]

Ah - that's good information to know . If the update does cause the issue, then I would probably say that contacting Microsoft and getting them to figure this out for you is a good idea. However, if you're up for trying to figure it out yourself, check some basics first - like, is the box listening on 3389 on 0.0.0.0, does a network trace running at either end show any errors during the TS setup, make sure the security on the RDP listener can be set to client compatible or low as a test if it isn't already, etc.

I'm all for seeing a network trace and a netstat to check that we're listening on 3389, and what actually comes over the wire during a TS connection attempt...

[Bad boy Warrior]

Just to add to that i had a similar issue. The way i resolved it was by logging onto the server turning off RDP - restarting turning RDP back on, at this stage you can either restart again or give it a few minutes before attempting to RDP to the machine.

[richecker]

Thanks guys for the help. I got so back logged that I forgot to tell you guys that all I did was what bad boy described. It worked fine for me.