Also see the NCSA Kerberos
Windows and
UNIX
Troubleshooting Guides.
General Questions
The password to use is your NCSA AFS/Kerberos password.
For HPC users, this is the same as your NCSA UniTree (mass storage) password.
For NCSA staff, this is the same as the password you use for checking email
or logging into NCSA's public systems (pecos and
osage).
Note that you will also use this password to connect to NCSA's internal
server to download the software.
Currently, the only way to access UniTree is using the kerberized ftp client.
Questions about Kerberos
When you issue a kinit, you would specify your NCSA login as follows:
kinit NCSAlogin
Then, with
telnet or
rlogin, you need to use the
-l option. For example:
telnet -l NCSAlogin modi4.ncsa.uiuc.edu
There are a couple of reasons this is happening. First verify that you
are using the kerberized telnet client, and not the generic one. If
you still get this error with the kerberized version, check that your
krb5.conf file has the following in the section [appdefaults]:
telnet = {
autologin = 1
}
Alternatively, you can use the
-a option to telnet.
This means that kinit cannot find the necessary configuration on the realm
you are requesting.
Where is your krb5.conf located? The NCSA generated binaries
look for both /etc/krb5.conf and
/usr/local/krb5/etc/krb5.conf. If you
have placed the krb5.conf file elsewhere, you need to use the
environment variable KRB5_CONFIG to specify this.
Check the instructions on the
download page on how to do this.
Another possibility is that you are indvertently requesting a bad
realm in some way. If you authenticate to multiple realms, you will be
specifying the realm when you kinit. Realm names are case sensitive, so
you need to make sure to enter
kinit NCSAlogin@NCSA.EDU
A third possibility is that you are trying to connect from behind a firewall.
Please see the firewall information, or check with
your local system administrator.
kinit: Can't open/find configuration file (dce / krb) when parsing name
jdoe
kinit: Principal unknown (kerberos).
Some Unix platforms - Solaris is one, have a vendor version of kerberos
installed with the kerberized utilities located in /usr/bin.
You can change the order of your path so the version of kinit that is used
is the one you installed.
Check the instructions on the
download
page to set your path correctly.
Client not found in Kerberos database while logging in
The error means that you have not entered a valid Kerberos username. Please
check that you have correctly entered your NCSA login.
Questions about SSH
SSH2 clients are not supported at NCSA, so you need to use SSH1 clients.
Use the -l option to ssh. For example:
ssh -l NCSAlogin modi4.ncsa.uiuc.edu
You will need to use a kerberized ftp client;
scp cannot be used when an account is in restricted mode.
The first time you use SSH to connect to a host you will
get a message that says:
host key not found from the list of known hosts
do you still want to continue the connection[yes/no]?
Answer yes (y-e-s) to this and you will then be connected. You will see
this message when you connect to a host for the
first time only.
ssh will add the host to its list.
/usr/bin/X11/xauth: error in locking authority file
when logging in with ssh usually indicates that you are over your quota
in your home directory. You can check this with the command
quota -v. You will need to remove files to get below the quota.
This error occurs when a command is trying to write to stdout or stderr (for
example, an "echo" command or an undefined variable in your .cshrc file).
Another reason for the error is
when your account on an NCSA system is terminated and goes into restricted mode
(see section on
Account Termination),
you will not be able to use scp to copy files from that system
to your home machine.
If you try, you may see messages like the following:
Write failed flushing stdout buffer.
write stdout: Broken pipe
While your account is in restricted mode, you will need to use
a kerberized ftp client to access your files.
If you still have an active account, and you are seeing this error,
please contact the NCSA Consulting Office for assistance.