02-15-2005, 08:54 AM | #1 (permalink) |
Insane
Location: Michigan
|
Windows: Remote Desktop Login = Immediate Log Out
I just put togther my new pc and tried using remote desktop to get into it from work and as soon as it says "loading personal settings" it changes to "logging out". I have turned on remote desktop via system properties. It does this for my user account and the administrator account. To make things weirder, if I log in at the console (physically or via VNC), I can then remote desktop in and take over the session.
Any ideas on what is going on?
__________________
Patterns have a habit of repeating themselves. |
02-15-2005, 10:24 AM | #2 (permalink) |
Insane
Location: Michigan
|
Nevermind, turns out it was a nVidia driver issue. I went to get the latest drivers and I got a 404 so I downloaded the version of drivers right before that, with the intention of "it will work for now, Ill wait for the vendor to fix their site, then Ill get the newest drivers". Apparently, after the release of those drivers, MS released a patched that screwed up nVidia w/Remote Desktop. I found the newer drivers today and all is good.
Thanks to any of those who read my post.
__________________
Patterns have a habit of repeating themselves. |
02-17-2005, 03:50 PM | #4 (permalink) |
Crazy
|
On the topic of VNC's.... I havent used microsoft's remote desktop function. How does it compare to say TightVNC (what i use). I like tightVNC because you can connect to it through HTTP and it uses a java applet to control it. I like this because I can use it on any computer with a web browser.
|
02-18-2005, 03:42 AM | #5 (permalink) |
Junkie
Location: NorthEast
|
TightVNC is actually running on the console of the system, so you see what is there. While Remote Desktop virtualizes it, so if you log in via that and someone looks at your actual computer they see the login screen without any of the things you are doing. Not sure how well messages are routed that are are supposed to come up on the console with Remote Desktop, on Windows Terminal services, you can often not see a message that was sent to the console if you are logged in via terminal services.
TightVNC is probably "snappiest" of the vnc versions I have used. But Remote Desktop IS quicker, and also forwards sound. Tightvnc does NOT forward sound. |
02-18-2005, 09:00 AM | #6 (permalink) |
Insane
Location: Michigan
|
Remote Desktop / Terminal Services is the way to go. VNC works, but just isnt quite as fast. However, one thing that UltraVNC has that pisses me off is file transfer. I would LOVE that feature in Remote Desktop / Terminal Services.
You can also run a "Web" version of RD/TrmSrv, but it requires IE as it is ActiveX based.
__________________
Patterns have a habit of repeating themselves. |
Tags |
desktop, log, login, remote, windows |
|
|