SoftEther VPN User Forum

I have about 25 users who access our SoftEther vpn server from home on a weekly basis. Nine of these users have Windows 10 at home. Of those 9, 3 of them have been automatically upgraded to the Windows 10 Anniversary Update. All of three of the users who were updated to the latest Windows 10 update can no longer access and use the vpn server. They are able to authenticate, but they know longer reveive an IP address from the dhcp server. This is only affecting users with the latest Win10 update. All other users can connect and the vpn works fine. Only DHCP via the vpn server is affected, when not connected to the vpn the clients computers work fine.

We are using Server version: 419, Server build number: 9605, Oracle Linux x86_64

Users who are at this release can no longer aquire DHCP from Softether VPN.: Client OS name: "Windows 10", Client OS version: "Build 14393, Multiprocessor Free (14393.rs1_release.160805-1735)"
Client version: 419, Client build number: 9605

However, users at this release CAN still aquire DHCP and vpn works: Client OS name: "Windows 10" Client OS version: "Build 14393 Multiprocessor Free (14393.rs1_release.160715-1616)"
Client version: 419, Client build number: 9605,

I also tried rolling a system were vpn stopped working back from 14393.rs1_release.160805-1735 to 14393.rs1_release.160715-1616. The vpn still didn't work after this; no ip address via dhcp. I also tried updating the client to version: 421, Client build number: 9613 but this had no effect on the dhcp vpn problem.

Has anyone else encountered this problem? Does anyone have any troubleshooting recommendations? Or better yet, a fix for this problem?

Are there DHCP request and response logs in packet log?

thisjun wrote:
> Are there DHCP request and response logs in packet log?

There are requests, but no responses. DHCP server is on the network, not running on SoftEther server.

I have no problems with clients using WinXP, Win7, or Win8, only some Win10 users.

Hello there!, have you tried to re-install SE-Clients ?. Also, since the users are authenticated correctly, set their virtual adapters IP settings to static IP addresses, then test using "ping" or something like that, just to try to find out where is the root cause of the problem ?


Thanks.

raafat wrote:
> Hello there!, have you tried to re-install SE-Clients ?. Also, since the
> users are authenticated correctly, set their virtual adapters IP settings
> to static IP addresses, then test using "ping" or something like
> that, just to try to find out where is the root cause of the problem ?
>
>
> Thanks.
Yes, I did try re-installing the SE client, but that didn't help.

I did set a static IP and then the VPN worked. I know that the issue is between DHCP and Windows 10. Until yesterday I believed I had the issue narrowed down to one specific Win10 update build (14393.rs1_release.160715-1616), however yesterday I was working on a users new home laptop with Win10 build 10240.th1.160906-1755 and I was encountering the same problem. I see the DHCP request, but the vpn client never gets an IP address.

But when you connect a Win7 client to the same hub of the same server, you get a DHCP response, right ?

VPNuser2016 wrote:
> thisjun wrote:
> > Are there DHCP request and response logs in packet log?
>
> There are requests, but no responses. DHCP server is on the network, not running on
> SoftEther server.
>
> I have no problems with clients using WinXP, Win7, or Win8, only some Win10 users.

Kindly, may explain more about your sentence "DHCP server on the network, not running on softEther server" ?, Also, it's better if you provide us more details about your topology regarding SE server

hi, it happened to me too, i'm sure it's because of the new upgrade of windows 10 that we received

For me disable and enable vpn adaptor fixed the issue but I had to do that everytime I want to use softether vpn