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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SAT connection to 5022

Status
Not open for further replies.

werdcrime

Technical User
Mar 30, 2004
21
US
Hi-

We have been switching over everything we can to SSH and SFTP lately. I have one CM 2.2.2 S8700 that refuses all connections to port 5022.

I can access these media servers by the standard SSH port (22) using putty and it will connect without an issue. However ASA forces you to connect on the secure-sat port of 5022 which refuses all connections.

Initially this was also happening on another CM 2.2 S8700 but I was able to resolve this by allowing secure-sat in the firewall rules on that server. This has also been done on the one that is still rejecting this port.

I'm looking for any other ideas of where this could be getting blocked. I've contacted our security and networking groups and they are not blocking this traffic.
 
are you trying to say you cannot ASA thru port 5022?

look in your "display ip-service" form and see what port was opened for ASA
 
That is correct, I'm trying to get ASA to connect to this media server using SSH on port 5022.

Unless I'm mistaken nothing should need to be in ip-services since I'm connecting directly to the virtual IP of the media servers. At least this is not necessary on any of our other S87xx machines.

I went ahead and added it in any case and I am still unable to connect.

Thanks!
 
Check the firewall settings on the server and verify secure-sat is enabled.

IP-Services do not apply when you are connecting directly to the server.

James Middleton
ACSCI/ACSCD/MCSE
Xeta Technologies
jim.middleton@xeta.com
 
I verified that it is indeed enabled in the firewall settings (secure-sat 5022).
 
FYI-

After contacting Avaya they found that port 5022 was not defined in the sshd_config file. Once it was added in and the daemon was restarted it works just fine.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top