none
problem with adding a portproxy using netsh RRS feed

  • Question

  • Hi,

    I'm pretty inexperienced when it comes to network administration but need to learn more about it for a upcoming project, I'm currently just trying to get my head around how to use the netsh command to redirect tcp traffic that goes through my server, to start with something simple I created a amazon ami with a clean install of 2008 Server and installed iis then tried to create a rule that forwarded traffic from port 9000 to port 80 so I could test it was working by accessing a website on http://127.0.0.1:9000/. I entered the command:

     

    netsh interface portproxy add v4tov4 listenaddress=127.0.0.1 listenport=9000 connectaddress=127.0.0.1 connectport=80

     

    And it appeared to work, doing a "netsh interface portproxy show all" gave me:

     

     

    Address         Port        Address         Port

    --------------- ----------  --------------- ----------

    127.0.0.1       9000        127.0.0.1       80

     

     

    But when I try to access http://127.0.0.1:9000/ I get "Internet Explorer cannot display the webpage", without the port the default IIS page is displayed fine

     

    I'm sure I'm missing something pretty simple but couldnt find anything on google to find out what so if anyone can help with this it would be really appreciated

    Saturday, March 26, 2011 12:36 AM

Answers

  • Hi,

    Thanks for the post.

    Please be assured that IPv6 protocol has been installed on Windows Server 2008.

    Please understand that Netsh.exe is a tool an administrator can use to configure and monitor Windows-based computers at a command prompt. The Netsh.exe tool direct the context commands you enter to the appropriate helper, and the helper then carries out the command. A helper is a Dynamic Link Library (.dll) file that extends the functionality of the Netsh.exe tool by providing configuration, monitoring, and support for one or more services, utilities, or protocols. The <add v4tov4> command is sent to the IPV6MON.DLL helper, and because of that it will work only if IPv6 protocol is installed.

    Thanks,

    Miles


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, March 28, 2011 9:09 AM
    Moderator

