Could you please (as a test) try the connection with GSSAPIAuthentication disabled anyway? This would help to distinguish the issues you were experiencing from those described in bug #84899. The easiest way to do this:
This will disable the GSSAPI setting only for this connection, and additionally log every single step taken by SSH to a file called »ssh-nogssapi-nomdns.log« in your current directory. Please attach this log file to your next comment.
Could you please (as a test) try the connection with GSSAPIAuthentic ation disabled anyway? This would help to distinguish the issues you were experiencing from those described in bug #84899. The easiest way to do this:
ssh -vvv -oGSSAPIAuthent ication= no sage@192.168.1.2 >>ssh-nogssapi- nomdns. log 2>&1
This will disable the GSSAPI setting only for this connection, and additionally log every single step taken by SSH to a file called »ssh-nogssapi- nomdns. log« in your current directory. Please attach this log file to your next comment.