@kaystrobach@Ubiquiti Yes, finally it is port forwarding. But you don't need a VPN. You can establish a #ButConnect session in a #TeamViewer-like way: on invitation or unattended. Then, the webui (or any other protocol as needed) will be forwarded without exposing parts of the network to the Internet.
@kaystrobach Wouldn't _that_ be broken by design?
BTW: It's easy to access devices (directly - not by #ScreenSharing) that don't run #RemoteAccess software by themselves with #ButConnect.
(... although not from mobile, yet.)
(No QNAP NAS available here for testing, though.)
@WillnDad1 Well - the part for establishing connections is a command line tool and hence considered "less beautiful" than a GUI.
But that's the way it is at the moment and it allows to be platform independent in a simple way.
We would like to improve that situation, but it's not there yet.
While #ButConnect's user interface is not particularly nice, it's still easy to use:
The 'client' just presses [RETURN] once.
And the 'agent' presses [A], [RETURN] and then enters the credentials provided by the client.
That's it. No installation, no registration, not even a GUI.
@mjimlay @RustyJorgensen@Capp00@theurparanoid That's exactly what we created #ButConnect for:
You can use RDP (or other protocols) without exposing it to the internet in a #TeamViewer-like(*) way: 'client' creates the session and shares credentials, 'agent' can connect.
(* ... without all the bells and whistles, of course ;)
#SysAdmins and #DevOps should consider trying #ButConnect.
It provides access to all kinds of servers on a remote network w/o having to "hop" over #TeamViewer connections.
It runs on #Windows, #macOS and #Linux and can also be configured for unattended access.
Take a look at it.
If you use #TeamViewer to access a computer for the purpose of actually reaching a 3rd one, you have to establish an additional session that thereby occupies the 1st.
This is not necessary with #ButConnect. You can reach hosts on the remote net directly.
https://t.co/rxlk5ZOEXN
Another type of #RemoteAccess solution: #ButConnect
- cross-platform #Windows#Linux#macOS#BSD
- CLI
- provides access to many protocols, not only #RemoteDesktop
- no registration, no installation (except #mono)
- instant or unattended access
- free for private and business use
#ButConnect isn't just a #RemoteAccess tool but also a "remote network access" solution.
It's possible to reach all kinds of remote hosts that don't need to run the utility themselves without having to go over multiple intermediate hops or nested sessions.
https://t.co/hkfTj1xRUt
#ButConnect is not limited to #RemoteSupport via #RemoteDesktop (#RDP#VNC).
It allows access to virtually any host or service in a remote network, like web interfaces, command lines, remote consoles, database servers ...
And you can connect spontaneously!
https://t.co/YocIlkSEP7
A while ago we created our own replacement for other #RemoteAccess or #RemoteSupport tools or for working from home ...
... and now we would like to share our solution.
No need for any other #RemoteDesktop software anymore.
(BTW: #ButConnect is #free for private or business use.)
#Unattended#RemoteAccess with #ButConnect works with #SSH keys (that can be further protected with passphrases).
Therefore, it's not that easy to take over a remote computer unauthorised. At least it is not enough to find out an ID/password combination.
https://t.co/jxqSrHsR7i
@FatalPuls3 @scottybones@TeamViewer Again, you don't have to open any ports or adjust firewall rules at all.
That's what #ButConnect is there for.
After beeing connected, you can use any tool as you like.
(#VNC, #RDP, ... so - more abilities.)
@TeamViewer_help@CreepyXL@TeamViewer For those, #TeamViewer isn't the best solution anyway.
Rather use #RDP (but do NOT expose it to the internet!
Here, #ButConnect comes into play: You can connect in different scenarios: spontaneously with the help of a coworker or unattended.
Then use the link for #RemoteDesktop.)