Rdesktop Internal Licensing Error

If you get the following error message when running rdesktop to connect to a Remote Desktop to a Windows server

Autoselected keyboard map en-us
disconnect: Internal licensing error.

Then try running

rm ~/.rdesktop/licence* && rdesktop <windows server name>

There is a license file that gets created when using rdesktop. At some point Microsoft changed their remote desktop authentication, so you need to remove the license file each time before starting rdesktop.


The new version of PuTTY has a new authentication GSSAPI feature. This allows users to log in with out a password but will not mount a users home directory. We have had several users using the new version of PuTTY who could not log in to kerbNFSv4 system.

To overcome this problem you must disable GSSAPI authentication.

To do this in PuTTY go to
Connection –> SSH –> Auth –> uncheck “Attempt Kerberos 5 GSSAPI/SSPI auth (SSH-2)”
Connection –> SSH –> Auth –> GSSAPI –> uncheck “Allow GSSAPI Authentication (SSH-2 only)”

See the following images.



ECpE Red Hat Linux Setup Options

Option A. IASTATE Domain System (Standard Lab Build)

The system would be in the IASTATE domain and would be configured similar to a lab system. We would grant you sudo privileges to install software and also give you full read-write access to certain directories you need.

* IASTATE Domain Authentication
* You cannot get root access
* You can get limited sudo privileges
* Full read and write access to /local, /usr/local, and /tmp
* Full support

Sudo commands that can be granted

Networking: /sbin/route, /sbin/ifconfig, /bin/ping, /sbin/dhclient, /usr/bin/net, /sbin/iptables, /usr/bin/rfcomm, /usr/bin/wvdial, /sbin/iwconfig, /sbin/mii-tool Installation and management of software: /bin/rpm, /usr/bin/up2date, /usr/bin/yum Services: /sbin/service, /sbin/chkconfig Updating the locate database: /usr/sbin/updatedb Storage: /sbin/fdisk, /sbin/sfdisk, /sbin/parted, /sbin/partprobe, /bin/mount, /bin/umount Processes: /bin/nice, /bin/kill, /usr/bin/kill, /usr/bin/killall Drivers: /sbin/modprobe

Others on a individual bases

Option B. Stand Alone System (Outside of IASTATE Domain)

This would be a standalone box. We give you the root password. With this option you are more responsible for maintaining and setting up things. If you break anything you will be responsible for fixing it unless it requires a rebuild. We will help to a certain extent with setting up some software, email, and auto mounting; but will not be able to help as in option A.

* You get root access
* Limited access to commercial software
* We cannot guaranty the integrity of the system