 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows XP / Remote Desktop / May 2008Problems logging in locally after Remote Desktop session
I have read a great many posts about Remote Desktop issues but cannot find anything which explains exactly what I am seeing. The scenario .. I have two computers, a Lenovo T61 laptop running XP Pro SP2 and a home built desktop machine, also running XP Pro SP2 My desktop machine is connected to a Linkysys WRT54GS router via a wired connection. My laptop is connected to the same router but using a wireless connection. From my laptop I am able to remote desktop into my desktop machine. However, when I kill my remote desktop session, on my desktop machine the login screen still says that I am logged in. I am not sure if this is indicative of a problem or not. Next, I log in at my desktop machine but all that happens is that the screen goes black and I am unable to do anything. Even CTRL-ALT-DEL doesn't do anything. Note that the same problem happens if I use a wired connection from my laptop to the router. On this black screen, at the top right I see the Kaspersky Internet Suite 7 logo. At first I thought that it was Kaspersky which was causing the problem so I completely uninstalled it and repeated the experiments. This time I get the same black screen, but without the Kaspersky logo. The only way that I have found to get my desktop machine back up and be able to log back in is to do a hard reset or power cycle. Note that this issue happens when I try to remote desktop on my local network, I am not trying to get in via the public internet. No VPN is involved. I use the same laptop at work to remote desktop into other XP machines at work (over a local network) and Remote Desktop works fine. Does anyone l any idea what could be causing these problems? thanks in advance for your help By "kill my remote desktop session" do you use a log off or disconnect or simply click on the little x in the top right corner of the Remote Desktop [RDC] display?  SignatureAl Jarvi (MS-MVP Windows – Desktop User Experience) Please post *ALL* questions and replies to the news group for the mutual benefit of all of us... The MS-MVP Program - http://mvp.support.microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights... How to ask a question http://support.microsoft.com/KB/555375 >I have read a great many posts about Remote Desktop issues but cannot find > anything which explains exactly what I am seeing. The scenario .. [quoted text clipped - 42 lines] > > thanks in advance for your help I am sorry, 'killed' was a bad choice of word. Yes, I click on the little X at the top right hand corner of the Remote Desktop screen on my laptop. > By "kill my remote desktop session" do you use a log off or disconnect or > simply click on the little x in the top right corner of the Remote Desktop [quoted text clipped - 46 lines] > > > > thanks in advance for your help What happens if you Logoff or Disconnect from the RDC session? SignatureAl Jarvi (MS-MVP Windows – Desktop User Experience) Please post *ALL* questions and replies to the news group for the mutual benefit of all of us... The MS-MVP Program - http://mvp.support.microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights... How to ask a question http://support.microsoft.com/KB/555375 >I am sorry, 'killed' was a bad choice of word. > [quoted text clipped - 60 lines] >> > >> > thanks in advance for your help I will try this when I get home. I must admit that I have never used 'log off' before with Remote Desktop, I have always just hit the 'x' and closed the window. This is how we always use it at work. Maybe there is something different with the setup of the computers at work which allows it to be used in that way. I wanted to check though that the correct way to log off a Remote Desktop session is to select the Start button in the remote desktop window, then in the RD window again, select 'log off'? Also, given that I am the same user as one my desktop machine, shouldn't I just be able to close the RD window in this way, and just walk over to my desktop machine, enter my password and bring up same window? I will try the experiment you suggested and update this thread tonight. thanks for your help. > What happens if you Logoff or Disconnect from the RDC session? > [quoted text clipped - 62 lines] > >> > > >> > thanks in advance for your help I tried logging off from the Remote Desktop session (rather than just closing it with the 'x') but I still see the same problems. Here are the results of a couple more experiments I ran tonight: Key: 'DESK' = desktop PC 'LAPT' = laptop As before, DESK is connected to my Linysys router using wired connection, whereas my LAPT is connected to the same router wirelessly. Experiment #1 ============= 1: log into DESK -> logs in ok 2: On LAPT, RD to DESK -> logs in ok (DESK shows user logged in) 3. log off RD (RD session ends - 'Your remote session ended'), DESK goes back to normal login screen 4. Login to DESK machine -> logs in ok 5. restart DESK -> comes up with black screen with Kaspersky logo at top right. Unresponsive to keyboard, mouse ok 6. hit reset/power button on DESK -> comes up ok with usual login screen Note that the Kaspersky logo on the black screen is the same logo I see at the top right of the regular windows login screen Experiment #2 ============= 1. On DESK, run Kaspersky removal tool to completely remove all traces of Kaspersky Internet Suite 7 2. restart DESK 3. Log into DESK -> logs in ok 4. On LAPT, RD to DESK -> get black screen on LAPT! 5. Close RD 6. On LAPT, RD to DESK again -> get blue screen with login dialog box frozen! 7. Close RD 8. On LAPT, RD to DESK again -> get blue screen with login dialog box frozen! 9. On DESK, log in -> logs in ok, but wallpaper has gone! 10. restart DESK -> comes up with black screen (no Kaspersky logo). Unresponsive to keyboard, mouse ok 11. hit reset/power button on DESK -> comes up ok with usual login screen 12. Log into DESK -> logs in ok If there are any other experiments I can carry out to help debug this, please let me know. thanks > I will try this when I get home. I must admit that I have never used 'log > off' before with Remote Desktop, I have always just hit the 'x' and closed [quoted text clipped - 80 lines] > > >> > > > >> > thanks in advance for your help It really sounds to me like Kapersky has hosed (that's a technical term) up something on DESK. You might look at the event viewer on DESK to see if you can find any clues to what is happening. Also, do you have a restore point created prior to all of this happening that you might try to recover from? FWIW, I would also use the "disconnect" from RDC function versus "log off." That way you stay logged on with any programs you have running still running. SignatureAl Jarvi (MS-MVP Windows – Desktop User Experience) Please post *ALL* questions and replies to the news group for the mutual benefit of all of us... The MS-MVP Program - http://mvp.support.microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights... How to ask a question http://support.microsoft.com/KB/555375 >I tried logging off from the Remote Desktop session (rather than just >closing [quoted text clipped - 155 lines] >> > >> > >> > >> > thanks in advance for your help Unfortunately I do not have a restore point set, and to be honest I don't really know how long this problem has been around. I have been using the XP Pro install on DESK for probably a couple of years now without a reinstall. Remote Dekstop could have been broken for some time but I would not have known about it. This is the first time I have tried Remote Desktop into this machine, unfortunately it failed miserably the first time :-( I ran an experiment as you suggested, I did all the steps I mentioned in my last post and did them on 5 minute intervals. Then at the end of the experiment checked the Event and System Log on DESK, but there was absolutely no problems reported during these times. If my Windows is corrupted (by Kaspersky?) in some way, is there a way to fix it other than by a complete reinstall? In every other way DESK is running perfectly, it seems a real pain to have to reinstall everything just because RD doesn't work. I have another PC, currently running Linux which I could reformat and install XP Pro SP2. I won't be able to register it with Microsoft since I don't have another license but that shouldn't matter for testing as it will have some time to do the testing before Microsoft locks the OS. > It really sounds to me like Kapersky has hosed (that's a technical term) up > something on DESK. You might look at the event viewer on DESK to see if you [quoted text clipped - 166 lines] > >> > >> > > >> > >> > thanks in advance for your help * You can reregister Remote Desktop by running the following command from a command prompt. Make sure you have administrator privileges. Reboot the PC after doing this... regsvr32 remotepg.dll * The fix of last resort is a "Repair Reinstall" of the OS. Backup any critical data just in case. Note the warnings on the page... http://michaelstevenstech.com/XPrepairinstall.htm Good luck and sorry I can't be of more help... --- Al Jarvi (MS-MVP Windows – Desktop User Experience) Please post *ALL* questions and replies to the news group for the mutual benefit of all of us... The MS-MVP Program - http://mvp.support.microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights... How to ask a question http://support.microsoft.com/KB/555375 > Unfortunately I do not have a restore point set, and to be honest I don't > really know how long this problem has been around. I have been using the [quoted text clipped - 23 lines] > will > have some time to do the testing before Microsoft locks the OS. Unfortunately, 'regsvr32 remotepg.dll' didn't help. I have not taken the plunge and ran 'repair reinstall' yet. Instead,, I decided to install XP Pro SP2 on another PC and also installed Kaspersky Internet Security 7. This comuter doesn't exhibit the probelm, i.e. I don't see a black screen after restart. The only think is that the patch status is not the same as my 'DESK' machine. I don't think I will be able to install the updates from Microsoft however as I can't register it as I dont have a second license. I am going to ponder doing the resinstall on my DESK machine. I can't help thinking there is some setup on my DESK machine which is causing the problem, or some conflicting app. I have ran Advanced System Optimizer to clear up all the registry and other problems it could find but that didn't help either. thanks for all your help. > * You can reregister Remote Desktop by running the following command from a > command prompt. Make sure you have administrator privileges. Reboot the PC [quoted text clipped - 48 lines] > > will > > have some time to do the testing before Microsoft locks the OS. Hi, I have some more results, this time from experiments which suggest the issue is to do with the driver for my video card .. I went into msconfig and turned on boot logging. I then repeated the previous experiments. First I saved the boot log for a regular startup of windows, then I did the remote desktop, followed be disconnect and a restart (which resulted in the black screen with the Kaspersky logo). I then did a hard reset (to get it out of the 'blank screen' mode' and compared the two boot logs. I could see some differences, presumably because different drivers are loaded when doing a regular windows boot vs a restart, however the two logs diverged significantly when it got to the point of loading nv4_mini.sys. This is the Nvidia compatible Windows 2000 minport driver. So I then decided to upgrade to the latest Nvidia drivers (I already had quite a recent one. Now the results of my experiments are very different ! Instead of a black screen following the restart (after ending a remote desktop session from LAPTP) it now comes up with the Windows login screen (that's the good news). The bad news is that my screen has switched to 640x480 at 4bit colour depth ! Maybe I have just introduced a new, unrelated problem but my suspicion is that all the problems all along have been down to my video card/driver. I am using an Asus EN7600GT Pci Express card with 256MB DDR3. Up to now it has worked virtually flawlessly, however I did have to upgrade from the Asus driver to the generic Nvidia one some time ago to fix some problem (I can't remember what it was) I am going to do some research on the Nvidia and Asus forums to see if I can come up with anything. > Unfortunately, 'regsvr32 remotepg.dll' didn't help. > [quoted text clipped - 67 lines] > > > will > > > have some time to do the testing before Microsoft locks the OS. Google is a wonderful thing :-) Just did a quick search and it came up with this .. http://forums.nvidia.com/lofiversion/index.php?t48628.html > Hi, I have some more results, this time from experiments which suggest the > issue is to do with the driver for my video card .. [quoted text clipped - 101 lines] > > > > will > > > > have some time to do the testing before Microsoft locks the OS. > Google is a wonderful thing :-) > [quoted text clipped - 107 lines] > > > > > will > > > > > have some time to do the testing before Microsoft locks the OS. I am having the same problem. I also saw that article, but there was no response, and did you notice the date? I tried with the latest NVidia driver, and also a standard Windows driver. With the standard Windows driver, the resolution reverts to 800x600x4bit. Any other ideas? John Hi John, first I am going to go back to my previous driver version but use the one posted for my Asus card on the Asus website. If I still have the same problem then I will probably have to seek help either from Asus or from Nvidia, neither of which is going to get me a solution quickly and maybe never. I could also see if I can get in touch with the original poster to see if he ever found a solution. > > Google is a wonderful thing :-) > > [quoted text clipped - 120 lines] > > John Looks like there are a slew of problems with the later Nvidia forceware drivers which are casuing problems with Remote Desktop. Not necessarily the same as we are seeing but it appears that Nvidia are working on some fixes. See .. http://forums.nvidia.com/index.php?showtopic=67147&hl=remote+desktop I am going to read up on what is the safest way to completly remove all traces of my Nvidia drivers and then install the official one from the Asus website. > Hi John, > first I am going to go back to my previous driver version but use the one [quoted text clipped - 129 lines] > > > > John |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.