Hello Michal. Many thanks for your prompt response. Could you outline briefly how you went about setting up the server? the documentation isn't really clear enough and it gets a bit confusing when you're trying to get your head around the server component, then you've got the options of either being a client machine or a controled machine in both client and server dialogues. also, could you outline how you're getting the server on the main machine to run on startup so the others can connect to it? when you say beeping every few seconds, do the clients try to connect constantly? i'm really sorry for all the questions and really appreciate any help you can provide. all the best, Mo. On 03/07/2015 23:30, Michał Dziwisz wrote:

hi, You can setup your own server from the plugin. The main disadvantage of that method is if you have for example 5 machines with nvda auto connecting to that server, you must when you wish control other machine restart nvda, setup server again and set other key. I am controling few servers with win 2003 and 2008, and workstations of my customers The main problem is when you have few machines with differend keys trying connect to your server, machines with wrong key are beeping in few seconds period.

Right. so to clarify, if you've entered the key for example your name, do the customers then have to use the connect to server option on startup to connect to your server initially? how then do you connect to their machines? i'd assume that their machine has a separate key specified in the client options? i'm just trying to get my head around the hole process from start to finish, specifying multiple keys etc. what I ultimately want to be able to do is have the server running all the time on my main machine, then with as little user input as possible, for me to be able to connect to them for example using their first name as specified by me on their version of NVDA. once again i really appreciate your help and can't thank you enough. all the best, Mo. On 03/07/2015 23:42, Michał Dziwisz wrote:

Hi, Go to nvda, tools, remote, connect and select server and from group of radio buttons "control another machine". Type the key and remember about forwarding 6837 tcp port. My customers aren't connected all the time. When they are in trouble they know, that they should click the nvda icon from the desktop and call me or submit a ticket and provide the name of their computer.

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

hello. many thanks, It certainly seems to make more sense now. I will play around and post results to the list. many thanks once again for all your help. all the best, Mo. On 04/07/2015 01:43, Michał Dziwisz wrote:

Hi, every user has a an unique key, in our company every workstation has an unique name for inventory purposes so the name is a key. For distributing I created 7zip sfx archive running portable copy of nvda, you can follow these instructions: http://ntsblog.homedev.com.au/index.php/2015/05/14/self-extracting-archive-r...

ofcourse instead setup.exe is nvda.exe. So, scenario is as follows: 1: user is downloading a binary package 2: She / he runs that package 3: User calls me and i do the rest.

Main disadvantage of that is when you have blind users using nvda, because I am not able to run portable nvda when installed nvda is running. But, because I have 100% sighted customers its no problem at this time, perhaps somebody will have a better solution?

hth.