Skip to main content

How to open a RDP connection to a device that doesn't has direct access to internet using Azure Service Bus Relay

By
In one of the previous post I presented a mechanism that can be used as tunneling solution for Remote Screen Sharing using Azure Service Bus Relay.

But what is happening when you need to establish a Remote Screen Sharing session with a machine that is in a private network without direct access to internet.
For this case we would need a mechanism to forward the packages from the central machine, which has access to the internet to the other machine. In theory this could be done very simple, but in practice this could be done pretty hard, because forwarding packages to another machine is not a simple task.
On top of this, it would be great if we could do this without having a custom application on the target machine.

One solution is to use Service Bus Relay and Port Bridge application as presented in the previews link. A custom application will need to be installed only on:
  • The client machine (that is used to access the remote machine)
  • The central machine (that has access to internet from private network)
The interesting part is locations where the port bridge application needs to be installed. The application needs to be installed only on the Central Machin on he client side Nothing stop us to redirect the packages from this machine to another machine from private network. If we have the machine IP or name (and port) for screen sharing that it will be very simple to do this redirect.
The current application presented in the previous post allow us to specify the target host and port. Using this configuration we can specify directly the target device:

<add targetHost="DeviceIP" allowedPorts="3389" />

This simple solution in combination with Service Bus Relay can allow us to be able to access machines without direct access to internet in a very simple and easy way.
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

Azure AD and AWS Cognito side-by-side

By
In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more