[lug] OpenSSH upgrade small issue

[Justin]

I upgraded all my boxes today to OpenSSH 2.5.1p1 and I'm having a minor 
problem. One machine for some reason will not connect to other machines 
using protocol 2 unless I force it with the -2 flag. All of my machines 
config files are the same and in /etc/ssh/ssh_config I have it try 
protocol 2 first then 1. The only thing I've noticed is that the box 
having the problem, does not appear to read the /etc/ssh/ssh_config 
file before making a connection:
------------------
[glowecon at naz glowecon]$ ssh -v jackmoves.com
OpenSSH_2.5.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090600f
debug: Rhosts Authentication disabled, originating port will not be 
trusted.
debug: ssh_connect: getuid 500 geteuid 500 anon 1
debug: Connecting to jackmoves.com [63.228.67.67] port 22.
debug: Connection established.
...
...  snipped key file listings
...
debug: Remote protocol version 1.99, remote software version 
OpenSSH_2.5.1p1
debug: match: OpenSSH_2.5.1p1 pat ^OpenSSH
debug: Local version string SSH-1.5-OpenSSH_2.5.1p1
----------------------------
You can see above that it just uses the ssh protocol 1 by default. My 
other boxes appear to read the /etc/ssh/ssh_config file before making 
their connection:
----------------------------
[glowecon at oldschool glowecon]$ ssh -v naz.jackmoves.com
OpenSSH_2.5.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090581f
debug: Reading configuration data /etc/ssh/ssh_config
debug: Applying options for *
debug: Rhosts Authentication disabled, originating port will not be 
trusted.
debug: ssh_connect: getuid 500 geteuid 500 anon 1
debug: Connecting to naz [63.228.67.66] port 22.
debug: Connection established.
...
...  snipped key file listings
...
debug: Remote protocol version 1.99, remote software version 
OpenSSH_2.5.1p1
debug: match: OpenSSH_2.5.1p1 pat ^OpenSSH
Enabling compatibility mode for protocol 2.0
debug: Local version string SSH-2.0-OpenSSH_2.5.1p1
-------------------------

The boxes are almost identical in configuration. I haven't been able to 
figure out why the 'naz' host won't automatically try protocol 2. 
Anyone have any ideas? TIA.

Justin
-----
glow at jackmoves.com
www.jackmoves.com