Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
Customer was using L2tp over IPSec for RA. For Windows 7 users, customer was using Secoclinet and configured different l2tp groups with peer tunnel names, each with a separate IP pool.
For the Windows 10 users, we could not use the V1 Secoclient, which was not compatible, and we had to use the build-in client. Windows client don`t support tunnel name, so for all users, we need to use the default-lns group.
Still, we need to do a separation between the different customers.
We can implement the customer requirement in the following way. We create separate authentication domains for the users that need to receive IP from different pools.
1) We create two domains, default and test and add a different IP pool for each of them. Don`t forget to click ,,apply"
2) Check which Virtual-Template is used for the default-lns group and undo the remote service-scheme by command, like below:
3)Then we can do a test and connect to two users form the two domains used. We can see that they are receiving different IPs from different pools, even if they connect to the same default-lns group.