VPN server has four nics. Nic 1 has an address and has access to internet, Nics 2,3 & 4 do not have addresses and face three different lan segments each with their own DHCP/DNS server and router.
Three Hubs were created and different users were assigned to each Hub using standard password authentication.
These three hubs had local bridges to NICs 2,3,4
Users on HUB1/Local Bridge1 can log in using SoftEther Client from the internet and get an address from external DHCP server and connect to devices on the bridged segment
Users defined on HUB2/Local Bridge2, HUB3/Local Bridge3 & HUB4/Local Bridge4 cannot log in using any client, error looks like a password error but even pasting in the username and password still causes login failure
Running the latest stable version of SoftEther VPN server on Linux and Windows Client
Is this a configuration issue?
We believe you can bridge multiple segments with Hubs/Local Bridges and Dedicated NICS.
Cannot Login to bridged hub
-
- Posts: 137
- Joined: Mon Mar 24, 2014 3:59 am
Re: Cannot Login to bridged hub
User accounts in the non-default hub must send an @ symbol in the username field. For example:
alice@HUB2
bob@HUB2
charlie@HUB3
Authentication failures are logged. Check whether users in HUB2 or HUB3 are mentioned in the security_log/HUB1/* files.
alice@HUB2
bob@HUB2
charlie@HUB3
Authentication failures are logged. Check whether users in HUB2 or HUB3 are mentioned in the security_log/HUB1/* files.
-
- Posts: 5
- Joined: Tue Nov 18, 2014 5:24 pm
Re: Cannot Login to bridged hub
dajhorn wrote:
> User accounts in the non-default hub must send an @ symbol in the username
> field. For example:
>
> alice@HUB2
> bob@HUB2
> charlie@HUB3
>
> Authentication failures are logged. Check whether users in HUB2 or HUB3
> are mentioned in the security_log/HUB1/* files.
Thanks for the answer.
The security_log/HUB1/ files didn't show anything.
When trying to create user accounts with the @ symbol, the "OK" button is greyed out and new users cannot be created..
> User accounts in the non-default hub must send an @ symbol in the username
> field. For example:
>
> alice@HUB2
> bob@HUB2
> charlie@HUB3
>
> Authentication failures are logged. Check whether users in HUB2 or HUB3
> are mentioned in the security_log/HUB1/* files.
Thanks for the answer.
The security_log/HUB1/ files didn't show anything.
When trying to create user accounts with the @ symbol, the "OK" button is greyed out and new users cannot be created..
-
- Posts: 5
- Joined: Tue Nov 18, 2014 5:24 pm
Re: Cannot Login to bridged hub
Here are observations with multiple hubs and multiple users
This was tested using the SoftEther VPN Client
create users on each hub,
users can all have the same name (i.e. vpnuser) since they are on different hubs.
Do not use "@" when creating the vpnuser name, if you do you will not be able to save the username
Log in with SoftEther VPN Client using your user name, your virtual hub name and password.
So far success with the SoftEther VPN client.
If using Linux, you can watch the server log by going into the vpnserver/server_log directory and running the following command "tail -f vpn_yyyyddmm.log"
When using the Microsoft client, use the format "vpnuser@hubname" and password
Also success with the Microsoft client.
This was tested using the SoftEther VPN Client
create users on each hub,
users can all have the same name (i.e. vpnuser) since they are on different hubs.
Do not use "@" when creating the vpnuser name, if you do you will not be able to save the username
Log in with SoftEther VPN Client using your user name, your virtual hub name and password.
So far success with the SoftEther VPN client.
If using Linux, you can watch the server log by going into the vpnserver/server_log directory and running the following command "tail -f vpn_yyyyddmm.log"
When using the Microsoft client, use the format "vpnuser@hubname" and password
Also success with the Microsoft client.