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

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.


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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

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 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.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…