Bug Report
Posted: Sun Feb 25, 2018 6:03 am
Hi guys,
Not sure if there is a dedicated section for bug reports or not, but I have found a pretty annoying bug and it took me a while to finally get to the bottom of it...
So let's say you've set up your SoftEther VPN server on a work machine. On this work machine, you've got a Hyper-V virtual NIC set up. Your SoftEther VPN server is set up using a bridge connection, where it uses the virtual NIC for the connection. On the client side, you connect to your VPN server and try to open a file from the work LAN via SMB, e.g. \\contoso.com\document.docx, it takes ages to load and doesn't open. You can still ping machines on your work network, but opening files will fail. Turns out that when you are using a bridge connection, you can only use physical NICs. You can't use a virtual NIC connection.
Not sure if there is a dedicated section for bug reports or not, but I have found a pretty annoying bug and it took me a while to finally get to the bottom of it...
So let's say you've set up your SoftEther VPN server on a work machine. On this work machine, you've got a Hyper-V virtual NIC set up. Your SoftEther VPN server is set up using a bridge connection, where it uses the virtual NIC for the connection. On the client side, you connect to your VPN server and try to open a file from the work LAN via SMB, e.g. \\contoso.com\document.docx, it takes ages to load and doesn't open. You can still ping machines on your work network, but opening files will fail. Turns out that when you are using a bridge connection, you can only use physical NICs. You can't use a virtual NIC connection.