Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Andy Burns <usenet@andyburns.uk>
Newsgroups: alt.comp.os.windows-10,microsoft.public.windowsxp.general,comp.mobile.android
Subject: Re: What's the best way to forward SMB TCP port 445 to something higher than 1024 on Windows?
Date: Wed, 17 Oct 2018 01:06:20 +0100
Lines: 13
Message-ID: <g2ncnvFu63tU1@mid.individual.net>
References: <ppvu3u$pi3$1@news.mixmin.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net rv2ydnJ11V/zmgcu6bzFogvxyO+kTkf8srHaUNBKPJ17kyQ/5K
Cancel-Lock: sha1:QyfvMqG8Ikjw/XvxaQHoq0GvOS0=
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
In-Reply-To: <ppvu3u$pi3$1@news.mixmin.net>
Content-Language: en-GB
Xref: csiph.com alt.comp.os.windows-10:76683 microsoft.public.windowsxp.general:150401 comp.mobile.android:56709

Arlen Holder wrote:

> Do you have experience port forwarding SMB ports on Windows?

Yes, when I needed to map a drive over an SSH tunnel.

netsh interface portproxy add v4tov4 listenport=xxx 
listenaddress=192.168.xx.xx connectaddress=192.168.yy.yy connectport=yyy

Because the lanmanserver service starts early and binds to 445 on all 
interfaces, you may need to install a virtual kernel NIC driver in order 
to get an interface with a "spare" IP address to listen on, it was 
available from MS last time I needed it on Win7, not sure about Win10.