VPN to NetGear FVS318 from Windows XP 1

[jasoncout]

I just got a Netgear FVS318 and I'm trying to set up a VPN connection to it. I don't want to buy any additional software, so I'd like to use Windows XPs VPN client. I have downloaded the Win2k instructions from Netgear, but I still cannot connect. I don't get anything in the FVS318s logs regarding VPN, so I don't think I even get close. I'm pretty sure the problem is that the IPSec service on my laptop won't start. I get the following error when I try to start it:

Error 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.

I don't have any idea what this means. It's on a IBM ThinkPad T30. Someone else has the exact same model as I do, and IPSec won't start on theirs either, but it will start fine on my desktop (which is inside the firewall, so VPN isn't needed). Any ideas?? Thanks.

Jason Coutermarsh
jasoncout@bigfoot.com

 

[jmellon]

You may want to make sure that another VPN client isn't installed on the machine already. I had a similar problem to yours and realized that I had the SonicWall VPN client installed. After I stopped the SafeNet IKE service and the SafeNet Monitor service, I was able to start the IPSec service.

 

[Darrenzo]

You can't use Windows XP's native VPN client software to connect to a FVS318. You need to set up an IPSec policy to securely tunnel through on of the VPN ports on the router. Either that or buy a third party client software package.

Here's some instructions on how to set up an IPSec policy for connecting to the FVS318:-

http://home.stny.rr.com/ranch/reference/FVS318_W2Kupdated.pdf

tip: use XP Pro

- Darren

 

[Gumbolia]

I am also very new to this. It's only been two days with the FVS318. Dose anyone know where this document can be found related to XP. Things are quite different and a bit confusing.

Thanks Gumbolia
petrykja@wideopenwest.com

 

[Splixx]

I printed out that FVS318_Win2000 document and attempted to follow it to the letter.
However when I was done I could not even see my client hitting the 318 in the logs. I disabled the settings on the XP client and now I hit the 318 but get error messages. It leads me to believe I have the IP adresses set wrong, or something on my XP client...


Tues, 05/18/2004 13:30:52 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:30:52 - IKEeer Initialized IKE Main Mode
Tues, 05/18/2004 13:30:52 - IKE:main_inI1_outR1() connection not found 24.121.44.184[500]-24.121.46.219[500]
Tues, 05/18/2004 13:30:52 - IKE:Trying Dynamic IP Searching
Tues, 05/18/2004 13:30:52 - IPsec:instantiated "FVS318_WinXP_tmp0" for 24.121.46.219
Tues, 05/18/2004 13:30:52 - IKE:[FVS318_WinXP_tmp0] RX << MM_I1 : 24.121.46.219
Tues, 05/18/2004 13:30:52 - IPsec:New State index:0, sno:1
Tues, 05/18/2004 13:30:52 - IPsec:loglog[3] *#User don't want to use 3DES..... Attribute OAKLEY_ENCRYPTION_ALGORITHM
Tues, 05/18/2004 13:30:52 - IPsec:loglog[3] *#User don't want to use 3DES..... Attribute OAKLEY_ENCRYPTION_ALGORITHM
Tues, 05/18/2004 13:30:52 - IPsec:Oakley Transform 3 accepted
Tues, 05/18/2004 13:30:52 - IKE:OAKLEY_PRESHARED_KEY/OAKLEY_DES_CBC/MODP768
Tues, 05/18/2004 13:30:52 - IKE:[FVS318_WinXP_tmp0] TX >> MM_R1 : 24.121.46.219
Tues, 05/18/2004 13:30:52 - IPsec:inserting event EVENT_RETRANSMIT, timeout in 10 seconds for #1
Tues, 05/18/2004 13:30:52 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:30:52 - IKE:[FVS318_WinXP_tmp0] RX << MM_I2 : 24.121.46.219
Tues, 05/18/2004 13:30:52 - IKE:[FVS318_WinXP_tmp0] TX >> MM_R2 : 24.121.46.219
Tues, 05/18/2004 13:30:52 - IPsec:inserting event EVENT_RETRANSMIT, timeout in 10 seconds for #1
Tues, 05/18/2004 13:30:54 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:30:54 - IKE:[FVS318_WinXP_tmp0] RX << MM_I3 : 24.121.46.219
Tues, 05/18/2004 13:30:54 - IPsececoded Peer's ID is ID_IPV4_ADDR:192.168.1.100 and 24.121.46.219 in st
Tues, 05/18/2004 13:30:54 - IKE:[FVS318_WinXP_tmp0] TX >> MM_R3 : 24.121.46.219
Tues, 05/18/2004 13:30:54 - IPsec:inserting event EVENT_SA_EXPIRE, timeout in 28980 seconds for #1
Tues, 05/18/2004 13:30:54 - IPsec:STATE_MAIN_R3: sent MR3, ISAKMP SA established
Tues, 05/18/2004 13:30:54 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:30:54 - IPsec:New State index:1, sno:2
Tues, 05/18/2004 13:30:54 - IKE:[FVS318_WinXP_tmp0] RX << QM_I1 : 24.121.46.219
Tues, 05/18/2004 13:30:54 - IPseceer client ID payload ID_IPV4_ADDR specifies protocol 17; we only support 0
Tues, 05/18/2004 13:30:54 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:30:54 - IPsec:loglog[3] *#hahaha.... next payload type of ISAKMP Hash Payload has an unknown value: 254
Tues, 05/18/2004 13:30:54 - IPsec:malformed payload in packet
Tues, 05/18/2004 13:30:56 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:30:56 - IPsec:loglog[3] *#hahaha.... next payload type of ISAKMP Hash Payload has an unknown value: 254
Tues, 05/18/2004 13:30:56 - IPsec:malformed payload in packet
Tues, 05/18/2004 13:31:00 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:31:00 - IPsec:loglog[3] *#hahaha.... next payload type of ISAKMP Hash Payload has an unknown value: 254
Tues, 05/18/2004 13:31:00 - IPsec:malformed payload in packet
Tues, 05/18/2004 13:31:08 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:31:08 - IPsec:loglog[3] *#hahaha.... next payload type of ISAKMP Hash Payload has an unknown value: 254
Tues, 05/18/2004 13:31:08 - IPsec:malformed payload in packet
Tues, 05/18/2004 13:31:24 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:31:24 - IPsec:loglog[3] *#hahaha.... next payload type of ISAKMP Hash Payload has an unknown value: 254
Tues, 05/18/2004 13:31:24 - IPsec:malformed payload in packet
Tues, 05/18/2004 13:31:56 - IPsec:Receive Packet address:0x1397478 from 24.121.46.219
Tues, 05/18/2004 13:31:56 - IKE:[FVS318_WinXP_tmp0] RX << XCHG_INFO : 24.121.46.219
Tues, 05/18/2004 13:31:56 - IPsec:Enter Process_DeleteSA() spi_len=16
Tues, 05/18/2004 13:31:56 - IKE:RX << DELETE ISAKMP SA : 24.121.46.219 ,I-R=dd 2c 54 5c 9f b4 e8 b0 91 24 40 47 13 3f a3 af
Tues, 05/18/2004 13:31:56 - IKE:[FVS318_WinXP_tmp0] ISAKMP SAs were Deleted!
Tues, 05/18/2004 13:33:54 - IPsec:[FVS318_WinXP_tmp0] is removed from the head of conn_list
Tues, 05/18/2004 13:33:54 - IPsec:Connection [FVS318_WinXP_tmp0] is deleted from connection table