IPSEC PFsense to windows 2003 server
-
I am trying to tunnel from my pfsense box to windows 2003 server but is not working
this is a part of the ipsec log from sistem logsracoon: INFO: unsupported PF_KEY message REGISTER
racoon: ERROR: failed to bind to address xx.xx.xx.xxx[500] (Address already in use).
racoon: INFO: fe80::240:95ff:fe30:3229%rl0[500] used as isakmp port (fd=27)
racoon: INFO: 10.11.0.1[500] used as isakmp port (fd=26)
racoon: INFO: fe80::250:fcff:fee7:2079%vr0[500] used as isakmp port (fd=25)
racoon: INFO: 127.0.0.1[500] used as isakmp port (fd=24)
racoon: INFO: ::1[500] used as isakmp port (fd=23)
racoon: INFO: fe80::1%lo0[500] used as isakmp port (fd=22)
racoon: INFO: fe80::240:95ff:fe30:3229%ng1[500] used as isakmp port (fd=21)
racoon: INFO: xx.xx.xx.xxx[500] used as isakmp port (fd=20)
racoon: ERROR: failed to bind to address xx.xx.xx.xxx[500] (Address already in use).
racoon: INFO: fe80::240:95ff:fe30:3229%rl0[500] used as isakmp port (fd=26)
racoon: INFO: 10.11.0.1[500] used as isakmp port (fd=25)
racoon: INFO: fe80::250:fcff:fee7:2079%vr0[500] used as isakmp port (fd=24)
racoon: INFO: 127.0.0.1[500] used as isakmp port (fd=23)
racoon: INFO: ::1[500] used as isakmp port (fd=22)
racoon: INFO: fe80::1%lo0[500] used as isakmp port (fd=21)
racoon: INFO: fe80::240:95ff:fe30:3229%ng1[500] used as isakmp port (fd=20)
racoon: INFO: xx.xx.xx.xxx[500] used as isakmp port (fd=19)is anybody tried to create a tunnel between pfsense and windoews 2003 server?
please i need some help -
I'm getting the same error message, but it doesn't matter where I'm setting the tunnel to connect to. No matter what I point it at, I get the same message. I don't think its your server 2k3 box.
-
I had the same issue as well.
The version of PFsense I was using was 1.0. The tunnel was working fine for few days and all of a sudden it died and never came up. When I googled it and found that this was a bug with racoon (IPSEC) module and will be resolved in future releases.
http://cvstrac.pfsense.com/tktview?tn=1129
I found the root cause by debugging racoon module on pfsense through SSH console.In order to fix this isssue I upgraded my pfsense to 1.2 BETA 2 and now everything is working smoothly. My tunnel is now active for nearly 4 days.
-
I am using 1.2-RC2 and i get this error
To sunny chowdhry
Please tell me how to configure both ends of the tunnel so i can get it to work