HP Proliant DL380 G5 - Remote Desktop

[Roy Andrews]

Yep.

Any other ideas? I've never even heard of this specific error before.

[Mi6t0]

And are you sure that the "allow remote desktop" in system properties is checked?

Also you can check on which port the connection is established - is it possible that someone has changed the remote desktop port?
Regards,

[Colin_29]

Ok I think you need to drop back to some basic diagnostics. I would run Netcat (http://netcat.sourceforge.net/download.php) on the server 'nc.exe -l -p 3389' and try to connect (telnet 3389). This will show if the server is allowing traffic in for RDP. If it is not then you have a comms issue.

Try 'Shields Up' to see your port status.

[chongkan]

What is the resolution of the Server and client machines?

Depending on the computer I'm using I get the same error whenever I click the scrolls on any window on the remote desktop..

I'm able to login, but if I touch the scroll the connection falls and I get that error..

Can you check that and advice?

[Colin_29]

Sorry wrong URL. This one for Windows http://www.vulnwatch.org/netcat/

[Roy Andrews]

Some good ideas to try out there.

I will check the RDP port and test access through netcat.

[Roy Andrews]

Just tried to connect to netcat but it won't connect. So I went to check the port but the...

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\"

...key doesn't contain the "RDP-Tcp" key or its sub-keys.

That's extremely weird. It seems RDP doesn't even know what port it's supposed to be on.

[Roy Andrews]

Sorry for the triple post but please disregard my last comment as the "admin" key contains "PortNumber" 3389.

Any ideas of anything else to check?

[Colin_29]

So are you saying that you can connect (telnet 3389) or not. If not then using nc, can you connect on any other port you publish? What were the results from ShieldsUp?

[Roy Andrews]

Shields up does not really help me as I'm not trying to access remote desktop over the internet but across the local network.

Shields up shows only ports 80 and 143 open to the internet.

Just checked again, I CAN telnet through port 3389.