Remote desktop host logs out, locks up

When I try connecting to my remote desktop host, on the client side I get nothing but a black screen (there is a menu with the ip address at the top), and on the host side it logs out, and then stops accepting any input from the mouse and keyboard (the screensaver eventually comes up). I've tried disabling the bitmap caching as was mentioned in some other thread, but that did nothing.

Suggestions?

 

Welcome to the forum luke16.

What is the connection between the computer you are connecting to remotely and the computer you are running the remote desktop client on. That is, are they on the same network or are you connecting from one PC to the other over a WAN on internet connection?

 

Its on the same network, and uses ethernet through a router.

I tried connecting in reverse, with the former client as the host and vice versa, and that actually worked and I was able to control the host, but the inputs to the host still froze for some reason, even after I logged out on the client side.
So this lockup is happening on both my computers for some reason.

 

OK - two likely problems:

• Firewall not set up correctly - that is not configured to allow full communication of remote desktop client with server.
• Network hardware problem. You may have an intermittent hardware fault - one that does not show up with occasional connection such as grabbing e-mails and web pages from the internet, but does show up when you need a continuous connection to be maintained - that is during remote desktop connection

I think the first is most likely, so lets hit that first and return to underlying hardware if the firewall settings are OK.

So, what firewall systems are you using on the two computers?

 

I am using built in windows firewall, with exceptions for remote desktop enabled in both.
As for the networking problem, I have tested that by moving large files between the 2 and doing hash checks afterwards, all came back good.

It looks like I may not have been clear on my last post, the inputs (mouse keyboard, etc) that freeze are located physically at the computer, not over the network. ie, the keyboard and mouse are connect directly to the host. sorry for any confusion.

 

OK - I think I see what you are saying:

If you are sitting at the computer that is being connected too, you'll get the following:

• Everything working as it should. You stop work and a remote connection is initiated.
• The screen goes blank and a notice comes in telling you that computer has been locked and you need to be the person logged on or an Admin to unlock it.
• The remote connection job is completed and the remote person closes their session.
• At this point, you go to log in directly at the computer that was being shared and you find the keyboard and mouse don't work.

OK - What types of keyboard and mice do you have: ps2 or usb?

Do you have a KVM switch on this PC?

Do you get the same problem if you do Ctrl-Alt-Del and lock the computer locally?

 

The screen goes blank and a notice comes in telling you that computer has been locked and you need to be the person logged on or an Admin to unlock it.

Actually, it goes straight to the login screen on the host computer right after a connection is made, and the inputs lock then. There is no notice screen, and you do not have to finish the remote connection on the client computer before the lock happens.

OK - What types of keyboard and mice do you have: ps2 or usb?

usb all around.

Do you have a KVM switch on this PC?

No

Do you get the same problem if you do Ctrl-Alt-Del and lock the computer locally?

If by lock, you mean logging out (windows key + L), then no.

 

Have you tried using a ps2 keyboard?

Usually motherboards do not work natively with a USB keyboard. The system needs to load additional USB drivers before it can communicate with USB devices. It appears that your system is having trouble returning control to your USB human input devices. You may well find that your system finds it easier to work with a ps2 keyboard.

An alternative approach may be to use a different remote desktop application such as VNC.

Other than that, I am not sure what else I can suggest.

 

vnc

Tight vnc appears to be serving my needs right now (in fact I am posting remotely right now ) thanks

As for the usb incompatible MB, I dont believe that to be the case, as I have the bios set up to emulate the usb input devices as if they were regular ps/2 devices (I've used several older bootloaders that were incompatible with usb, and it worked fine with them...) Both of my computers aren't very accessible (one is actually buried under the house believe it or not) and I don't really have any ps/2 devices laying around any more, so testing this isn't really an option.

Anyway, all I need to do now is find a way around my universities firewall, and then I'm set.

 

Glad to have been of some assistance.

You're on your own there. I'd strongly advise that instead of going round the firewall, you discuss your needs with the university network admins and find a supported way to achieve what you want.

 

I believe I just figured out a really[/B] nice way around that: tight vnc can be accessed via a web browser!

You go to any computer, open up a web browser, type in your ip address with the port number (tight vnc uses 5800 by default), and then the web browser downloads a javascript applet, and your in.

All I need to do now is get tight vnc installed on my linux machine.