Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

SSH Problem After Adding Static Translation

Hi There,

I have a server which needs to SSH to my PIX FW, this server used to SSH successfully until I added static translation to it in my config. The related PIX config is:

name 172.16.2.33 SecurityServer2

static (inside,outside) 212.93.195.26 SecurityServer2 netmask 255.255.255.255 0 0

ssh SecurityServer2 255.255.255.255 inside

I'm getting the following error message:

TCP connection limit exceeded from 172.16.2.33/3906 to inside:172.16.1.29/ssh

I looked into the meaning of this message and I'm not seeing any active SSH connections to kill!

Please remeber that server used to SSH with no problems before adding the above static rule? Any input would be highly appreciated.

Thanks,

Haitham

1 REPLY

Re: SSH Problem After Adding Static Translation

Hi Haitam

It may sounds weird, but I've seen where using 'name' command doesn't really help, which I end-up removing the IP-Name (name 172.16.2.33 SecurityServer2), and it works. Not sure if it works for you.

Before that, try to allow telnet/http (for https) for testing, and see if it works.

Rgds,

AK

86
Views
0
Helpful
1
Replies
CreatePlease to create content