Unable to Remote Desktop to Corporate Server

[TZRick]

Hello everyone,

I am running Linspire 6.x and having problems running krdc to access the server. Initially, I got a message saying that I needed rdesktop, which I have since downloaded and installed from CNR. I'm using the rdp:/xx.xx.xx.xx format in krdc to specify the connection type.

The error I am getting is "Connection Failure: Connection attempt to host failed".

Any ideas?

[jrusso2]

Could be a number of things. Is the server set up to allow that desktop to connect? Does the user have permissions to connect remotely. Are you using a Netbios name to connect or the servers IP address? Are you using a firewall? Is the port blocked?

[TZRick]

This is a corporate terminal server, so it is accessible over the internet. I connect to it properly from all of my windows machines, whether my home laptop, my work laptop or any other Windows machine for that matter.

I am not even allowed to enter credentials, so I'm guessing privilieges should not have anything to do with it?

I am using the ip address of the server, as I always do when I am not at the office. From a hardware perspective, I am not using anything that is blocking remote desktop because my home laptop and work laptop can both connect through my network (Cable modem + router + wireless switch). On the software side, when I open FireStarter and go to the Policy tab, for Outbound Traffic Policy, the setting is Permissive by default, blacklist traffic.

[bobd13045]

Originally Posted by TZRick

This is a corporate terminal server, so it is accessible over the internet. I connect to it properly from all of my windows machines, whether my home laptop, my work laptop or any other Windows machine for that matter.

I am not even allowed to enter credentials, so I'm guessing privilieges should not have anything to do with it?

I am using the ip address of the server, as I always do when I am not at the office. From a hardware perspective, I am not using anything that is blocking remote desktop because my home laptop and work laptop can both connect through my network (Cable modem + router + wireless switch). On the software side, when I open FireStarter and go to the Policy tab, for Outbound Traffic Policy, the setting is Permissive by default, blacklist traffic.

Rick

You said it work's in Windows. Worst case you can set your PC up for Dual Boot
(Windows and Linux).

I can read my company mail while in Linux, but to connect to the company intranet I have to be in Windows. So dual boot has been very handy for me.

Hopefully one of our other members can help you with your Linspire remote desktop
problem.

Bob

[subslug]

I would certainly open the firewall in Linspire's control center under the networking area.
I doubt it will connect otherwise.

Another thing it could be, normally in krdc you need to input the ip address and the screen you want to log into.....sort of like "xxx.xxx.xxx.xxx:0"

This might help you too.

[DrHu]

You also don't say which windows host type
XP, 2000 or Vista ?
http://www.hostingtech.com/?m=show&id=870

rdesktop is an open source client for Windows NT Terminal Server and Windows 2000/2003 Terminal Services, capable of natively speaking Remote Desktop Protocol (RDP) in order to present the user's NT desktop. Unlike Citrix ICA , no server extensions are required.

--you might want to do it in a terminal (konsole) to see if there are any replies (messages) coming back

rdesktop -u yourname 192.168.1.10 & <enter>
Using the -u option instructs rdesktop to send the username specified to the given server. Ok, now lets say you have the need to connect to a terminal server which only supports RDP Version 4, simple, just enter the following command:

rdesktop -4 192.168.1.10 & <enter>
rdesktop connects using RDP Version 4 just as you specified. rdesktop has many other options you can explore on your own, you can read about them via the man pages, or to see a quick list just enter the following command:

rdesktop..
http://episteme.arstechnica.com/eve/...m/195009042931
http://aseigo.blogspot.com/2008/02/k...ver-again.html
https://secure-support.novell.com/Ka...tml#disclaimer

[Elbato]

http://www.nongnu.org/grdesktop/shots.html

[TZRick]

BobD,

Thanks for the input. I'm not planning to dual-boot anytime soon. I've sent a dollar too many Microsoft's way.

[TZRick]

SubSlug,

