Server IPaddress Change now L2TP will not connect

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
dfwtx
Posts: 5
Joined: Mon Aug 13, 2018 1:06 am

Server IPaddress Change now L2TP will not connect

Post by dfwtx » Mon Aug 20, 2018 3:11 pm

I am having an issue after changing to a new Internet provider. Everything else seems to work, but now L2TP will not complete the VPN connection.

Do I need to rebuild any certificates or change an IP that is cached somewhere within the VPN server? I have it set to listen on 0.0.0.0.

2018-08-12 20:19:32.890 IPsec Client 12 (serverip:500 -> 0.0.0.0:500): A new IPsec client is created.
2018-08-12 20:19:32.890 IPsec IKE Session (IKE SA) 11 (Client: 12) (serverip:500 -> 0.0.0.0:500): A new IKE SA (Main Mode) is c
reated. Initiator Cookie: (cookie-was-here, Responder Cookie: (cooke-was-here), DH Group: MODP 2048 (Group 14), Hash Algori
thm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2018-08-12 20:19:35.015 IPsec Client 12 (serverip:4500 -> 0.0.0.0:4500): The port number information of this client is updated.
2018-08-12 20:19:35.015 IPsec Client 12 (serverip:4500 -> 0.0.0.0:4500):
2018-08-12 20:19:35.015 IPsec IKE Session (IKE SA) 11 (Client: 12) (serverip:4500 -> 0.0.0.0:4500): This IKE SA is established
between the server and the client.
2018-08-12 20:19:36.065 IPsec IKE Session (IKE SA) 11 (Client: 12) (serverip:4500 -> 0.0.0.0:4500): The client initiates a Quic
kMode negotiation.
2018-08-12 20:19:36.065 IPsec ESP Session (IPsec SA) 22 (Client: 12) (serverip:4500 -> 0.0.0.0:4500): A new IPsec SA (Direction
: Client -> Server) is created. SPI: 0xC654F75B, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key
Size: 256 bits, Lifetime: 250000 Kbytes or 3600 seconds
2018-08-12 20:19:36.065 IPsec ESP Session (IPsec SA) 22 (Client: 12) (serverip:4500 -> 0.0.0.0:4500): A new IPsec SA (Direction
: Server -> Client) is created. SPI: 0x5C3C8C82, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key
Size: 256 bits, Lifetime: 250000 Kbytes or 3600 seconds
2018-08-12 20:19:36.207 IPsec ESP Session (IPsec SA) 22 (Client: 12) (serverip:4500 -> 0.0.0.0:4500): This IPsec SA is establis
hed between the server and the client.
2018-08-12 20:19:36.207 IPsec Client 12 (serverip:4500 -> 0.0.0.0:4500): The L2TP Server Module is started.

Thanks in advance,
Jason

dfwtx
Posts: 5
Joined: Mon Aug 13, 2018 1:06 am

Re: Server IPaddress Change now L2TP will not connect

Post by dfwtx » Thu Aug 30, 2018 6:26 am

No one has any idea why L2TP is the only part of the VPN server that doesn't work after changing to a new Internet provider? The logs don't give me any clue as to why.

cedar
Site Admin
Posts: 955
Joined: Sat Mar 09, 2013 5:37 am

Re: Server IPaddress Change now L2TP will not connect

Post by cedar » Thu Aug 30, 2018 10:16 am

There is no error in the scope of your log. Please show more.

dfwtx
Posts: 5
Joined: Mon Aug 13, 2018 1:06 am

Re: Server IPaddress Change now L2TP will not connect

Post by dfwtx » Thu Aug 30, 2018 2:00 pm

More from where? That is all it gives. Is their a way to increase the log level to produce more? I agree I have not been able to figure out why it fails with the current logs.

dfwtx
Posts: 5
Joined: Mon Aug 13, 2018 1:06 am

[solved] Server IPaddress Change now L2TP will not connect

Post by dfwtx » Thu Aug 30, 2018 2:37 pm

I just backed up the config reinstalled and it works now. I wonder if it has something to do with the certificates. After it rebuilt with the new install it worked.

Post Reply