chris forrest (All user's messages)


Search  Rules 
Forgot your password?
Select date in calendarSelect date in calendar

Pages: 1
Disabling remote access if local user logged in?
Paul B wrote:
Eugene Idzikovsky wrote:
Probably feature of limiting connections amount won't be implemented.
I think it would be a good idea to implement this. It's up to the people administering the server to decide whether reducing the number of concurrent users to 1 is acceptable (for example on the basis that log on locally is available). You could also enforce a inactive session timeout after so many minutes _if_ the number of concurrent users is set to 1. So after say, 15 minutes of inactivity Radmiin Server drops the connection and Locks or Logs Off the server.

It's just a question of additional flexibility. The more flexible the product is the more people will buy it. No-one would be forced to set a connection limit of one would they - it's a decision individual users would have to take responsibility for.

And maybe this also ties in with other discussions about protecting Radmin settings to stop _any_ user with a full connection changing the settings - the idea of another permissions level like "Radmin Admin :)" who _is_ allowed to change settings.

Paul is right here. This is a feature we'd like to ensure that servers with the most sensitive and critical information aren't being worked on at the same time. You don't have to limit it by default but since this app only does console level access, it would help to give the users some ability to limit how many concurrent connections there are to whichever console at a certain time.
Disabling remote access if local user logged in?
Paul B wrote:
You have the choice in the Radmin Server settings of auto allow or auto deny after the prescribed time is up.

Right, but what happens if it is set to auto deny and nobody is around the machine to accept?

Next, where can I set the number of concurrent Radmin connections to 1?
Disabling remote access if local user logged in?
That was kind of what I wa
Paul B wrote:
As an afterthought, as far as local logons go there are probably a few workarounds you could employ. For example you could have policy-driven logon/logoff script which turn the Radmin Server service off/on respectively. This would stop Radmin access while a user was logged on and restore that capability when they logged off.

That wouldn't solve all of your problems by any means, but it may help to form one part of a workable solution.

That's kind of where I was headed with my question.

Another one:

With the option to have the locally logged in user click a prompt to accept an incoming connection turned on, what happens if nobody is logged into the machine to accept the incoming connection?
Disabling remote access if local user logged in?

I'm interested in finding out if Radmin can be set up to disallow incoming connections if a user is already logged into the machine, or if a connection can be disallowed if the connection isn't coming from a user who is currently logged in locally.

This question came up because of the availability to sensitive data to prying eyes.

Edited: chris forrest - 17.04.2009 13:26:34
Pages: 1

Radmin 3.5

Windows 10 Compatible


Free for 30 days


Only $49 per lifetime license
for  50 PCs - $29.8 per remote PC
for 100 PCs - $24.9 per remote PC
for 150 PCs - $23.3 per remote PC
from 200 PCs - $22 per remote PC
Follow us on Twitter
Famatech Corporation Copyright © 1999-2016 Famatech. All rights reserved.