# Neue Seite

The command syntax is as follows:

`netsh interface portproxy add v4tov4 listenaddress=localaddress listenport=localport connectaddress=destaddress connectport=destport`

where

<div id="bkmrk-">  
</div>- **listenaddress** –is a local IP address to listen for incoming connection (useful if you have multiple NICs in different subnets/[VLANs](http://woshub.com/configure-multiple-vlan-on-windows/) or [multiple IP addresses on one interface](http://woshub.com/assign-multiple-ip-addresses-single-nic-windows/));
- **listenport** – a local TCP port number to listen on (the connection is waiting on);
- **connectaddress** – is a local or remote IP address (or DNS name) to which you want to redirect the incoming connection;
- **connectport** – is a TCP port to which the connection from `listenport` is forwarded to.

<div class="info_box" id="bkmrk-using-the%C2%A0netsh-inte">Using the `netsh interface portproxy add` `v4tov6`/`v6tov4`/`v6tov6` options, you can create port forwarding rules between IPv4 and IPv6 a</div><div class="info_box" id="bkmrk--1"></div>`netstat -na|find "3340"`

Alternatively, you can check that the port is not listening locally using [the PowerShell cmdlet Test-NetConnection](http://woshub.com/checking-tcp-port-response-using-powershell/):

`Test-NetConnection -ComputerName localhost -Port 3340`

``