After a great deal of testing different scenarios such as stopping the Virus Protection Service (Mcafee in this case), assuring all proper users were in the remote desktop users group, checking to see if windows sucky-ass firewall was running (it was not) we had to resort to any good engineers best tool. Google.
This was more of a challenge than usual because there was a lot of crap on this issue. We had to dig through quite a bit of useless garbage until we finally found a helpful hint. I just want to add it here in hope to make the search for the next sorry sucker who has this issue a little easier. I should add a bunch of meta tags in the code behind this, but I am too lazy for that.
Bottom line that fixed our issue: re-register the remote desktop connection dll.
in a command prompt type in regsvr32 remotepg.dll
Reboot system and voila.
1 comment:
dude, I don't know what it is, but lately I have been re-registering DLL's a lot. Mostly for windows update failures that mysterously popped up in bunches the last 2-3 months, and again today for a windows firewall and WMI service failure. I don't know how people figure out that fix unless you are a microsoft engineer, but I am glad people post these fixes.
Post a Comment