Problems with Windows IKEv2 Client after SecuExtender retirement / Windows net drive mapping
Master Member
Since Zyxel intends to retire the SSL VPN SecuExtender Client, we're presently trying to change to the Windows build-in IPSec IKEv2 client.
All necessary steps at our USG Flex 700 are done and we are able to establish a VPN connection. From remote we are able to ping the DC, could resolve the domain name, could reach third party software in our on-premise environment through the tunnel, etc.
Only one thing is weird. We are not able to automatically map any network drives. It doesn't work with "net use" nor with GPO, where the GPUpdate is carried out after the tunnel has been established.
It seems for us, that the Windows Client is always taking the VPN login credentials also for trying to reconnect to the network drives. But the network drives will always be mapped with user's domain credentials which are different from VPN login credentials. Could anybody confirm this behaviour? We do not like to use the same login credentials for both the Windows Domain login and the VPN login. Does anybody knows a solution?
Categories
- All Categories
- 415 Beta Program
- 2.5K Nebula
- 156 Nebula Ideas
- 106 Nebula Status and Incidents
- 5.9K Security
- 321 USG FLEX H Series
- 286 Security Ideas
- 1.5K Switch
- 78 Switch Ideas
- 1.2K Wireless
- 42 Wireless Ideas
- 6.6K Consumer Product
- 257 Service & License
- 399 News and Release
- 86 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.8K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 87 About Community
- 78 Security Highlight
