HP Proliant DL380 G5 - Remote Desktop

Whenever I try to access remote desktop on the server, I get:

---------------------------
This computer can't connect to the remote computer.

The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support.
---------------------------

I have enabled remote desktop in the system properties.

Can anyone suggest something?

27 REPLIES 27

hi

can you ping the server ip?
this is the first time you have this issue?

-------
also what is the Proliant support pack are you using?

regards

Didn't your momma teach you to say thanks!

Yes, the server is working perfectly other than no remote desktop. Pinging, and even network sharing works fine.

Only remote desktop has an issue. Google only finds 5 results for the error message and most of those are foreign languages.

Proliant DL380 G5 running Windows Storage Server 2003 R2.

What do you mean by "support pack"? I think we have phone service and 4 year warranty. Not sure about callout service.

hi

I meant Proliant Support Pack (package that includes drivers) but I can see your server is working fine I mean networking

are you sure about google?

http://www.google.com/search?q=This+computer+can't+connect+to+the+remote+computer&sourceid=navclient-ff&ie=UTF-8&rlz=1B3GGGL_enCR228CR228

regards

Didn't your momma teach you to say thanks!

hi

http://www.windowsnetworking.com/articles_tutorials/Using-Remote-Desktop-Windows-XP-Pro.html

regards

Didn't your momma teach you to say thanks!

I know how to use remote desktop. I use it every day at work. Its just this server that's giving me a headache with its stupidity.

When I said google had limited results that's with the actual error. Your search was the generic part of the error. If you look at the results of your search, they are not related to my problem.

If you search "due to a network error" you get 5 results.

Might try updating to Terminal Services 6.

hi

sorry I did not mean that did not know how to create RDP connection I just added some information that I was thinking could help

so check this link
http://support.microsoft.com/kb/936594

it says something about this
"You cannot create a Remote Desktop Protocol (RDP) connection to the server."

I hope this can help you

regards

Didn't your momma teach you to say thanks!

hi again this another article mentions RSS and TOE take a look

http://msexchangeteam.com/archive/2007/07/18/446400.aspx

regards

Didn't your momma teach you to say thanks!

Sorry for getting you wrong.

Thanks for those links. I tried them but still doesn't work.

Tried messing with disable/enable RSS and chimney. No dice.

When I rang HP, I got someone out of the country who had no idea.

Maybe its time to give up and do a full reinstall of Windows and stuff. I would've expected a brand new server, set up "professionally" by HP to work out of the box.

Have you allowed RDP as an exception in the Windows firewall?

Yep.

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

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,

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.

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?

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

Some good ideas to try out there.

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

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.

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?

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?

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.

I had some similar issues and re-applied the SP and that seemed to fix it. If you can telnet the RDP fine, it's a Windows setup/registry thing.

Ok, so comms are fine. I think it almost definately a Windows issue. I agree, your easiest next step is to reapply the service pack. If that fails you need to balance how long this is taking you against reinstalling the server, because I think you will then be into registry edits and things like that and may never get to the bottom of it.

Please post your results and assign points as appropriate.

I would try disabling the Windows Firewall service just to see if that is blocking the RDP request.

Neal, If you look back through the thread you will see that we have established that the server can listen on 3389. The problem is almost certainly a Windows issue and definately not comms.

Colin,

I did see the threads indicating that comms was not an issue. I have seen issues where the Firewall service was started, giving these scenarios. My suggestion was to temporarily disable the firewall service, if it is in fact started.

Otherwise, you would be correct in that is would be a Windows issue.

Neal