Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya Site Administration 6.x: Communications Error

Status
Not open for further replies.
Nov 27, 2012
167
US
Can anyone think of a reason that ASA site administration won't connect to my CM, but putty will, using the same port parameters? ASA gives error "communication error: network connection failed", but putty works fine.
 
ASA needs to use 5022 for an SSH connection.

Code:
   	   	  secure-sat 	  5022/tcp
   	   	  def-sat 	  5023/tcp
 
Well, that doesn't explain why putty works with the same parameters, over port 5022. Our security guy is telling me that it has something to do with the "ciphers" allowed, I just don't understand why the connection mechanism is different between putty and ASA.
 
The OP did not specify that you were using SSH on 5022 merely that you were able to use the same parameters, so I assumed you were trying to use SAT on 22 hence my suggestion. Are you able to use the Java SAT from the web interface? It will use 5022 as well.
 
Did this just happen or was always that way? If it has always been that way check in the SMI and verify your profile has that capability. There is also a global setting as well.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top