You are browsing the archive for 2018 October.

Azure: Unable to connect to VMs in a peered VNet from P2S VPN

8:50 am in Azure, Azure Networking, Azure virtual network, P2S client, P2S VPN, RDP, VNet peering by Wim Matthyssen

These days when setting up a greenfield Azure IaaS environment for customers, we use the hub-spoke network topology with shared services. In this topology the HUB network is used as central point of connectivity and a place to host services that can be consumed by the different workloads hosted in the spoke VNets. All spokes are peered with this Hub network, to isolate all workloads. Whenever I work remotely on these environments, I mostly use a Point-to-Site (P2S) connection to securely connect to the different VNets from my client devices.

However last week while deploying a new environment for a customer, I stumbled upon a problem where I couldn’t RDP (private IP addresses) to the virtual machines (VMs) in the different spokes. The RDP access to the VM’s in the Hub VNet worked without any issues.


This is caused, because by design the P2S client will have routes listed for all VMs in the HUB VNet (which hosts the Virtual Network Gateway). However, even though the HUB VNet and the other VNets are connecting via peering, the P2S client will not have any routes presented in its configuration to discover the VMs in the other VNets. In order for the P2S client to be able to reach all VMs (trough for example RDP) located in the peered VNets, a static route for these VNets should be added in the routes.txt file of that specific connection. You can follow the steps below to get this working.


Open Run, type %appdata% and press Enter.


Open Microsoft – Network – Connections – Cm and select the right connection folder. Next, open the routes.txt file in Notepad (to open just double-click).



You can also find the correct path to the routes.txt file in the P2S VPN log file. You can open this file by opening your P2S connection and selecting on Properties instead of Connect. In the opened Properties page select View Log. Search for ActionPath, which will show you the location of the file.



End of remark.

In the opened routes.txt file, add the static routes for the other VNets.

For example:

ADD MASK default METRIC default IF default

ADD MASK default METRIC default IF default

ADD MASK default METRIC default IF default


Save the file, and connect again. You should now be able to RDP to all other VMs in the spoke VNets.

Hope this helps and for any questions feel free to contact me through my Twitter handle.

Wim Matthyssen (@wmathyssen)

Microsoft Ignite 2018 recap

9:26 am in Microsoft Ignite, Microsoft Ignite 2018, Orlando, Windows, Windows 10, Windows Admin Center by Wim Matthyssen

Last week I visited the Microsoft Ignite 2018 conference in Orlando with some colleagues. 10,000 km of walking later and sitting back her at home thinking about the past exciting week. I tought it’s a good time to write a recap, quietly hoping the writing will help battling jet lag. :)


After a long flight and a stopover at Dulles International Airport in Washington it was really nice that we could pick up our badge directly at the airport which spared us the morning line before the start of the event. I planned almost all my sessions I wanted to follow before the event and the MS Events app really came in handy to check my schedule, get event notifications, messages and to fill in all evaluations. The navigation function in the app also came in really handy telling me how to get from one session to another. You should know that the venue of Ignite was the OCCC, a huge complex on International Drive in Orlando, combining two conference centers and the Hyatt Regency connected together by a Skybridge.


The thing I was really happy about was that I wore comfortable shoes and clothes, because I did a lot of walking, really a lot of walking. I would advise if you’re ever planning to go to Ignite wear shoes were you can at least walk 10 km a day in, otherwise do not do Ignite in them! Orlando itself is a beautiful city, with a lot of theme parks like Universal Studios Florida and Universal’s Islands of Adventure, which hosted the Ignite Celebration on Thursday evening. If you ever have the chance to go there, the Wizarding World of Harry Potter is truly magical.


It was my first time at Ignite and my main focus was to learn as much as possible and get note of all announcements and changes around Azure, and I must say I got lots of that. Next to all Azure related sessions, I also followed a few of them around Windows Admin Center and Windows 10. For the most part, the quality of all sessions I followed was excellent only the rooms were sometimes a bit cold due to the airco.


Below you can find some announcements, I gathered during the technical breakout and theater room sessions I followed:

  • Microsoft partners with Adobe and SAP for new Open Data Initiative.
  • Microsoft Teams Screen Sharing which allows you to screenshare in Teams without needing to escalate to a meeting first.
  • SQL Server 2019 preview announced.
  • Windows Server 2019 general availability (GA) in October, together with Windows Server version 1809.
  • Azure Firewall a stateful firewall as a service GA.
  • Windows Virtual Desktop a virtual desktop experience which lets you run Windows 10 in the cloud, available in Preview.
  • Announcement of Microsoft Learn, a new learning platform to optimise your Microsoft skills.
  • Azure SQL Database Managed Instance a new deployment model of Azure SQL Database GA.
  • Azure Blueprints in Preview, which let you define user access, policies and resources in Azure.
  • Azure Management Groups available to organise and governance all your resources between all your subscriptions.
  • Azure Resource Graph GA which allow you to easily query, explore and analyse all your Azure cloud resources at scale.
  • Azure Migrate now also supports Hyper-V.
  • Azure Monitor now includes Log Analytics and Application Insights for collecting and analysing telemetry of your cloud and on-premises resources and applications.
  • There will be 2 models of the Surface Hub 2, the Surface Hub2S coming Q2 2019 and theSurface Hub 2X coming in 2020.
  • Azure Data box, Microsoft’s heavy-duty data transfer appliance is now GA.
  • Announcement of Azure Sphere, a Linux-based operating system created by Microsoft for Internet of Things applications.

If you’re interested in getting an overview of all announcements Microsoft did at Ignite, be sure to check out this Book of News.

Session Overview

Below you can find a few sessions I followed in person and I recommend to take a look at (click the link to get to the YouTube video):

I had a lot of sessions planned in my schedule that I did not manage to attend but I will take time to watch the recordings and slides. Like every year you can catch up the session recordings that are available on YouTube or the Microsoft Tech Community, but if you’re interested you can also download all Ignite content locally with the following PowerShell script from MVP Michel de Rooij (@mderooij):


For everyone who could not attend Ignite in person and still want to get the chance to follow some sessions live and explore the latest cloud technologies, Microsoft has announced, Microsoft Ignite | The Tour. which takes place in a lot of cities all around the world. You can check out the schedule over here:

I want to end this blog post with saying that Microsoft Ignite rocked! It doesn’t matter if you’re an ITPro or DevOps, if you ever have the change to go there, you shouldn’t hesitate because it’s really a great and fantastic experience. In my opinion, there’s not much that Microsoft can do to improve Ignite, everything was handled like it should for such hugh event and the content was great and will keep my busy absorbing in the next few weeks. Hope to be back again in Orlando in November next year