Not able to connect to remote when on a remote network

from Stardock Forums

Hi,

I just downloded a trial of the KVM Pro to check i this was to solve my needs for controlling a omputer remotely.

Evertying works just fine when I am on the same subnet.
I then test to connect the same remote computer to mobile router.
Now KVM Pro is not able to connect.

- I have no public IP
- The newtwork is set as Private
- I have, for test purposes, disabled the firewall completely

Any clues?
I spawned thru the FAQ but did not find any posts on this.

My hope was to use KVM Pro similarly as Teamviewer or Google Remote Desktop allowing to connect anywhere.

How can I make this happen with KVM Pro?

BR

/Niklas

multiplicity
5,304 views 9 replies
Reply #1 from Stardock Forums Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from Stardock Forums Top

Hello,
I have forwarded your problem/question again to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #4 from Stardock Forums Top

Evertying works just fine when I am on the same subnet.
I then test to connect the same remote computer to mobile router.
Now KVM Pro is not able to connect.
End of quote

My hope was to use KVM Pro similarly as Teamviewer or Google Remote Desktop allowing to connect anywhere.
End of quote

While this is being explored for future versions, this is not possible without a central server to manage the connections across disparate isolated networks.

The best way around this currently is to have each point connected to the same VPN, thus putting them on a shared subnet.

Hope this helps.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #5 from Stardock Forums Top

Thanks Sean. Good clarification. Hope to see that functionality in future versions.
I love the things Stardock does. Keep up!

/Niklas

 

 

Reply #6 from Stardock Forums Top


Hi,

I just downloded a trial of the KVM Pro to check i this was to solve my needs for controlling a omputer remotely.

Evertying works just fine when I am on the same subnet.
I then test to connect the same remote computer to mobile router.
Now KVM Pro is not able to connect.

- I have no public IP
- The newtwork is set as Private
- I have, for test purposes, disabled the firewall completely

Any clues?
I spawned thru the FAQ but did not find any posts on this.

My hope was to use KVM Pro similarly as Teamviewer or Google Remote Desktop allowing to connect anywhere.

How can I make this happen with KVM Pro?

BR

/Niklas
End of quote

 

Did you solve that finally?

Reply #7 from Stardock Forums Top

Quoting OllyBe, reply 6


Quoting ,
quoting post

Hi,

I just downloded a trial of the KVM Pro to check i this was to solve my needs for controlling a omputer remotely.

Evertying works just fine when I am on the same subnet.
I then test to connect the same remote computer to mobile router.
Now KVM Pro is not able to connect.

- I have no public IP
- The newtwork is set as Private
- I have, for test purposes, disabled the firewall completely

Any clues?
I spawned thru the FAQ but did not find any posts on this.

My hope was to use KVM Pro similarly as Teamviewer or Google Remote Desktop allowing to connect anywhere.

How can I make this happen with KVM Pro?

BR

/Niklas


Did you solve that finally?

End of OllyBe's quote

Its not 'broken' so its not really a 'solve' type issue.  The OP is asking for a feature addition.  What I recommended, employing a VPN on both sides, is the current best work-around.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #8 from Stardock Forums Top
Quoting sdrohan, reply 7

Its not 'broken' so its not really a 'solve' type issue.  The OP is asking for a feature addition.  What I recommended, employing a VPN on both sides, is the current best work-around.

Sean Drohan
Stardock Product Lifecycle Manager

End of sdrohan's quote

Hi,

thanks for doing a great job!

With the arrival of Multiplicity 4, is it now possible to connect and control computers outside the same subnet?
See original post and description above.

/Niklas

Reply #9 from Stardock Forums Top

Quoting niklas8, reply 8


Quoting sdrohan,
reply 7


Its not 'broken' so its not really a 'solve' type issue.  The OP is asking for a feature addition.  What I recommended, employing a VPN on both sides, is the current best work-around.

Sean Drohan
Stardock Product Lifecycle Manager

Hi,

thanks for doing a great job!

With the arrival of Multiplicity 4, is it now possible to connect and control computers outside the same subnet?
See original post and description above.

/Niklas

End of niklas8's quote

Hmmm, that is not a feature of Multiplicity 4 but if you have utilized the workaround, great.

Sean Drohan
Stardock Product Lifecycle Manager