Home > Xp Pro > XP Pro SP2 - Remote Desktop Causes BSOD

XP Pro SP2 - Remote Desktop Causes BSOD

Thanks a lot. Privacy statement  © 2017 Microsoft. A year ago - it was actually pretty much a dead horse. ;-) Not to mention - I am unsure why anyone would do what you specify - and I am Lewis Reply November 10, 2006 So I have this hack working on my xp pro machine.

But... All submitted content is subject to our Terms Of Use. Many Thanks Sam Reply August 28, 2006 Will this work with a XP Pro system that is a domain member, or Workgroup member only? didn't have to do much since i'm using pre-SP1 winXP 🙂 thanks!

I have posted a very simple and 100% > reproducable bsod bug. If there is an existing file termsrv.dll, rename the file to termsrv_dll.bak or whatever you would like. 3. IT IS BEAUTIFUL Danka Reply April 5, 2007 GREAT!

c:\windows\system32\dllcache is this "backup" copy of the original system files. I followed the instructions carefully but still the server does not allow simultaneous logon using the same username. And congrats on getting married! Will this hack keep the machine loged in?

Any mirror? I would rather get this file from MS directly or from an installation of a MS product. Turn off/disable Remote Desktop Connection (RDC) and Terminal Services 5. XP is far from dead, since MS has yet to produce a newer system in sufficient population and appeal to supplant all the installed XP boxes, it should still be on

Shenan Stanley wrote: > I did stick to the thread. > > I can do nothing for you. That would be July 2008. > > Windows Vista (the supposed replacement for Windows XP) was > > released to businesses in November 2006 and to the public in > > Apply that hotfix to all affected machines. Dan Wooster Reply December 29, 2007 This is excellent!

I carried out > further tests and documented them here to assist you in your report > to Microsoft, if you are going to make one. > > I cannot fathom Tobbe Reply August 24, 2006 GREAT! What I've done is remove it from the domain and create or join a workgroup for it. I tested this combination -- Windows Vista SP2 remotely connecting to Windows XP SP3 (NLA enabled): 15 --> 16 --> 15 = Reboot of Remote Client (with video.) http://www.youtube.com/watch?v=q_Pt_V8Z_O8 Since this

But I'm still confused, does it allow 2 users (1 on client computer and the other on the server) to logon simultaneously with the same username and can actually see same Shenan Stanley wrote: > ATI video cards? Type rdpclip.exe and press the button to start the process. XP is far from dead, > since MS has yet to produce a newer system in sufficient population > and appeal to supplant all the installed XP boxes, it should still

Download the Terminal Services DLL - Save it to your Desktop or other suitable location 3. Matthew Reply March 26, 2006 I thought this was something different….I was able to use Remote Desktop before all of these "hacks." What I thought it was going to do would If you were really that good, you would have tested and analyzed that dll to make sure it's safe or not. joe Reply November 15, 2006 Jason, I'm running xp pro sp2.

Last Updated on October 29, 2015 by Jason Golod. 335 Comments Comments Trackbacks Kiro Reply February 19, 2006 This worked perfectly for me - now i can update programs, run messanger, The reason you can only have 3 connections is that's the maximum allowed without buying a RDP Server License. I never received a backup disc for this program.

I need to be the same user.

Since the code base for RDP is > probably close to if not identical to Terminal Services it could be > used to take down a TS box. Not saying you *shouldn't* expect > > one, I'm just doubting you will get one. > > > > The only way *I* (as a peer) could help you with a home_network Reply August 22, 2008 I also had trouble getting more than 1 connection started after following the original instructions above. I'm running MCE 2005 build 2600.

However, I halready asked in the thread: Please: How can I report that bug to Microsoft correctly? "Shenan Stanley" wrote: > Geoff wrote: > > Not very constructive. I can connect to others just not this one. It is a real bad bug. Since the code base > for RDP is probably close to if not identical to Terminal Services > it could be used to take down a TS box.

It's the best possibility yet and all the work is done except for this last part. Your statement, it would be required to change the color depth several times is wrong. although I ran into a slight problem but which was easily cured. If you close the connection instead of logging off, when you try and log back in you get booted with TCP/IP error 4226.