<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
I look deeper into this issue and found some Sonicwall documents on <br>their web site. Apparently I needed to enable phase I agressive mode.<br><br>I added "aggrmode=yes" to my connection definition and got past Xauth <br>authentication. I am know bumping into other problems, but these are <br>for another thread (after some more research). Thanks for your help.<br><br>By the way - in my research I read that 2.6 kernels do not require the line<br><br> interfaces="ipsec0=eth0"<br><br>in the config file. I took it out and it seemed to have no effect. Is <br>this correct?<br><br>Best,<br>Dave<br><br><br>Paul Wouters wrote:<br>> On Mon, 15 Sep 2008, Hot Mailing wrote:<br>><br>>> 106 "WorkOffice" #1: STATE_MAIN_I2: sent MI2, expecting MR2<br>>> 003 "WorkOffice" #1: ignoring unknown Vendor ID payload <br>>> [404bf439522ca3f6]<br>>> 003 "WorkOffice" #1: received Vendor ID payload [XAUTH]<br>>> 003 "WorkOffice" #1: received Vendor ID payload [Dead Peer Detection]<br>>> 003 "WorkOffice" #1: NAT-Traversal: Result using RFC 3947<br>>> (NAT-Traversal): i am NATed<br>>> 108 "WorkOffice" #1: STATE_MAIN_I3: sent MI3, expecting MR3<br>>> 003 "WorkOffice" #1: Mode Config message is unacceptable because it is<br>>> for an incomplete ISAKMP SA (state=STATE_MAIN_I3)<br>><br>> We are expecting an MR3 packet to finish setting up phase 1, but we are<br>> getting a mode config packet. This looks like a Sonicwall bug. I have<br>> a vague recollection that this has been seen before. Try googling the<br>> archives for 'xauth sonicwall' ?<br>><br>> Paul<br>><br>><br><br><br /><hr />See how Windows Mobile brings your life together—at home, work, or on the go. <a href='http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/' target='_new'>See Now</a></body>
</html>