IKE NAT-T breaks L2TP/IPSec

E

Eric Vyncke

After installing 818043 (the NAT-T feature for IPSec), the
IKE negotiation fails....

Some debugging shows that my XP Home Edition is now
proposing a wrong IKE phase 2 ID: instead of protecting
only the UDP/1701, it requests all protocols (0 as
protocol and opaque as port).

Obviously, the other end (a Cisco router) refuses this
proposal and the VPN does not start.

Thanks for any information

-eric
 
S

Smich Peral

Eric,
I am also seeing the same thing with the windows 2000 818043 update.
With the exact same 0 protocol. I was curious if your IKE phase 2
fails with proxy identites not supported? I thought for sure i was
the only person on the planet trying this. Have you made any headway?

Regards,
Smich
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top