Table of contents
Combined revision comparison
...
Users are refused access if the password doesn't match when they attempt to connect to VPN. Users can change the password registered in VPN Server themselves at any time using VPN Client. For details see #4.9.1#.4.9 Other Functions.
...
The server product name that the SoftEther VPN Server notifies the RADIUS server of is "SoftEther VPN Server 2.0".
...
NT domain and Active Directory authentication are methods whereby user name and password are authenticated, just like with password authentication, but passwords are managed by NT domain controller of a Windows NT 4.0 Server or later or an Active Directory controller of Windows Sever 2000 Sever or Server 2003 rather than SoftEther VPN Server. This enables user authentication using the existing company password database. If company employees change their passwords on the Windows domain, it also applies to the password for SoftEther VPN connection, thereby enabling password unification.
...
Windows domain by Windows Server NT 4.0 / 2000 Server / Server 2003 is already widely used. Thus companies and Internet service providers that have Windows domain based authentication service can conduct user authentication by NT domain controller or Active Directory controller.
...
| In order to conduct NT domain or Active Directory authentication, the SoftEther VPN Server to conduct user authentication must be capable of running on Windows NT , with |
...
Version from 03:36, 2 Mar 2013
...
Users are refused access if the password doesn't match when they attempt to connect to VPN. Users can change the password registered in VPN Server themselves at any time using VPN Client. For details see #4.9.1#.
...
The server product name that the SoftEther VPN Server notifies the RADIUS server of is "SoftEther VPN Server 2.0".
...
NT domain and Active Directory authentication are methods whereby user name and password are authenticated, just like with password authentication, but passwords are managed by NT domain controller of a Windows NT 4.0 Server or later or an Active Directory controller of Windows 2000 Sever or Server 2003 rather than SoftEther VPN Server. This enables user authentication using the existing company password database. If company employees change their passwords on the Windows domain, it also applies to the password for SoftEther VPN connection, thereby enabling password unification.
...
Windows domain by Windows NT 4.0 / 2000 Server / Server 2003 is already widely used. Thus companies and Internet service providers that have Windows domain based authentication service can conduct user authentication by NT domain controller or Active Directory controller.
...
| In order to conduct NT domain or Active Directory authentication, the SoftEther VPN Server to conduct user authentication must be capable of running on Windows NT |
...
Version as of 02:26, 3 Mar 2013
...
Users are refused access if the password doesn't match when they attempt to connect to VPN. Users can change the password registered in VPN Server themselves at any time using VPN Client. For details see 4.9 Other Functions.
...
| In order to conduct NT domain or Active Directory authentication, the SoftEther VPN Server to conduct user authentication must be capable of running on Windows NT, with capable of participating in domain. SoftEther VPN Servers that run on Windows 98, Windows 98 Second Edition, Windows Millennium Edition or Linux, FreeBSD, Solaris or Macintosh OS X cannot conduct NT domain or Active Directory authentication. Authentication of users set for NT domain or Active Directory authentication always fails. |
...
