This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

sentinel nat-t works fine now, but:

no data is transferred. i acquired a virtual ip in sentinal, the connection shows to be up. i also tried to set the rules on both firewall to any-any-allow for testing purposes. won't work.

any hint?

thanks,

sebastian

This thread was automatically locked due to age.

Parents

0 seb-zrh over 22 years ago

this meesage shows up, mmmh... any idea?

Warning: peer is NATed but source port is still udp/500. Ipsec-passthrough NAT device suspected -- NAT-T may not work.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 seb-zrh over 22 years ago

this meesage shows up, mmmh... any idea?

Warning: peer is NATed but source port is still udp/500. Ipsec-passthrough NAT device suspected -- NAT-T may not work.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Andy_01 over 22 years ago in reply to seb-zrh

NAT-T doesn't work if the router inbetween does IPSEC passthrough, you can only use NAT-T without IPSEC passthrough turned on OR rely on IPSEC passthrough.
Cancel
Vote Up 0 Vote Down

Cancel
0 seb-zrh over 22 years ago in reply to Andy_01

ah, i see. how do i "turn off" ipsec? just delete any corresponding entries in ipsec-window?

thanks,
sebastian
Cancel
Vote Up 0 Vote Down

Cancel
0 Volker over 22 years ago in reply to seb-zrh

Just disable NAT_T in your Sentinel Client, and everything might work. I had a DSL Router on the Client Side with IPSEC-Pass Through. I disabled the NAT-T in the Sentinel Client and I got a working connection.

Volker Wend
Cancel
Vote Up 0 Vote Down

Cancel