Uma i-Ncat isivele itholakala ku-Windows OpenSSH, inganikeza ukuxhumana nge-SOCKS5 proxy. Engeza okufakiwe kwe-host kukho ukulungiselelwa kwe-SSH okusetshenziswa yilelo klayenti le-OpenSSH:

Host target-via-socks
    HostName ssh.example
    User user
    ProxyCommand ncat.exe --proxy-type socks5 --proxy proxy.example:1080 %h %p

Shintsha womabili amagama e-host kanye ne-akhawunti, bese uxhuma nge-ssh target-via-socks. Lesi sibonelo sicabanga ukuthi i-ncat.exe isendleleni yokusesha yamafayela asebenzisekayo omsizi. Uma kungenjalo sebenzisa indlela egcwele yefayela elisebenzisekayo ecashunwe ngendlela efanele, ikakhulukazi uma ifolda inezikhala.

Iphoyinti lokugcina le-proxy iza ngemva kwe--proxy. I-OpenSSH inweba i-%h ne-%p ibe igama le-host le-SSH lokugcina kanye ne-port. I-Ncat ixoxisana ngokuxhumana kwe-SOCKS futhi ithwala umfudlana wamabhayithi ovelayo kwi-input ne-output ejwayelekile; i-OpenSSH iqhubeka nokuxhawana kwe-SSH phezu kwalowo mfudlana.

I--proxy-type socks5 ecacile ibalulekile. Uma lokho kukhetho kungekho, i-Ncat isebenzisa i-HTTP proxy ngokuzenzakalelayo, ngisho noma i-port enikeziwe ingu-1080. Isilaleli se-SOCKS asikwazi ukucabanga ukuthi isicelo se-HTTP CONNECT sasihloselwe i-SOCKS.

Lesi sibonelo sicabanga iphoyinti lokugcina le-SOCKS elingenakuqinisekiswa; khetha umgadli kusukela ohweni lwama-proxy e-SOCKS5 kuphela endaweni yokufika yomphakathi ye-SSH lapho leyo ndlela ivunyelwe khona, futhi uhlole ukufinyelela ku-host ne-port yayo yangempela. Ukuqinisekiswa kwe-proxy, uma kudingekile, kwehlukile ekungeneni kwe-SSH kamuva. Gcina ukuqinisekiswa kokhiye we-host wendawo yokufika ye-SSH; ukufinyelela kuyo ngomsizi akulushintshi ubunikazi i-OpenSSH okufanele ibuqinisekise.

Izihloko ezihlobene