I have tried stopping FireStarter with and I got the same error. I also looked into the man pages you sent and they were helpful, but I could not find a solution.

[mr.gigabytes]

If you are connecting over the internet you need to type in the port number as well. Locally, you can get by with only the IP address.

Ex. Via Internet rdp://10.0.0.222:3389
Locally rdp://10.0.0.222

rdesktop is available in CNR and it must be installed before you can connect. 3389 is the default port for Remote desktop in windows.

[TZRick]

Dr. Hu,

The server is a Windows 2003 Server, most likely fully-patched. I looked into the links you sent for rdesktop and running from the command line. They all say Connection Timed Out.

Concerning tsclient, it is not available on the CNR website. I already use krdc, so that option is out.

The other links you posted were also helpful, but did not lead me to a solution.

Any other ideas? I think what I've seen here is that it is definitely some sort of networking issue...but what? I disabled FireStarter and it still didn't work. Is there another phantom firewall that I am not aware of?

Thanks again for your input and I look forward to more.

[TZRick]

mr.gigabytes,

Even specifying the port doesn't work. Thanks though.

[mr.gigabytes]

If you have the Linspire firewall set to closed it may not work.

I have a thought, if you PM me the IP address of the server you are trying to connect to, I can see if I am able to connect to it. I won't login of course, but to at least see if ithe server is receptive to the connection. I am able to login to my server at the office as well as my freespire box using krdc. If I am able to connect, we can troubleshoot your box.

[DrHu]

ping the ip address you are trying to connect to, any response (although they may have disabled icmp at the server end..)
Try a browser connection to that host IP address, any responses (even an error )

Microsoft list of errors..
http://technet2.microsoft.com/window...33.mspx#BKMK_2

The remote connection has timed out. Please try connecting to the remote computer again.
Cause: The terminal server disconnected your session because you did not send a response within the time limit set for responses.
Solution: Try connecting to the terminal server again. If you receive this error message, try to reconnect at a later time. If you continue to receive this error message, contact the server administrator.
Cause: A slow network connection, caused by excessive network traffic, has delayed your response to the terminal server.
Solution: Try connecting to the terminal server again. If you receive this error message, try to reconnect at a later time. If you continue to receive this error message, contact the server administrator.

Check if you are listening on the default port for windows rdp connections
--in a terminal window (konsole)
netstat -a
--see if port 3389 is there

Final thought

• You are allowed to connect remotely if you used a windows OS, yes or no
• The ts license count includes you or you know that they (server admins) have enough tsc licenses to handle xxx number of remote connections, and they have some spares!

firestarter should not be running, or you will have to setup a policy for port 3389
--in a terminal window (konsole)
sudo firestarter stop
edit correction
sudo firestater -p (or --stop)
--or just start firestarter and then stop it with th gui that appears on the system tray (kse, right-side of desktop)

Additionally, if you also connect with a router, then its firewall (NAT) will have to allow that port as well
--some people won't call a NAT a firewall (nitpicking, we are being more generic ), but it is the basis of a firewall, as it hides the internal network IP addresses.

[jrusso2]

Originally Posted by TZRick

mr.gigabytes,

Even specifying the port doesn't work. Thanks though.

Are you sure that your not using a VNC client of some sort to get past your work Firewall?

It would seem strange to run a server unprotected with RDP running and no credentials.

[TZRick]

Okay. I found the problem and it was between the chair and the screen. I had the third and fourth parts of the IP address swapped. Everything works fine now. Thanks for all of your help. I am sure that other users experiencing these issues will now have a lot of information to assist.

[bobd13045]

Originally Posted by TZRick

Okay. I found the problem and it was between the chair and the screen. I had the third and fourth parts of the IP address swapped. Everything works fine now. Thanks for all of your help. I am sure that other users experiencing these issues will now have a lot of information to assist.

I have been there. Sometimes the solution is right in front of me and I can't see it
Glad your remote desktop is working now.

Bob