Forum Replies Created
-
Posts
-
I think you missed my point about the similarities to browser really only end at how proxy would work. Browser general use case is not intranet or used behind secured networks, while NoMachine is.
And to be fair, I dislike the browser proxy configuration. It’s why I install plugins like SwitchyOmega which behind the scenes just uses auto proxy config because users should not have to deal with.
In my opinion, I think the concept of “manage and edit tens of session files” is a problem no one had. Yes, in the prior system, rather than 1 config for same settings, people had 3 for each network they are on, but “manage” really ends at the creation of these session files. I enjoy the ability to just connect to a session without having to make changes beforehand. Depending on where you are, you connect from a different session file. If there’s a concern for how this might balloon for roles like IT, there are other ways to organize configurations like session folder structuring. There’s also an inherent assumption that system proxy settings would be adequate, that is hardly how proxies are commonly being used. Many resources behind secured networks are not in the same network as where the client is connecting from. A NoMachine client on a single network may require 4 different proxies to access 4 different hosts, potentially concurrently. The current set up makes that difficult and require auto proxy configurations.
The analogy should not be made to browsers but should be to something like SSH given it’s an authentication method your product uses. Putty is one I use and it does not require me to mess configurations when I move because I would have variations of the session depending on where I am.
@Britgirl, I really don’t know how global proxy solves the problem of 5 individual files. It would make more (not all) sense if you can create global proxy profiles that you can toggle between. Because between the 5 nxs files and and having to change between 5 different proxies manually in global settings, I’d pick the 5 nxs files. Copying how browsers work should not be a priority given that the number of private networks you are connecting to via NoMachine is going to greater than private networks in a browser. Most people using a browser will likely never touch proxy settings. NoMachines behind proxies is done for security.
Automatic configuration is a good workaround, but this is not always available. And while it can be generated, this is IMO a step backwards from the UI option for per config setting.
I’m just curious why it was removed when a global and per config can co-exist where specificity overrides the general one. Was there a technical reason why it was removed?