Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Any one have any idea why a remote command to a NetApp filer would fail when using Plink/Putty (to execute a command) across 2 networks?

Everything is open both ways (multiple firewalls), but the filer seems to be responding from port 22 to some random port. So my Windows box on the other side doesn't know to answer because the target port isn't 22.

Any thoughts?

share|improve this question

The issue turned out to be a NetApp ONTAP bug.

Not sure what the workaround was, but another engineer remedied the issue.

Will see if I can post the root cause.

share|improve this answer


What do you seen when from the windows box you open a CMD window and use "telnet" to connect to port 22:

# telnet 22 Trying Connected to Escape character is '^]'. SSH-2.0-OpenSSH_4.3

You should see the "SSH-n.n" banner (might be different version string from the filer than my example above).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.