anser316 wrote:

We do want them to connect somewhere, but no where else, just one connection.

Well, that's the same.

any help with this please?

martin wrote:

anser316 wrote:

Yes please, we only want them to log on to one File Protocol and hostname, and be restricted to not connect to anything else.

No you cannot prevent WinSCP from connecting somewhere.

We do want them to connect somewhere, but no where else, just one connection.
Can the resource hacker tool do this?

anser316 wrote:

Yes please, we only want them to log on to one File Protocol and hostname, and be restricted to not connect to anything else.

No you cannot prevent WinSCP from connecting somewhere.

how about hide .ini file ?

Yes please, we only want them to log on to one File Protocol and hostname, and be restricted to not connect to anything else.

What is your goal?
Do you want to prevent the users from connecting anywhere else?

any idea anyone?

I can set File Protocol and Hostname for session by using the ini file.
Is there anyway the login can be locked down so they can not edit the site/session details?
Setting the ini file to read-only permission does stop changes to be saved, but a user can still edit the site config and login without saving.