opening tcp port 8190

[deftech]

I need this port open, so I set up a tcp mapping using that service port, and enabled the default mapping to the local machine I need it for, on that port 8190 as well.

Is this all I need to do to open ports?

The client machine is not using NAT. I just having it using wingate as a proxy server.

Thanks

[Pascal]

Should be; creating bindings on interfaces results in firewall holes being opened/closed as required. You can double check this by looking at the automatically opened holes in the Port Security section of ENS.

Of course, the alternative is to use ENS to redirect. It should normally be marginally faster than a TCP mapping.

[deftech]

Ah yes, I think what you suggest through ENS is better. I deleted my tcp mapping.

I setup under "port security" in ENS "LAN connections to internet" TCP 8190. That should allow the client computers' software to communicate out to the net on port 8190 correct?

I appreciate your comments and advice :)

[Pascal]

There are a few different firewall actions.

1. Open a hole. This allows connections through the specifier. (LAN connections to internet, for example)

2. Redirect. This redirects traffic from the one end to a specified IP on the other end. (Open a Inet side hole, redirect to LAN ip)

3. Block. This creates an effective hole.

By default you should not need to create holes on the LAN side. WinGate automatically trusts your local network when you make it "Internal". The only case where you'd need to explicitly open holes are if you've set the default action for LAN to Internet to be "Deny" and want to only allow communication on certain ports.

So the client computers should not need to have a hole opened for them if they are the ones starting the connection process.

If the remote computer starts the connection you would need to setup a redirect in the Internet to LAN table, as that is the direction the traffic is coming from.