All replies

  • tried it using a the real IP of the adapter, not the loopback address?
    Saturday, March 26, 2011 9:16 PM
  • I hadnt tried that but unfortunately it didnt make any difference :(

    Since posting I tried exactly the same thing on my home pc (windows 7) and it worked perfectly so i think it must be something to do with either a) something that isnt installed in 2008 by default or b) a security setting to allow it

    Sunday, March 27, 2011 2:42 AM
  • firewall?

    when you install the IIS web role, it enables port 80 inbound on the firewall.   may have to do it manually for port 9000

    • Proposed as answer by 李泓德 Tuesday, August 28, 2018 1:54 PM
    Sunday, March 27, 2011 6:27 AM
  • Yeah, I tried adding an exception and just turning the firewall off and neither made any difference :(
    Sunday, March 27, 2011 1:18 PM
  • Hi,

    Thanks for the post.

    Please be assured that IPv6 protocol has been installed on Windows Server 2008.

    Please understand that Netsh.exe is a tool an administrator can use to configure and monitor Windows-based computers at a command prompt. The Netsh.exe tool direct the context commands you enter to the appropriate helper, and the helper then carries out the command. A helper is a Dynamic Link Library (.dll) file that extends the functionality of the Netsh.exe tool by providing configuration, monitoring, and support for one or more services, utilities, or protocols. The <add v4tov4> command is sent to the IPV6MON.DLL helper, and because of that it will work only if IPv6 protocol is installed.

    Thanks,

    Miles


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, March 28, 2011 9:09 AM
    Moderator
  • I have very same issue.

    How can command be sent to IPV6MON.DLL ? There's no such file in Windows 2008 (with IPv6 installed), here's what my output of show helper shows:

    netsh interface portproxy>show helper
    Helper GUID DLL Filename Command
    -------------------------------------- ------------ -------
    {02BC1F81-D927-4EC5-8CBC-8DD65E3E38E8} AUTHFWCFG.DLL advfirewall
    {FB10CBCA-5430-46CE-B732-079B4E23BE24} AUTHFWCFG.DLL consec
    {35342B49-83B4-4FCC-A90D-278533D5BEA2} AUTHFWCFG.DLL firewall
    {4D0FEFCB-8C3E-4CDE-B39B-325933727297} AUTHFWCFG.DLL monitor
    {00770721-44EA-11D5-93BA-00B0D022DD1F} HNETMON.DLL bridge
    {0F7412F0-80FC-11D2-BE57-00C04FC3357A} DHCPMON.DLL dhcp
    {6DC31EC5-3583-4901-9E28-37C28113656A} DHCPCMONITOR.DLL dhcpclient
    {8B3A0D7F-1F30-4402-B753-C4B2C7607C97} FWCFG.DLL firewall
    {44F3288B-DBFF-4B31-A86E-633F50D706B3} NSHHTTP.DLL http
    {0705ECA1-7AAC-11D2-89DC-006008B0E5B9} IFMON.DLL interface
    {1C151866-F35B-4780-8CD2-E1924E9F03E1} NETIOHLP.DLL 6to4
    {725588AC-7A11-4220-A121-C92C915E8B73} NETIOHLP.DLL ipv4
    {500F32FD-7064-476B-8FD6-2171EA46428F} NETIOHLP.DLL ipv6
    {90E1CBE1-01D9-4174-BB4D-EB97F3F6150D} NETIOHLP.DLL 6to4
    {90E1CBE1-01D9-4174-BB4D-EB97F3F6150D} NETIOHLP.DLL isatap
    {1C151866-F35B-4780-8CD2-E1924E9F03E1} NETIOHLP.DLL isatap
    {1C151866-F35B-4780-8CD2-E1924E9F03E1} NETIOHLP.DLL portproxy
    {78197B47-2BEF-49CA-ACEB-D8816371BAA8} NETIOHLP.DLL tcp
    {1C151866-F35B-4780-8CD2-E1924E9F03E1} NETIOHLP.DLL teredo
    {F7E0BC27-BA6E-4145-A123-012F1922F3F1} NSHIPSEC.DLL ipsec
    {F7E0BC29-BA6E-4145-A123-012F1922F3F1} NSHIPSEC.DLL dynamic
    {F7E0BC28-BA6E-4145-A123-012F1922F3F1} NSHIPSEC.DLL static
    {1D8240C7-48B9-47CC-9E40-4F7A0A390E71} DOT3CFG.DLL lan
    {00B399EA-447F-4B19-8393-F9D71D7760F9} NAPMONTR.DLL nap
    {3F8A1180-FF5D-4B5B-934C-D08DFFBC9CBC} NAPMONTR.DLL client
    {B123BAAA-79E9-49FD-AB2C-E87C56CE4CFF} NAPMONTR.DLL hra
    {931852E2-597D-40B9-B927-55FFC81A6104} NETIOHLP.DLL netio
    {0705ECA2-7AAC-11D2-89DC-006008B0E5B9} RASMONTR.DLL ras
    {42E3CC21-098C-11D3-8C4D-00104BCA495B} RASMONTR.DLL aaaa
    {90FE6CFC-B6A2-463B-AA12-25E615EC3C66} RASMONTR.DLL diagnostics
    {13D12A78-D0FB-11D2-9B76-00104BCA495B} RASMONTR.DLL ip
    {36B3EF76-94C1-460F-BD6F-DF0178D90EAC} RASMONTR.DLL ipv6
    {592852F7-5F6F-470B-9097-C5D33B612975} RPCNSH.DLL rpc
    {C07E293F-9531-4426-8E5C-D7EBBA50F693} RPCNSH.DLL filter
    {0BFDC146-56A3-4311-A7D5-7D9953F8326E} WHHELPER.DLL winhttp
    {BF563723-9065-11D2-BE87-00C04FC3357A} WINSMON.DLL wins
    {B2C0EEF4-CCE5-4F55-934E-ABF60F3DCF56} WSHELPER.DLL winsock

    And I have IPV6 enabled on my LAN connection.

    • Proposed as answer by Igor Be Tuesday, October 30, 2012 2:50 AM
    Tuesday, October 30, 2012 1:51 AM
  • The reason is simple but weird.

    You cannot use 127.0.0.1 as the connectaddress in the netsh command. You probably need a port forwarding tool if you have to to use 127.0.0.1 as connectaddress.

    btw: Although the question is posted 2 years ago, I decide to post this answer because it really confuses my a lot. Wish it can help.

    • Proposed as answer by Roby Thomas Thursday, April 3, 2014 4:52 AM
    Tuesday, August 27, 2013 3:18 AM
  • Joe,

    Did you find a solution to this?, I'm having the same issue on windows 2012 to try to secure MySQL port form automated attacks and I just can't figure out what the problem is:

    netsh interface portproxy add v4tov4 listenaddress=any listenport=30000 connectaddress=82.37.183.201 connectport=3306

    Thanks in advance


    G.Waters

    Friday, January 3, 2014 3:43 PM
  • And it still isn't solved... 

    I'm trying to forward port 80 to 32400 (plex media server)

    I have tried several different commands - and I got it to work, briefly, but then I restarted and now I can't get it to work again...

    netsh interface portproxy add v4tov4 listenport=80 listenaddress=192.168.0.100 connectport=32400 connectaddress=192.168.0.100

    I have tried with locahost, I have tried with 127.0.0.1, and even leaving the listenaddress parameter out altogether, but still without results...

    doing a reset:

    netsh interface portproxy reset all

    was what made it work once...

    reset, then added the portproxy, but alas, no longer...

    As this is still a top hit on google search results, any news would be useful to us all ;)

    Thanks,

    Mark

    Wednesday, January 8, 2014 1:48 AM
  • Mark,

    I don't know if you already figured this out, but netsh commands work behind the firewall, this is:

    Client requets -----> Firewall rules --------> Netsh rules

    So using only netsh commands will not work by themselves, they work with firewall rules as well

    I had it working by:

    - Opening the port in the firewall (do not assign it to any program, just open the port 80)
    - Run the netsh command (netsh interface portproxy add v4tov4 listenport=80 connectport=32400 connectaddress=192.168.0.100) Note that I'm not adding listenaddress since I want to allow any ip address to connect to port 80

    The result is:

    Client request port 80 -----> Firewall allow to pass -----> Netsh route from port 80 to 32400

    And that's it, let me know if you need more help

    Regards.

    George


    G.Waters



    • Edited by George Waters Wednesday, January 8, 2014 3:29 AM
    • Proposed as answer by George Waters Wednesday, January 8, 2014 10:41 PM
    Wednesday, January 8, 2014 3:26 AM
  • I'm sorry, I should have mentioned that I also opened up my inbound port 80 in Windows Firewall.

    I've gotten home from work and after I booted up my desktop, it worked. I've rebooted 10 times, it works now!?

    It got late last night, I must have been tired..

    Also thanks for the advice about leaving listenaddress out, I've actually modified my bat file to just have:

    netsh interface portproxy add v4tov4 listenport=80 connectport=32400 connectaddress=127.0.0.1

    That way, if my router gives me a new IP at some point, it won't break.

    Thanks again George, it's probably a VERY good thing to let everybody else know that Firewalls still block before packets reach the portproxy interface! :)

    Kind regards

    Mark

    Wednesday, January 8, 2014 7:28 PM
  • I having simular issue 2 sets of Windows 2008 R2 Servers once connects fine the other doesn't
    netsh interface portproxy add v4tov4 listenaddress=172.16.16.1 listenport=445 connectaddress=172.16.16.1 connectport=44445

    on the working server c:\>netstat -an | find ":445"
      TCP    172.16.16.1:445        0.0.0.0:0              LISTENING

    on the non-working server C:\>netstat -an | find ":445"
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
      TCP    [::]:445               [::]:0                 LISTENING

    netsh interface portproxy>show helper
    NO IPV6MON.DLL on any of the Servers and they all have ipv6 installed and the portproxy is to MS Loopback adapter with every thing unchecked but TCP/IP v4

    Config is very similar to https://www.angryadmin.co.uk/?s=portproxy only using 172.16.16.1 for the loopback adapter.

    Also belive IPV6MON.DLL may only be on Windows XP sp2

    http://support.microsoft.com/kb/555744/en-us

    see section article applies to: windows xp sp2

    Thursday, May 8, 2014 4:54 PM
  • So long as you have IPV6 installed, the most common problem thereafter is setting your listen port to the same as your connect port, when also using your connect address as 127.0.0.1. (Assuming you've already disabled your firewall for testing)

    What worked for me was using a free port as the listen port, and then pointing traffic at the connect port where my app was on 127.0.0.1.

    You'll know it worked, as when using TCPView you will see svchost.exe open up the listener.  When the command fails (netsh gives you no feedback on this) you will notice svchost.exe does nothing in the way of opening up the listener.  

    Hope it helps..


    • Edited by ShaunHed Tuesday, May 13, 2014 7:18 AM
    Tuesday, May 13, 2014 7:17 AM
  • @Mythink: I am currently facing the exact same problem but I'm on Windows 8.1.  In our case, I think the LanmanServer is getting to the port first which is preventing the portproxy rule from going into effect.

    In my case, disabling the LanmanServer service and rebooting resulted in the IP helper service (iphlpsvc) listening on port 445 of the loopback adapter.  When I manually started the LanmanServer afterwards, file and printer sharing was restored and SMB over SSH continued to work.  So this definitely looks timing related.  I've played around a bit, but I can't quite figure out the dependencies for the service startup.  Perhaps someone knowledgeable can share some wisdom.

    Saturday, July 19, 2014 11:56 PM
  • Don't know if this helps, but I experienced exactly what replicat said. Timing's the issue.

    After putting in the portproxy add commands I had to disable three services: lanmanserver, smb and iphlpsvc, reboot and start iphlpsvc manually and it was fine.

    Seems clunky so I just wrote a script that does it all at each user logon. The script disables all three when it's done so that it can keep them from launching too early on the next reboot.

    Still a little clunky because it requires a scheduled task and a script, but it's invisible and seamless to the user - it's done before the desktop even comes up usually.

    Friday, July 25, 2014 4:10 AM
  • In my case netsh didn't work because IPHelper service was disabled.
    Monday, December 5, 2016 4:46 PM
  • If listenaddress is not a local address, netsh will not work.
    
    Solution:
    
    you can add it by the follwoing command:
    
    netsh int ipv4 add addr "Ethernet0 " 10.0.50.111/32
    


    • Edited by rainkin Monday, May 1, 2017 12:54 PM
    Monday, May 1, 2017 12:49 PM
  • 我也出现类似的情况,谢谢!!
    Friday, August 18, 2017 4:43 AM
  • Why it doesn't work when connectaddress is 127.0.0.1.

    Administrator

    C:\Windows\system32>netsh interface portproxy add v4tov4 listenport=20000 connectaddress=10.86.50.178 connectport=80 protocol=tcp
    
    C:\Windows\system32>netsh interface portproxy show all
    
    Listen on IPv4:             Connect to IPv4:
    
    Address         Port        Address         Port
    --------------- ----------  --------------- ----------
    *               20000       10.86.50.178    80
    *               8080        127.0.0.1       80

    Listened ports (the port 8080 is not listened and cannot be connected and 20000 is listened):

    C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>netstat -an | findstr LISTE
    N
      TCP    0.0.0.0:21             0.0.0.0:0              LISTENING
      TCP    0.0.0.0:21             0.0.0.0:0              LISTENING
      TCP    0.0.0.0:25             0.0.0.0:0              LISTENING
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING    // <------  
      TCP    0.0.0.0:110            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:143            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:554            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:587            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:1026           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:1027           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:1028           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:1292           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:4793           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:10243          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:11200          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:16422          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:20000          0.0.0.0:0              LISTENING    // <--------
      TCP    10.86.50.178:139       0.0.0.0:0              LISTENING
      TCP    127.0.0.1:5939         0.0.0.0:0              LISTENING
      TCP    127.0.0.1:10000        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:10001        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:10002        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:49177        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:49178        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:49186        0.0.0.0:0              LISTENING
      TCP    [::]:21                [::]:0                 LISTENING
      TCP    [::]:21                [::]:0                 LISTENING
      TCP    [::]:135               [::]:0                 LISTENING
      TCP    [::]:445               [::]:0                 LISTENING
      TCP    [::]:554               [::]:0                 LISTENING
      TCP    [::]:1025              [::]:0                 LISTENING
      TCP    [::]:1026              [::]:0                 LISTENING
      TCP    [::]:1027              [::]:0                 LISTENING
      TCP    [::]:1028              [::]:0                 LISTENING
      TCP    [::]:1292              [::]:0                 LISTENING
      TCP    [::]:2869              [::]:0                 LISTENING
      TCP    [::]:3587              [::]:0                 LISTENING
      TCP    [::]:4793              [::]:0                 LISTENING
      TCP    [::]:5357              [::]:0                 LISTENING
      TCP    [::]:10243             [::]:0                 LISTENING
      TCP    [::1]:14147            [::]:0                 LISTENING


    My enviroment (systeminfo) is winodws 7 in VMware Virtual Platform and has TCP/IPv6 installed and the service IP Helper running.

    Microsoft Windows 7 Enterprise
    6.1.7601 Service Pack 1 Build 7601

    You need to install IPv6 (Run->Settings->Control Panel->Network Connections->Local Area Connection->Properties->Install->Protocol->Microsoft TCP/IP version 6), otherwise this feature won’t work. It’s a known bug in netsh and it doesn’t look like Microsoft is going to fix it.

    and here is the Microsoft KB article :

    http://support.microsoft.com/kb/555744

    C:\Users\ssfang>netsh
    netsh>show helper
    Helper GUID                             DLL Filename  Command
    --------------------------------------  ------------  -------
    {02BC1F81-D927-4EC5-8CBC-8DD65E3E38E8}  AUTHFWCFG.DLL  advfirewall
    {FB10CBCA-5430-46CE-B732-079B4E23BE24}  AUTHFWCFG.DLL    consec
    {35342B49-83B4-4FCC-A90D-278533D5BEA2}  AUTHFWCFG.DLL    firewall
    {4BD827F7-1E83-462D-B893-F33A80C5DE1D}  AUTHFWCFG.DLL    mainmode
    {4D0FEFCB-8C3E-4CDE-B39B-325933727297}  AUTHFWCFG.DLL    monitor
    {A31CB05A-1213-4F4E-B420-0EE908B896CB}  PEERDISTSH.DLL  branchcache
    {555EA58E-72B1-4F0A-9055-779D0F5400B2}  PEERDISTSH.DLL    smb
    {00770721-44EA-11D5-93BA-00B0D022DD1F}  HNETMON.DLL   bridge
    {6DC31EC5-3583-4901-9E28-37C28113656A}  DHCPCMONITOR.DLL  dhcpclient
    {8A6D23B3-0AF2-4101-BC6E-8114B325FE17}  NETIOHLP.DLL  dnsclient
    {8B3A0D7F-1F30-4402-B753-C4B2C7607C97}  FWCFG.DLL     firewall
    {44F3288B-DBFF-4B31-A86E-633F50D706B3}  NSHHTTP.DLL   http
    {0705ECA1-7AAC-11D2-89DC-006008B0E5B9}  IFMON.DLL     interface
    {1C151866-F35B-4780-8CD2-E1924E9F03E1}  NETIOHLP.DLL    6to4
    {97C192DB-A774-43E6-BE78-1FABD795EEAB}  NETIOHLP.DLL    httpstunnel
    {725588AC-7A11-4220-A121-C92C915E8B73}  NETIOHLP.DLL    ipv4
    {500F32FD-7064-476B-8FD6-2171EA46428F}  NETIOHLP.DLL    ipv6
    {90E1CBE1-01D9-4174-BB4D-EB97F3F6150D}  NETIOHLP.DLL      6to4
    {90E1CBE1-01D9-4174-BB4D-EB97F3F6150D}  NETIOHLP.DLL      isatap
    {1C151866-F35B-4780-8CD2-E1924E9F03E1}  NETIOHLP.DLL    isatap
    {1C151866-F35B-4780-8CD2-E1924E9F03E1}  NETIOHLP.DLL    portproxy
    {78197B47-2BEF-49CA-ACEB-D8816371BAA8}  NETIOHLP.DLL    tcp
    {1C151866-F35B-4780-8CD2-E1924E9F03E1}  NETIOHLP.DLL    teredo
    {F7E0BC27-BA6E-4145-A123-012F1922F3F1}  NSHIPSEC.DLL  ipsec
    {F7E0BC29-BA6E-4145-A123-012F1922F3F1}  NSHIPSEC.DLL    dynamic
    {F7E0BC28-BA6E-4145-A123-012F1922F3F1}  NSHIPSEC.DLL    static
    {1D8240C7-48B9-47CC-9E40-4F7A0A390E71}  DOT3CFG.DLL   lan
    {B572D5F3-E15B-4501-84F2-6626F762AFB1}  WWANCFG.DLL   mbn
    {B341E8BA-13AA-4E08-8CF1-A6F2D8B0C229}  NETIOHLP.DLL  namespace
    {00B399EA-447F-4B19-8393-F9D71D7760F9}  NAPMONTR.DLL  nap
    {3F8A1180-FF5D-4B5B-934C-D08DFFBC9CBC}  NAPMONTR.DLL    client
    {B123BAAA-79E9-49FD-AB2C-E87C56CE4CFF}  NAPMONTR.DLL    hra
    {931852E2-597D-40B9-B927-55FFC81A6104}  NETIOHLP.DLL  netio
    {B7BE4347-E851-4EEC-BC65-B0C0E87B86E3}  P2PNETSH.DLL  p2p
    {9E0D63D7-4644-476B-9DAC-D62F96E08376}  P2PNETSH.DLL    collab
    {6ED05238-F6A3-F801-967A-5CAD6F6CAC56}  P2PNETSH.DLL      contact
    {E35A9D1F-61E8-4CF5-A46C-0F715A9303B8}  P2PNETSH.DLL    group
    {9AA625FC-7E31-4679-B5B5-DFC67A3510AB}  P2PNETSH.DLL      database
    {FBFC037E-D455-4B8D-80A5-B379002DBCAD}  P2PNETSH.DLL    idmgr
    {9E0D63D6-4644-476B-9DAC-D64F96E01376}  P2PNETSH.DLL    pnrp
    {1DD4935A-E587-4D16-AE27-14E40385AB12}  P2PNETSH.DLL      cloud
    {AD1D76C9-434B-48E0-9D2C-31FA93D9635A}  P2PNETSH.DLL      diagnostics
    {6EC05238-F6A3-4801-967A-5C9D6F6CAC50}  P2PNETSH.DLL      peer
    {0705ECA2-7AAC-11D2-89DC-006008B0E5B9}  RASMONTR.DLL  ras
    {42E3CC21-098C-11D3-8C4D-00104BCA495B}  RASMONTR.DLL    aaaa
    {90FE6CFC-B6A2-463B-AA12-25E615EC3C66}  RASMONTR.DLL    diagnostics
    {13D12A78-D0FB-11D2-9B76-00104BCA495B}  RASMONTR.DLL    ip
    {36B3EF76-94C1-460F-BD6F-DF0178D90EAC}  RASMONTR.DLL    ipv6
    {592852F7-5F6F-470B-9097-C5D33B612975}  RPCNSH.DLL    rpc
    {C07E293F-9531-4426-8E5C-D7EBBA50F693}  RPCNSH.DLL      filter
    {D3E9D893-852F-4E22-B05D-99293065773D}  NETTRACE.DLL  trace
    {C100BECD-D33A-4A4B-BF23-BBEF4663D017}  WCNNETSH.DLL  wcn
    {3BB6DA1D-AC0C-4972-AC05-B22F49DEA9B6}  NSHWFP.DLL    wfp
    {0BFDC146-56A3-4311-A7D5-7D9953F8326E}  WHHELPER.DLL  winhttp
    {B2C0EEF4-CCE5-4F55-934E-ABF60F3DCF56}  WSHELPER.DLL  winsock
    {D424E730-1DB7-4287-8C9B-0774F5AD0576}  WLANCFG.DLL   wlan
    netsh>interface portproxy
    netsh interface portproxy>show helper
    Helper GUID                             DLL Filename  Command
    --------------------------------------  ------------  -------
    {02BC1F81-D927-4EC5-8CBC-8DD65E3E38E8}  AUTHFWCFG.DLL  advfirewall
    {FB10CBCA-5430-46CE-B732-079B4E23BE24}  AUTHFWCFG.DLL    consec
    {35342B49-83B4-4FCC-A90D-278533D5BEA2}  AUTHFWCFG.DLL    firewall
    {4BD827F7-1E83-462D-B893-F33A80C5DE1D}  AUTHFWCFG.DLL    mainmode
    {4D0FEFCB-8C3E-4CDE-B39B-325933727297}  AUTHFWCFG.DLL    monitor
    {A31CB05A-1213-4F4E-B420-0EE908B896CB}  PEERDISTSH.DLL  branchcache
    {555EA58E-72B1-4F0A-9055-779D0F5400B2}  PEERDISTSH.DLL    smb
    {00770721-44EA-11D5-93BA-00B0D022DD1F}  HNETMON.DLL   bridge
    {6DC31EC5-3583-4901-9E28-37C28113656A}  DHCPCMONITOR.DLL  dhcpclient
    {8A6D23B3-0AF2-4101-BC6E-8114B325FE17}  NETIOHLP.DLL  dnsclient
    {8B3A0D7F-1F30-4402-B753-C4B2C7607C97}  FWCFG.DLL     firewall
    {44F3288B-DBFF-4B31-A86E-633F50D706B3}  NSHHTTP.DLL   http
    {0705ECA1-7AAC-11D2-89DC-006008B0E5B9}  IFMON.DLL     interface
    {1C151866-F35B-4780-8CD2-E1924E9F03E1}  NETIOHLP.DLL    6to4
    {97C192DB-A774-43E6-BE78-1FABD795EEAB}  NETIOHLP.DLL    httpstunnel
    {725588AC-7A11-4220-A121-C92C915E8B73}  NETIOHLP.DLL    ipv4
    {500F32FD-7064-476B-8FD6-2171EA46428F}  NETIOHLP.DLL    ipv6
    {90E1CBE1-01D9-4174-BB4D-EB97F3F6150D}  NETIOHLP.DLL      6to4
    {90E1CBE1-01D9-4174-BB4D-EB97F3F6150D}  NETIOHLP.DLL      isatap
    {1C151866-F35B-4780-8CD2-E1924E9F03E1}  NETIOHLP.DLL    isatap
    {1C151866-F35B-4780-8CD2-E1924E9F03E1}  NETIOHLP.DLL    portproxy
    {78197B47-2BEF-49CA-ACEB-D8816371BAA8}  NETIOHLP.DLL    tcp
    {1C151866-F35B-4780-8CD2-E1924E9F03E1}  NETIOHLP.DLL    teredo
    {F7E0BC27-BA6E-4145-A123-012F1922F3F1}  NSHIPSEC.DLL  ipsec
    {F7E0BC29-BA6E-4145-A123-012F1922F3F1}  NSHIPSEC.DLL    dynamic
    {F7E0BC28-BA6E-4145-A123-012F1922F3F1}  NSHIPSEC.DLL    static
    {1D8240C7-48B9-47CC-9E40-4F7A0A390E71}  DOT3CFG.DLL   lan
    {B572D5F3-E15B-4501-84F2-6626F762AFB1}  WWANCFG.DLL   mbn
    {B341E8BA-13AA-4E08-8CF1-A6F2D8B0C229}  NETIOHLP.DLL  namespace
    {00B399EA-447F-4B19-8393-F9D71D7760F9}  NAPMONTR.DLL  nap
    {3F8A1180-FF5D-4B5B-934C-D08DFFBC9CBC}  NAPMONTR.DLL    client
    {B123BAAA-79E9-49FD-AB2C-E87C56CE4CFF}  NAPMONTR.DLL    hra
    {931852E2-597D-40B9-B927-55FFC81A6104}  NETIOHLP.DLL  netio
    {B7BE4347-E851-4EEC-BC65-B0C0E87B86E3}  P2PNETSH.DLL  p2p
    {9E0D63D7-4644-476B-9DAC-D62F96E08376}  P2PNETSH.DLL    collab
    {6ED05238-F6A3-F801-967A-5CAD6F6CAC56}  P2PNETSH.DLL      contact
    {E35A9D1F-61E8-4CF5-A46C-0F715A9303B8}  P2PNETSH.DLL    group
    {9AA625FC-7E31-4679-B5B5-DFC67A3510AB}  P2PNETSH.DLL      database
    {FBFC037E-D455-4B8D-80A5-B379002DBCAD}  P2PNETSH.DLL    idmgr
    {9E0D63D6-4644-476B-9DAC-D64F96E01376}  P2PNETSH.DLL    pnrp
    {1DD4935A-E587-4D16-AE27-14E40385AB12}  P2PNETSH.DLL      cloud
    {AD1D76C9-434B-48E0-9D2C-31FA93D9635A}  P2PNETSH.DLL      diagnostics
    {6EC05238-F6A3-4801-967A-5C9D6F6CAC50}  P2PNETSH.DLL      peer
    {0705ECA2-7AAC-11D2-89DC-006008B0E5B9}  RASMONTR.DLL  ras
    {42E3CC21-098C-11D3-8C4D-00104BCA495B}  RASMONTR.DLL    aaaa
    {90FE6CFC-B6A2-463B-AA12-25E615EC3C66}  RASMONTR.DLL    diagnostics
    {13D12A78-D0FB-11D2-9B76-00104BCA495B}  RASMONTR.DLL    ip
    {36B3EF76-94C1-460F-BD6F-DF0178D90EAC}  RASMONTR.DLL    ipv6
    {592852F7-5F6F-470B-9097-C5D33B612975}  RPCNSH.DLL    rpc
    {C07E293F-9531-4426-8E5C-D7EBBA50F693}  RPCNSH.DLL      filter
    {D3E9D893-852F-4E22-B05D-99293065773D}  NETTRACE.DLL  trace
    {C100BECD-D33A-4A4B-BF23-BBEF4663D017}  WCNNETSH.DLL  wcn
    {3BB6DA1D-AC0C-4972-AC05-B22F49DEA9B6}  NSHWFP.DLL    wfp
    {0BFDC146-56A3-4311-A7D5-7D9953F8326E}  WHHELPER.DLL  winhttp
    {B2C0EEF4-CCE5-4F55-934E-ABF60F3DCF56}  WSHELPER.DLL  winsock
    {D424E730-1DB7-4287-8C9B-0774F5AD0576}  WLANCFG.DLL   wlan




    please verify my account.


    • Edited by kekkou Thursday, March 22, 2018 12:24 PM Add my environment in details
    Thursday, March 22, 2018 11:38 AM
  • I have exactly the same problem in Win7 Enterpise. I did not see IPV6 DLL in the show helper, too. All netsh portproxy command end without error but netstat shows ALL commands has no effect. No new listening ports come into existence.

    I finally abandon to use Win7 Ent to forward the port. I just downloaded a simple port copy software and it does the mapping nicely. 

    To all the incoming net admin who encounter this problem, forget about the netsh portproxy command. It is a waste of time. You may even consider writing the port forward program yourself.

    Wednesday, April 11, 2018 6:41 PM
  • I don't know if this even matters anymore, or if you have found a solution, but what fixed mine was
    1. Press windows + r

    2. type services.msc

    3. Locate Net.Tcp Port Sharing Service

    4. Right click it and open properties

    5. change its startup type to automatic, and then apply

    6. press start

    this is what fixed mine i know i'm 8 years late, but this might help someone

    Sunday, May 19, 2019 2:20 AM