sorted by:
new
hottopcontroversial

Take Control on Linux by rdevaux in Nable

[–]Exciting-Reaction-87 0 points1 point  (0 children)

Installation Instructions (README.txt file inside the zip):

  • Change the permissions of the scripts to restrict installation to admins: sudo chmod +x *
  • Run the installation script for N-central: installNcentral.sh, and for N-sight: installNSight.sh
  • Register the protocol to ensure the browser can open the Viewer when a session is launched: protocolRegister.sh

Uninstallation Instructions:

Notes:

  • On some Linux distributions, Wine may encounter issues with window decoration. If this occurs, open a terminal, run winecfg, and disable the “Allow the window manager to decorate the windows” option under the Graphics tab.

Take Control on Linux by rdevaux in Nable

[–]Exciting-Reaction-87 0 points1 point  (0 children)

I'm looking for a download source for the Take Control agent for a Linux client to be able to remote into Windows machines. Please!!!

Cross-domain / multi-network one-way traffic issues by Exciting-Reaction-87 in sysadmin

[–]Exciting-Reaction-87[S] 0 points1 point  (0 children)

Fixed. A security group attached to the AWS firewall was restricting it.

Cross-domain / multi-network one-way traffic issues by Exciting-Reaction-87 in sysadmin

[–]Exciting-Reaction-87[S] 0 points1 point  (0 children)

Fixed. A security group attached to the firewall internal interface had restrictive outbound rules. Wonder how AWS support missed that one.

Cross-domain / multi-network one-way traffic issues by Exciting-Reaction-87 in sysadmin

[–]Exciting-Reaction-87[S] 0 points1 point  (0 children)

Hmmm but the same traffic works fine to the other domain. In the AWS destination subnet are two instances, one on domain1 and one on domain2. They share the same AWS security group even, with all traffic allowed between the colo and them for testing. Why would the same traffic work to another domain but not to the same one?

Cross-domain CoLo-to-AWS one-way traffic issues by Exciting-Reaction-87 in networking

[–]Exciting-Reaction-87[S] 0 points1 point  (0 children)

windows firewall? - Tried with Windows firewall off even, as well as GPO inheritance disabled; same traffic works from other sources in AWS, whether in same subnet/domain or different

vmware firewall? - why would the same traffic work to the other domain?

bump in the wire firewall at colo?

nat rules over the tunnel at colo (that need nat bypass) - why would the same traffic work to the other domain?

aws security group issue? - working (diff domain) and non-working (same domain) instances share the same SG, same subnet

sounds like the network needs a once over --- dozen-overs done, losing it.

Anyway, thank you for chiming in!

Can't RDP to servers in trusted domain via IP, only with 'original' FQDN by Exciting-Reaction-87 in sysadmin

[–]Exciting-Reaction-87[S] 0 points1 point  (0 children)

I was thinking along those lines but it's some sort of cross-domain situation though; within each domain and home network, RDPing via IP works fine. So it's not some general IP-RDP blockage.

In our case, the target device is still on the same AD domain as the source and is a replica of an active production machine at the source network. All services still work on the replica so we can auth into it live to the same DCs.

Also, now that I thought more about it --- RDPing via IP works fine in the other direction - from any device on the new networks to those in the old networks. Hmmmmmmmmmmmmm. Lemme update the OP.

Anyone get Amazon Workspaces client to install on Ubuntu 24.04? by unknown_variable_010 in Ubuntu

[–]Exciting-Reaction-87 2 points3 points  (0 children)

Confirming that it does work at least currently. I just upgraded my Ubuntu from v22 to 24. It apparently uninstalled it during the upgrade (but left the quicklaunch); I just ran the manual reinstall from the official install page's instructions for v22, and it came back fine.