Terminal Server Client unable to save profile

[FSLLL]

I can successfully connect to a remote Windows Computer using Terminal Server Client but I cannot save the profile (Fedora 12).

This means I have to enter the details every time I wish to connect.

As I have many different remote locations I need to access on a regular basis is there any way to save the profiles?

[marcrblevins]

You meant tsclient?

Did you click on Add Connection? It should save it for your.

I was looking for it in my KDE, so I typed 'client' and it found KRDC. That look promising to use.

Take a look at both and see which is easier to use.

I did a 'yum search krdc', that package is:

kdenetwork.i686 : K Desktop Environment - Network Applications

[FSLLL]

Thanks. The KDE one is fine it saves the profile. For some reason the one on Fedora 12 Gnome doesn't.

[marcrblevins]

So you really like the KRDC now?

I'll get it a shot whenever it have Windows Pro quality version here. I have Windows Vista Home on the laptop, remote in not allow.

[FSLLL]

I use it over an OpenVPN connection to connect to clients machines.

The one that came on the Fedora12 DVD has a box to tick on add connection tab to add to favourites but there does not seem to be anywhere to access favourites. There is an option export the connection you get a file save window with the directory greyed out and clicking save has no effect.

May be I'm missing something.

I like the fact that the KDE version is the same for Terminal Server and VNC plus others. The Gnome one is two separate applications tsclient and Tiger VNC. You can also have multiple connections, each of which shows on a separate tab, and easily move between them.

[timmspinn]

So was there any fix to get the Gnome tsclient to save favorites, aside from running KDE?? I have the same problem. When I'm creating a connection, I chose "Add to Favorites" but as soon as I close it, it loses all my connections I just made! Quite annoying.

[salder]

Check your $HOME/.xsession-errors file for errors. It couldn't find my $HOME because I was logging in via Likewise-based AD account and the domain name was all caps.