No Internet connection! on starting Remotely

[LinuxAndCoffee]

Hey there,

I cannot figure out what I have done incorrectly in trying to set up Remotely. I was able to install Remotely on a Windows 7 (x64) desktop with no problem, at least as far as I can tell. But when I open Remotely, on the top bar of the window it says No Internet connection!. I know the computer has an Internet connection because I am using FireFox on that desktop to send this message. I've tried checking everything I can think of, and the only thing I can come up with is that Remotely cannot get through my ISP's router and firewall because the port it wants is not open. I can open any ports I need to, so if that is all it is, please let me know what they are.

But if there is something else I should try, I am happy to do so. Thanks in advance for any help, advice, etc.


- Michael

 

[mirillis]

Hi Michael,

This looks like the "missing TLS1.2 Windows 7" problem.
Firefox works because it uses OpenSSL. Remotly uses built-in Microsoft Secure Channel.
Please check this link on how to enable TLS1.2 in Windows 7:

Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows - Microsoft Support

Describes an update that adds TLS 1.1 and TLS 1.2 to default security protocols in Windows Server 2012, Windows 7 SP1, and Windows Server 2008 R2 SP1.

support.microsoft.com

You can also type this search query in Google:
"tls1.2 windows 7 enable"

AI will show a step by step tutorial how to enable TLS1.2 like this:

To enable TLS 1.2 on Windows 7, you can either update your system with the appropriate Windows update (KB3140245), which is the most recommended method, or manually edit the registry to create the necessary keys and settings. The registry method involves navigating to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols, creating new keys for TLS 1.2, Client, and Server, and adding Enabled and DisabledByDefault DWORD values.

Method 1: Install the Windows Update

• The most straightforward method is to download and install the KB3140245 update from Microsoft. This update enables TLS 1.1 and 1.2 support and makes necessary registry changes for you.
• After installation, restart your computer to apply the changes.
  

Method 2: Manually edit the registry

• Press Windows Key + R, type regedit, and press Enter to open the Registry Editor.
  
  
• Navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols.
  
  
• Right-click on the Protocols folder, select New > Key, and name it TLS 1.2.
  
  
• Right-click on the new TLS 1.2 folder, select New > Key, and name it Client.
  
  
• Right-click on the Client folder, select New > DWORD (32-bit) Value, and name it DisabledByDefault.
  
  
• Double-click DisabledByDefault, ensure the Value data is 0, and click OK.
  
  
• Right-click on the Client folder again, select New > DWORD (32-bit) Value, and name it Enabled.
  
  
• Double-click Enabled, ensure the Value data is 1 (to enable), and click OK.
  
  
• (Optional) Repeat the Client key creation for Server and repeat the process to create the TLS 1.1 protocol as well.
  
  
• Restart your computer for the changes to take effect

 

[LinuxAndCoffee]

Hey mirillis,

Thanks for the quick and detailed reply! I followed what you posted, and it turns out that I actually had that update already installed (totally by accident, I swear, lol). But to be safe, I checked the registry to make sure the changes were how they needed to be, and those were also already correct. I am wondering if something just went screwy during the installation (maybe I didn't see an error or something?), so I may try an uninstall, restart, and then reinstall of Remotely tomorrow when I get to my office (where the computer in question is).

This just seems so weird to me. I was a Windows user for many, many years, and even supported Windows computer labs in a previous lifetime. And I can't remember a time I ever saw something quite like this. I was almost wondering if I had somehow got a virus, but why a virus would target just one application like Remotely, especially because it is not usable in its current state. I really appreciate your assistance so far, and if you happen to think of anything else, please let me know.

Now that I know it is probably connected to TLS, I can narrow down my hunting for solutions. Thanks again, and I will post back when/if I figure this out in case anyone else runs across it again.


- Michael

 

[mirillis]

One thing is for sure. Remotly works on Windows 7 with all features just like on newer systems. We are always testing Windows 7 before releasing a new update just to make sure there is no regress.

One more thing came to my mind. Maybe there is a firewall blocking Remotly from accessing internet?
In the previous post there was something about the icon on the caption bar that says there is no internet.
And this is actually not related to TLS (the icon just shows if there is a network card/interface that has internet access present in the system).

Can you check Settings->Network:

Maybe you have more than one network interface?