Net 3.5 redistrib disables RDP on XP SP3
This is extremely odd as if this was remotely commonplace I would be seeing some Google hits on this, but nothing.
On two machines now (both HP's but one's AMD and one's a Quad-core Intel so quite different hardware), both XP SP3, installing the Net 3.5 restrib disables RDP.
Connection attempts don't tell you anything - you hit connect, you're right back at the server name entry screen - it just flickers for a split second. Nothing in the event log on either machine, no pop-ups whatsoever. You do get the non-verified warning dialog the first time you attempt to connect so it is seeing it, it just can't complete the connection.
Remove Net 3.5 - works. I've tried it on perfectly clean installs as well, so it's nothing else we're loading aside from net 3.5. I can verify use TS Manager that the RDP port is still listening where it should be. uncheck RDP access to remove the listener, reboot, add-in back in, still no go.
Anyone heard of this?
On two machines now (both HP's but one's AMD and one's a Quad-core Intel so quite different hardware), both XP SP3, installing the Net 3.5 restrib disables RDP.
Connection attempts don't tell you anything - you hit connect, you're right back at the server name entry screen - it just flickers for a split second. Nothing in the event log on either machine, no pop-ups whatsoever. You do get the non-verified warning dialog the first time you attempt to connect so it is seeing it, it just can't complete the connection.
Remove Net 3.5 - works. I've tried it on perfectly clean installs as well, so it's nothing else we're loading aside from net 3.5. I can verify use TS Manager that the RDP port is still listening where it should be. uncheck RDP access to remove the listener, reboot, add-in back in, still no go.
Anyone heard of this?
Listening......
I also cannot connect to XP Pro SP3 machines in the same domain & subnet.
The strange things is it was working this morning, but I kept getting Clipboard errors then after a while a
another error "Out of memory". After rebooting the remote machine, I couldn't connect at all.
I am an administrator on both machines.
I can still connect to our Windows 2K SP4 server from both machines.
Tried:
Disabling the firewall on remotely and locally.
Disabling RDP (Control Panel / System / Remote) then reanbling it.
This site points to a registry CLSID, but doesn't say what to change.
http://www.bit-tech.net/news/2008/05/21/xp-sp3-breaks-whs-rdp/1
Steps to take before you install Windows XP Service Pack 3
http://support.microsoft.com/kb/950717
This article explains about why session 0 is no longer available to users.
http://www.badkey.com/db/blogsphere.nsf/d6plinks/JWIE-7EHJFH
I hope something here will give you the inpiration to find the answer.
I'll keep looking and get back to you if I find anything that could be useful.
In the meantime, still listening.........
I also cannot connect to XP Pro SP3 machines in the same domain & subnet.
The strange things is it was working this morning, but I kept getting Clipboard errors then after a while a
another error "Out of memory". After rebooting the remote machine, I couldn't connect at all.
I am an administrator on both machines.
I can still connect to our Windows 2K SP4 server from both machines.
Tried:
Disabling the firewall on remotely and locally.
Disabling RDP (Control Panel / System / Remote) then reanbling it.
This site points to a registry CLSID, but doesn't say what to change.
http://www.bit-tech.net/news/2008/05/21/xp-sp3-breaks-whs-rdp/1
Steps to take before you install Windows XP Service Pack 3
http://support.microsoft.com/kb/950717
This article explains about why session 0 is no longer available to users.
http://www.badkey.com/db/blogsphere.nsf/d6plinks/JWIE-7EHJFH
I hope something here will give you the inpiration to find the answer.
I'll keep looking and get back to you if I find anything that could be useful.
In the meantime, still listening.........
hmm i seem to have found something
see if this has any relevance as its basically after service pack install
https://www.experts-exchange.com/questions/22935104/The-Terminal-Services-Active-X-control-mstscax-dll-does-not-match-the-version-of-the-Client-Shell-What-is-going-on.html
see if this has any relevance as its basically after service pack install
https://www.experts-exchange.com/questions/22935104/The-Terminal-Services-Active-X-control-mstscax-dll-does-not-match-the-version-of-the-Client-Shell-What-is-going-on.html
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
it could be a problem with the RDP-TCP Listener
delete it and reload it