Camelot One
Premium,MVM
join:2001-11-21
Sarasota, FL
clubs:
1 edit | [XP Pro] Strange issue - .Net 3.5 kills Remote Desktop I've been troubleshooting this for more than a week, and I can reproduce the issue every time I try. But strangely, repeated google searches haven't turned up a single comment on it, and I can't believe no one else has run into this.
Windows XP Pro - SP3, whether slip streamed on a fresh install, or installed manually on top of SP2. As soon as you install the .net 3.5 package, the computer no longer functions as a Remote Desktop Host.
There are no errors on either side. Security Audit on the host doesn't show a logon attempt at all. And on the client side, you click Connect, it says "connecting to xxxx", and then just vanishes. No errors, nothing. The "host" in question can still connect to other computers just fine, it just doesn't work as a host.
As soon as I uninstall .net 3.5 and reboot, RDP works again. Install .net3.5, and its dead. I can do this over and over, always the same result.
I've tested this from different client computers, though I am working with the same "host" each time. And I've wiped/reinstalled windows several times during the testing process. It doesn't matter if I use the .net 3.5 redistributable, or the available DotNetAIO cabs available for nlite. If 3.5 is installed, RDP doesn't work.
For clients I've tested from XP Pro SP2, XP Pro SP3, and Vista Ultimate SP1. All running the latest updates.
Has anyone else run into this? Heard of this? Have any suggestions? I know the easy solution is to just not install 3.5, but I have a client who just purchased the Expression Studio 2 package, which requires .net 3.5.
edit - the Test Box/Host is an Intel P35/Q6600 with 4Gb ram and a realtek onboard lan. Latest drivers ofcoarse. |
·
·