Erik Bixby wrote:

>Advice from a networking guy: fire up ethereal, and look at what's
>going out over the network.  :)
>  
>
Well, here's the status, and I will report the final outcome of this, 
when that occurs...

While googling for "slow ssh login" I found some references to adding 
the machine names and IPs to the hosts files.  What the heck, it is 
behaving like some kind of reverse dns lookup oddity.

Adding machine names and ip addresses to the hosts file solves the 
problem.  Now, that works for today (fortunately we're a pretty small 
shop, only 15 machines to add), but it doesn't answer "What changed?"

Our "other" network machines are served by a Windows domain controller 
server that provides WINS and DNS.  The Linux boxes are pointed at that 
machine for their DNS needs.  Until this morning, that was apparently 
all they needed.   It probably goes without saying that there is nothing 
in the Windows machine's logs to indicate there are any problems, 
nothing was changed on this machine, and even rebooting the thing 
doesn't put things back to the way they were.

So for now everything is back to normal speed, and I'm going to lunch.  
I'll sort out later why our Linux boxes just NOW decided that a Windows 
DNS server isn't good enough for them.  ;-)

Thanks to everyone for your suggestions.  You all steered me in the 
right direction, and that's what I needed.  More when the answer is 
found, or when new info appears.

Bill

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change  you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss