Connecting to employer's server

Asked by Mitchell Parchem

Hello,
I am running Ubuntu 10.04 and I am trying to connect to my employer's server from home. The employer is running Windows Server 2008. When I was using Ubuntu 9.10, I was able to connect through using Terminal Server Client without any problems. Now that I switched over, the Server screen opens but it keeps telling me 'invalid user name or password' ... I have verified both of those and the ones I am using are correct. Is there some security settings that I am missing in 10.04 ?

Thanks for the help.

Mitch

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu gnome-rdp Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

What client app in Ubutu are you using?

Revision history for this message
Mitchell Parchem (mparchem63) said :
#2

I do not know what that is .... have always just gone through Terminal Server Client

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

ok can you telnet to the port you connect to? The default is 3389 but your admins may use something different.

Revision history for this message
Mitchell Parchem (mparchem63) said :
#4

Hello again,

I spoke with my IT guy at work and he says that they do do 'Telnet' but the default port they use for folks dailing in from home is 443.....is there a way to set Terminal Server Client to use that port insteads of 3389 ?

Revision history for this message
Mitchell Parchem (mparchem63) said :
#5

correction ...... employer does not do Telnet

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#6

Maybe but you can TEST the connection. You can telnet to any port and it will work. If the connection does not work then it's not the app. If it works then we know its the configuration in the application you are using.

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#7

If you want to connect to the Windows Terminal Server at your place of employment, and they use port 443 instead of the standard Terminal Services port (which is 3389), then it sounds like all that is necessary is for you to:

(1) Install a Terminal Services client (this is the same as a Remote Desktop client).
(2) Enter the server's information in the client, making sure to specify port 443.
(3) Click Connect.

There's more than one client program you can use on Ubuntu for this, but here's the most standard way. Install the package "gnome-rdp" (you can do this in Applications > Ubuntu Software Center), then go to Applications > Internet > Gnome-RDP, click New, name the session whatever you want, keep RDP as the protocol (not VNC or SSH), for Computer put the domain name or IP address of the server, followed (without a space) by ":443" (without the quotes), put in your username and password, and put in the domain if applicable.

If you have any problems with these instructions, please post again. If the problem is that you're unable to connect to the server, then following actionparsnip's advice may be useful. The purpose of telnetting in to the server is not to administer it with telnet (hardly anything supports that anymore), but rather to see if the port is open and accessible to you.

Revision history for this message
Mitchell Parchem (mparchem63) said :
#8

The package "gnome-RDP" is already installed on my computer. I did try to specify port 443 in the IP address as indicated but it wouldn't even connect then - at least before when I didn't specify It took me to the log-in screen.

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#9

When you put in the IP address but not port 443, it gives you a graphical Windows login screen?

Revision history for this message
Mitchell Parchem (mparchem63) said :
#10

Yes that is correct ; when I use the additional port numbers, I get an error message saying that it could not connect.

Revision history for this message
Mitchell Parchem (mparchem63) said :
#11

Additional info : I had a coworker log on to employer's server using my ID and PW, they were able to sign on without issue. So, the problem is something with the OS. Is there some new changes between 10.04 and 9.10 with Terminal Server Client.

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#12

You might try a different RDP client, such as xrdp.

Revision history for this message
Mitchell Parchem (mparchem63) said :
#13

I did a search for xrdp in the software center could not find it, i ma going to try downloading Remotedesktop client

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#14

That's strange. The package "xrdp" is present in Lucid (as well as other Ubuntu releases). It is provided by the Universe repository, so perhaps you don't have that enabled. You can enable that by going to Edit > Software Sources in the Ubuntu Software Center (see http://s3.postimage.org/t543xpwf2/xrdp_package.png).

If you have the Universe repository enabled and still cannot find xrdp in the Software Center, then you can try opening a Terminal window (which has nothing to do with Windows *Terminal* Services; rather, as you likely already know, the Terminal in Ubuntu is similar to the Command Prompt in Windows; you can open a Terminal window by going to Applications > Accessories > Terminal or pressing Ctrl+Alt+T) and running the command:

sudo apt-get update; sudo apt-get install xrdp

To run a command, paste it in (or type it in exactly) and press enter. When you run that command, you may be prompted for your password. As you enter it, you won't see any placeholder characters (like *). That's OK -- just type it in and press enter.

That might succeed at installing xrdp. If not, then you can select all the text in the Terminal (Edit > Select All), copy it to the clipboard (Edit > Copy), and paste it here, which should provide some information to help figure out why it's not installing.

Can you help with this problem?

Provide an answer of your own, or ask Mitchell Parchem for more information if necessary.

To post a message you must log in.