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

tried it using a the real IP of the adapter, not the loopback address?

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

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

Yeah, I tried adding an exception and just turning the firewall off and neither made any difference :(

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, MilesPlease 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.

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.