VPN Setup Problem on Windows 10 Pro
Hi Masters! I wanted to configure the VPN profile with VPN Credentials Helper via the Powershell, but the rasdial it says the following error on Windows 10 Pro 22H2: Remote Access error 703 - The connection needs information from you, but the application does not allow user interaction. I noticed the following: If I create a new IPSEC VPN connection with an empty username and password, the rasdial command displays an error when running. But if I create the IPSEC VPN connection with a (test) username and (123456) password and then delete the username (empty) and password (empty), everything works fine, rasdial connected. I am attaching the picture: Is this a bug? Why doesn't it work the first time? Thank you! Regards: DrCyberg
Always on VPN prompting for action needed - Azure AD Join issue?
Hello! We have Always on VPN implemented for our Windows 10 laptops. Everything was/is working great, until we purchased Microsoft 365. Once devices started to Azure AD Join, it put in an additional user certificate from MS-Organization-Access. Now, anytime a user logs in, instead of automatically connecting as they expect, you will have to go to the VPN connection and you will see "Action Needed." Once you click connect, it brings up a dropdown to select which certificate to use, the options being the one created for AoVPN (email address as the name) and the other being the one created by the azure ad join. Selecting and connecting the proper certificate does not persist between logins. Is there a way to specify which certificate it needs to be pointing at to avoid this issue?
Integrated VPN client: Add option for group name shared secret / group password
I have to use Cisco AnyConnect for some work-related VPNs because this option is not supported. Another report, not by me: https://social.technet.microsoft.com/Forums/ie/en-US/ccbfedbd-ace8-40c7-ad5f-68184ac10feb/windows-10-vpn-add-group-name-secret-passwordHow to set my VPN connection as Non-metered in Windows 10?
I want to explicitly tell Windows 10 1909 to consider my VPN connection as non-metered. whenever I connect to my VPN server, created from the Windows settings, apps like Mail stop showing me notifications, Store won't automatically update apps and things like that. Windows by default thinks my VPN connection is set as metered. I went to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost but there is no mention of my VPN connection's name I manually set them all to "1" which means Non-metered. can anyone help me set my VPN connection as Non-metered so Windows 10 can use Internet as much as it wants just like when I connect to Internet without VPN? Thanks More info on this: this is how advanced settings for WiFi looks like in Windows settings And this is how advanced settings for VPN looks like in Windows settings You see the part about "Metered Connection" is missing from VPN settings! Another thing I tried was disabling SlowLinkDetection in Registry, setting it to 0: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System\SlowLinkDetectEnabled It didn't help. I test it simply but sending an Email to myself on phone and watch for the notification banner on Windows 10. when I'm connected directly to WIFI, the notification banner appears as soon as the mail is arrived but when I'm connected to VPN, the notification banner only appears when I manually open the Mail app in Windows 10 (UWP). I use PPTP/SSTP protocols, set them up in Windows 10 settings natively.
Windows 10 VPN and SQL with Meraki VPN
Hi, when our users connect to VPN (Windows 10 VPN on Meraki) they used to be able to access a client application on a SQL server host (a Windows 10 host)....but something recently happened on the host (uninstalled Norton security and it likely reset a bunch of stuff) and now client VPN users are no longer able to access that application....we can ping the SQL host from the client device after connecting to VPN but no longer access the application, so my guess its some Windows firewall port or protocol on the SQL server blocking the traffic when it sees the traffic coming in via VPN because it works fine within the network, and its not as permission issue as I put the same client device on the network and it can access the application without any issues. Any thoughts or ideas?
Networking issues since January 23 (approximately)
Hi everyone, I'd like to start by clarifying that the issue I have is happening on Insider builds (one PC in SLow, one in Fast), and I'm not sure if that has anything to do with it. Here's the thing: Last week, on Thursday (I think), both of my laptops started indicating that my home Wi-Fi connection wasn't connected to the internet, despite my phone and other devices saying otherwise. What's more, despite the error, both my laptops could browse the web (using the new Edge) or check for updates. However, UWP apps like Unigram, OneNote, and To Do didn't work. I only actively use one laptop, so there are no settings I could have changed on both, and since they're on different versions of Windows 10, and neither got an update prior to the issue, so it was completely out of the blue. After running the network troubleshooter, resetting my router and modem, and updating drivers, nothing seemed to work. Eventually, though, my main lapto seemed to sort itself out on its own, and my secondary laptop, while it took a little longer, also stopped showing the error. However, I have now noticed that VPN apps based on UWP, like TouchVPN and the Store version of Avira Phantom VPN, always fail to connect, and that happens on both laptops. There are no limits I've reached, and the apps work on my phone. Likewise, the classic desktop app for Avira still works fine with Phantom VPN. Put short, it seems like there's something about UWP apps that's not working quite as it should. Though most apps are fine now, VPN apps based on UWP aren't working. I have no clue why, but I hope someone can help. Thanks in advance!W10 Pro - Problems with multiple server IPs and mapped network drive
I have a file server fileserver1 with two IPs, a LAN IP 192.168.100.100 and a VPN IP 192.168.200.200. The Windows 10 Pro client uses the DNS name fileserver1.company.corp to get the correct IP depending on its own network (LAN or VPN). DNS name resolution works without problems. The client has a persistent network drive K: \\fileserver1.company.corp. Unfortunately the Windows 10 Pro client always seems to use the cached server IP (192.168.100.100 or 192.168.200.200) to reconnect the network drive on startup. Some users want to wakeup the Windows PC from powersave mode. If the client uses the cached IP from the other location (LAN vs. VPN), access to this drive fails. How can I update the network drive IP? Currently I use two workarounds. On most PCs it is enough to delete network drives (net use K: /delete) and then connect the network drive again with the DNS name (net use K: \\fileserver1.company.corp /persistent:yes) Some PCs need a reboot between deletion of network drive and connection
