Solaris

Then you might try adding the server on a client's /etc/hosts and use a hostname instead of an IP to see if that makes a difference.

Is connecting from the server to the server exhibiting the same issue ?

Code:

ssh 127.0.0.1

Yes, it looks like a delay caused by network function so could be a number of things.

Your Solaris box doesn't use DNS but other network security devices or other nodes might. Some network security devices may be trying to do a reverse DNS lookup to validate the initiator of the connection so you should get your network support to check that entries for the client and server are in there.

Also, take a look in /etc/defaultrouter and see that ip address. Is it still valid? When a inbound connection request comes in Solaris needs to instantly know the route back. I've known network support boys to retire a router and not tell everybody so Solaris then tries to use an incorrect default router. Check with the network team that your configured default router is still alive and kicking. Try pinging it and see if it instantly responds.

Have you tried doing the same connection from a different client? Do you get the same result? What about a different client in a different location?

Can you ping your client from the server? (Of course, not all nodes may be configured to reply to pings but if it does work then it tells you something.)

If I get any more thoughts then I'll post them. Good hunting.

PS. How many NIC's in the box? Can we all assume just the one?

Yes, server to same server is doing the same thing as a remote connection. Also, when I try and connect to 127.0.0.1 it still shows the same symptoms. When I try and connect to a web page or anything on the server it works instantly it only seems to be SSH that I'm having issues with...

@hicks I will also try some of the stuff you are talking about to see if I notice anything.

It's definitely no IP routing problem then!
Does

Code:

grep '^[^#]' /etc/net/*/hosts

yield 3 times the local hostname that matches in /etc/hosts,
and does its IP address match a working interface in

Code:

ifconfig -a

?

Connection to 127.0.0.1 should be instant. It can be slow if reverse lookup doesn't work. Please confirm

Code:

 
127.0.0.1   localhost

appears in /etc/hosts.

Also, from the server try connecting using the server's real ip address (rather than 127.0.0.1). Is that slow too?

@kindbag Anything interesting in the system log file ?

Code:

dmesg | grep sshd