Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

Binding error in UDP port.

May 06 06 3:26 am

Hello all!

In two different installations (WinGate 6.1.1) I have tried to make a UDP mapping on port 500.
Binding is not working. The service icon is a red "!" and the log file shows "error 10013".

What can I do?

Thanx!

May 06 06 4:06 am

Not sure about error 10013, but check if there is another process bound to that port.

open up a cmd prompt, and see if you can see udp port 500 already listening:

netstat -an

May 06 06 8:47 pm

Error 10013 means not enough permissions to bind on this port - one of the reasons of this can be another system application bound on the same port.

May 07 06 1:14 am

Hi thanx for reply!!

In port 500 UDP is running a part of IPSec.
If I stop IPSec service binding works great, but I need IPSec working.
My customer needs make a mapping for his checkpoint.

How can I do this UDP mapping without disable IPSec service?

Regards!
Ricardo

May 07 06 3:21 pm

Hi Ricardo,

Can you elaborate on the connectivity your client needs?

i.e. LAN Client does not have NAT, but needs to access UDP 500 on Checkpoint, the application they are using can specify a differnet port; i.e. 499

---> You could crate a port redirection via the ENS --> Port Security --> "LAN Connections to WinGate", set it up to listen on 499 and redirect to port 500 on the Checkpoint

May 07 06 8:13 pm

As Roderick suggested the ENS redirect would be your best course of action - you can't "officially" bind this socket.
Post a reply