OpenSSH-3.9p1 and MIT Kerberos - openssh

This is a discussion on OpenSSH-3.9p1 and MIT Kerberos - openssh ; Hello all -
I am experimenting with Kerberized-ssh for the first time. I have
configured a test KDC and created a test Realm. I have tried connecting
from the KDC to the KDC using ssh with 'gssapi-with-mic' with no luck. ...

OpenSSH-3.9p1 and MIT Kerberos

Hello all -
I am experimenting with Kerberized-ssh for the first time. I have
configured a test KDC and created a test Realm. I have tried connecting
from the KDC to the KDC using ssh with 'gssapi-with-mic' with no luck. I
am finally stuck as I am not receiving any relevant error
messages. Any help would be appreciated. Below are the details:

# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.

# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.

# This sshd was compiled with
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ssh/bin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options change a
# default value.

# For this to work you will also need host keys
in /usr/local/ssh/etc/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication mechanism.
# Depending on your PAM configuration, this may bypass the setting of
# PasswordAuthentication, PermitEmptyPasswords, and
# "PermitRootLogin without-password". If you just want the PAM account
and
# session checks to run without PAM authentication, then enable this but
set
# ChallengeResponseAuthentication=no
UsePAM no