Send protocol NO-OP is not working

[kamal]

We have this Sun Server, being used as jumpbox. I have enabled port forwarding using one of the article mentioned on vandyke website.

Issue is, anti IDLE mechanism is not effective in my case using NO-OP or even using " /b"(without quotes)

Nothing is appearing while trace option is enabled. What could be the reason?

[rtb]

Hi kamal,

The space and backspace characters are sent so fast that you don't see it happening. The NO-OP is not traced so it doesn't appear when using the normal trace options output.

A client can only do so much to try and convince a server or remote environment not to disconnect it. If you are getting disconnected even though you are using anti-idle options, you will need to investigate the server side of things.

It could be the server or the shell that is disconnecting you. You may also want to discuss this with the server administrator.

[rtb]

Hi kamal,

I do have a couple of questions.

What version of SecureCRT are you using?

What specific method have you used to configured the port forwarding?

[kamal]

Method:

https://www.vandyke.com/support/tips/socksproxy.html

Version 7.2.6 (x64 build 606)

[rtb]

Hi kamal,

Is your master session requesting a shell?

If so, have you enabled anti-idle measures in your master session?

[kamal]

Hey Todd,

Do Not Request Shell did the trick. Many Thanks!

Cheers!