Hi all,

 

  My question is regarding the NVDA remote access.Last week I install the NVDA remote on my work computer to be able to access from home and it works fine with one exception.

  My work computer goes to the lock screen after some enactivity time and to continue I need to press ctrl+alt+del and enter my username and password.

  So, the remote access works very well while the work computer is unlocked, as soon as lock screen is kicks in, the remote speech stops, my local NVDA still shows as “connected”, however even choosing “press ctrl+alt+delete” from NVDA remote access menu does not do anything, I am not able to unlock my work PC remotely.

  Looks like, it is some kind of limitation of NVDA remote access. I wonder, if development is still going on? After more then a year, I still see the version is 1.2. And my second question, may be someone knows the work around, how I can dismiss this lock screen remotely?

  Forgot to mention, I am running windows 7 both, remotely and locally, if it makes any difference. I was also looking for some third_party solution, however did not find anything.

 

Will greatly appreciate, if someone could please help!

 

Many thanks.

 

  Igor.

 

On your work computer, did you copy your NVDA user profile after installing the remote access add-on using the ‘Use currently saved settings on log-on and other secure screens’ button on the preferences/general page of the NVDA menu?               

Cheers

Chris

Hi Chris,

I believe, I did, however will verify tomorrow. Thanks for the suggestion! The local NVDA works fine on the locked screen, only remote NVDA has problems.

All the best!

    Igor

On your work computer, did you copy your NVDA user profile after installing the remote access add-on using the ‘Use currently saved settings on log-on and other secure screens’ button on the preferences/general page of the NVDA menu?               

Cheers

Chris

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with auto-connect
set for your user NVDA settings and copy this set-up to the secure screen
settings, your work computer will drop its remote connection when the
secure screen appears but immediately re-establish it when the secure
screen NVDA settings are loaded. Similarly, when you log into your work
computer, the remote connection will drop again and reconnect when your
user NVDA settings are loaded. Your local computer shows as being
connected but this only indicates that it is connected to the host server,
not your work computer.

Cheers

Chris

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with
auto-connect set for your user NVDA settings and copy this set-up to
the secure screen settings, your work computer will drop its remote
connection when the secure screen appears but immediately re-establish
it when the secure screen NVDA settings are loaded. Similarly, when
you log into your work computer, the remote connection will drop again
and reconnect when your user NVDA settings are loaded. Your local
computer shows as being connected but this only indicates that it is
connected to the host server, not your work computer.

Cheers

Chris

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with
auto-connect set for your user NVDA settings and copy this set-up to
the secure screen settings, your work computer will drop its remote
connection when the secure screen appears but immediately re-establish
it when the secure screen NVDA settings are loaded. Similarly, when
you log into your work computer, the remote connection will drop again
and reconnect when your user NVDA settings are loaded. Your local
computer shows as being connected but this only indicates that it is
connected to the host server, not your work computer.

Cheers

Chris

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with
auto-connect set for your user NVDA settings and copy this set-up to
the secure screen settings, your work computer will drop its remote
connection when the secure screen appears but immediately re-establish
it when the secure screen NVDA settings are loaded. Similarly, when
you log into your work computer, the remote connection will drop again
and reconnect when your user NVDA settings are loaded. Your local
computer shows as being connected but this only indicates that it is
connected to the host server, not your work computer.

Cheers

Chris

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with
auto-connect set for your user NVDA settings and copy this set-up to
the secure screen settings, your work computer will drop its remote
connection when the secure screen appears but immediately re-establish
it when the secure screen NVDA settings are loaded. Similarly, when
you log into your work computer, the remote connection will drop again
and reconnect when your user NVDA settings are loaded. Your local
computer shows as being connected but this only indicates that it is
connected to the host server, not your work computer.

Cheers

Chris

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with
auto-connect set for your user NVDA settings and copy this set-up to
the secure screen settings, your work computer will drop its remote
connection when the secure screen appears but immediately re-establish
it when the secure screen NVDA settings are loaded. Similarly, when
you log into your work computer, the remote connection will drop again
and reconnect when your user NVDA settings are loaded. Your local
computer shows as being connected but this only indicates that it is
connected to the host server, not your work computer.

Cheers

Chris

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with
auto-connect set for your user NVDA settings and copy this set-up to
the secure screen settings, your work computer will drop its remote
connection when the secure screen appears but immediately re-establish
it when the secure screen NVDA settings are loaded. Similarly, when
you log into your work computer, the remote connection will drop again
and reconnect when your user NVDA settings are loaded. Your local
computer shows as being connected but this only indicates that it is
connected to the host server, not your work computer.

Cheers

Chris

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with
auto-connect set for your user NVDA settings and copy this set-up to
the secure screen settings, your work computer will drop its remote
connection when the secure screen appears but immediately re-establish
it when the secure screen NVDA settings are loaded. Similarly, when
you log into your work computer, the remote connection will drop again
and reconnect when your user NVDA settings are loaded. Your local
computer shows as being connected but this only indicates that it is
connected to the host server, not your work computer.

Cheers

Chris

Hi Chris,

Thanks so much for researching this issue. Well, if it works on your side,
then it is something in my configuration.
To clear all douts, the autoconnect:
Nvda menu (insert+N), tools, remote access, options autoconnect on startup
need to be check providing the host name and access key.
As I mentioned, I see, nvda reconnects after the remote computer goes to
the lock screen, the connect menu under remote access is unavailable and
disconnect menu is available to break the connection.
I am running my own NVDA remote server on home laptop and connecting to
it.

I'll investigate more and will look at NVDA log.

Thanks a lot.

-Igor

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Mullins
Sent: Tuesday, September 27, 2016 1:02 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA remote access.

Igor
On my last post, please ignore "1. The W10 machine did not output any speech
locally but I can hear everything at the remote end. unlike when I connect
to my friends machine which speaks locally and I can hear everything at the
remote end". I hadn't realised I had a headphone extension wire plugged
into the machine which muted the sound.

I have now done a test logging out and into an account over a remote
connection and it works perfectly. I first had to re-copy my settings over
to the system settings having first set the autoconnect parameters. Just to
be sure we are on the same page, could you describe your understanding of
'autoconnect parameters'?

Cheers
Chris

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Mullins
Sent: 27 September 2016 17:12
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

Hi Igor
If you set logging to 'Info', you can see where remote connections occur.
However, I've tried to replicate your set-up and run some tests. To
simulate your work machine, I have used a windows 10 machine with nvda
2016.3 installed and have set remote to autoconnect. To simulate your home
machine, I have used an old XP laptop with nvda2014.4 installed and used
the remote dialog to manually connect it as the controlling computer to my
Windows 10 machine. It gave the long sound when I connected to the already
logged-in account on the W10 machine. I could access the W10 machine
perfectly and successfully locked the screen and logged back in again,
maintaining the remote connection.

I regularly connect to a friend's machine but we use the remote dialog to
specify the host and key parameters butthis is the first time I've used
autoconnect and I noticed a couple of differences between the connection
methods.
1. The W10 machine did not output any speech locally but I can hear
everything at the remote end. unlike when I connect to my friends machine
which speaks locally and I can hear everything at the remote end.
2. When I lock the screen, I don't hear the descending chime of nvda exit or
the ascending chime of NVDA load when I unlock my account with the log-in
password. logging in/out of an account I suspect behaves differently and I
will test this behaviour next.

With the behavior in 2 above in mind, could you leve your work machine on
the lock screen rather than the log-in screen to enable remote access or are
there group policies in effect which would prevent you doing this?

Cheers
Chris

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Igor
Kaplan
Sent: 27 September 2016 10:55
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

Yes, I do, and it shows "connected" on the lock screen.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Mullins
Sent: Tuesday, September 27, 2016 5:44 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

And you definitely have autoconnect enabled?

Cheers
Chris

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Igor
Kaplan
Sent: 26 September 2016 23:46
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

Well, verified today, my configs are definitely used on the security screens
and after the security screen is on the status of remote access plugin is
"connected", however no access at all.
However, if I go to the Remote Access menu, disconnect and then connect
again, right on the lock screen, it works perfectly. It continue to work
after the computer is unlocked, however again stops after the computer is
locked. So, looks like the NVDA attempts to reconnect on the security
screen, I even hear the long beep, the indication of connection, however
there is probably something, which does not let NVDA to connect properly.
I wonder, if connections attempts are recorded to the NVDA log, I could
probably attempt to debug sometime.

All the best.

Igor.
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Mullins
Sent: Monday, September 26, 2016 5:55 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

Go to the NVDA menu Preferences/General, there is a button labelled 'Use
current settings on log-on and other secure screens' to copy them over. You
will require admin priviledges to perform this routine.

Cheers
Chris

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Antony
Stone
Sent: 25 September 2016 23:59
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

How does one "copy this set-up to the secure screen settings"?

Antony.

On Monday 26 September 2016 at 00:50:58, Chris Mullins wrote:

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with
auto-connect set for your user NVDA settings and copy this set-up to
the secure screen settings, your work computer will drop its remote
connection when the secure screen appears but immediately re-establish
it when the secure screen NVDA settings are loaded. Similarly, when
you log into your work computer, the remote connection will drop again
and reconnect when your user NVDA settings are loaded. Your local
computer shows as being connected but this only indicates that it is
connected to the host server, not your work computer.

Cheers

Chris

--
Schrödinger's rule of data: the condition of any backup is unknown until a
restore is attempted.

Please reply to the list;
please *don't* CC
me.

Hi Chris,

Thanks so much for researching this issue. Well, if it works on your

then it is something in my configuration.
To clear all douts, the autoconnect:
Nvda menu (insert+N), tools, remote access, options autoconnect on startup
need to be check providing the host name and access key.
As I mentioned, I see, nvda reconnects after the remote computer goes to
the lock screen, the connect menu under remote access is unavailable and
disconnect menu is available to break the connection.
I am running my own NVDA remote server on home laptop and connecting to
it.

I'll investigate more and will look at NVDA log.

Thanks a lot.

-Igor

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Mullins
Sent: Tuesday, September 27, 2016 1:02 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA remote access.

Igor
On my last post, please ignore "1. The W10 machine did not output any

locally but I can hear everything at the remote end. unlike when I connect
to my friends machine which speaks locally and I can hear everything at

remote end". I hadn't realised I had a headphone extension wire plugged
into the machine which muted the sound.

I have now done a test logging out and into an account over a remote
connection and it works perfectly. I first had to re-copy my settings

to the system settings having first set the autoconnect parameters. Just

be sure we are on the same page, could you describe your understanding of
'autoconnect parameters'?

Cheers
Chris

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Mullins
Sent: 27 September 2016 17:12
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

Hi Igor
If you set logging to 'Info', you can see where remote connections occur.
However, I've tried to replicate your set-up and run some tests. To
simulate your work machine, I have used a windows 10 machine with nvda
2016.3 installed and have set remote to autoconnect. To simulate your

machine, I have used an old XP laptop with nvda2014.4 installed and used
the remote dialog to manually connect it as the controlling computer to my
Windows 10 machine. It gave the long sound when I connected to the already
logged-in account on the W10 machine. I could access the W10 machine
perfectly and successfully locked the screen and logged back in again,
maintaining the remote connection.

I regularly connect to a friend's machine but we use the remote dialog to
specify the host and key parameters butthis is the first time I've used
autoconnect and I noticed a couple of differences between the connection
methods.
1. The W10 machine did not output any speech locally but I can hear
everything at the remote end. unlike when I connect to my friends machine
which speaks locally and I can hear everything at the remote end.
2. When I lock the screen, I don't hear the descending chime of nvda exit

the ascending chime of NVDA load when I unlock my account with the log-in
password. logging in/out of an account I suspect behaves differently and

will test this behaviour next.

With the behavior in 2 above in mind, could you leve your work machine on
the lock screen rather than the log-in screen to enable remote access or

there group policies in effect which would prevent you doing this?

Cheers
Chris

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Igor
Kaplan
Sent: 27 September 2016 10:55
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

Yes, I do, and it shows "connected" on the lock screen.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Mullins
Sent: Tuesday, September 27, 2016 5:44 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

And you definitely have autoconnect enabled?

Cheers
Chris

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Igor
Kaplan
Sent: 26 September 2016 23:46
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

Well, verified today, my configs are definitely used on the security

and after the security screen is on the status of remote access plugin is
"connected", however no access at all.
However, if I go to the Remote Access menu, disconnect and then connect
again, right on the lock screen, it works perfectly. It continue to work
after the computer is unlocked, however again stops after the computer is
locked. So, looks like the NVDA attempts to reconnect on the security
screen, I even hear the long beep, the indication of connection, however
there is probably something, which does not let NVDA to connect properly.
I wonder, if connections attempts are recorded to the NVDA log, I could
probably attempt to debug sometime.

All the best.

Igor.
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Mullins
Sent: Monday, September 26, 2016 5:55 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

Go to the NVDA menu Preferences/General, there is a button labelled 'Use
current settings on log-on and other secure screens' to copy them over.

will require admin priviledges to perform this routine.

Cheers
Chris

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Antony
Stone
Sent: 25 September 2016 23:59
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote access.

How does one "copy this set-up to the secure screen settings"?

Antony.

On Monday 26 September 2016 at 00:50:58, Chris Mullins wrote:

The way I understand it is that when your work computer drops into the
secure screen it drops your user NVDA settings and loads the secure
screen NVDA settings. So if you have the remote add-on with
auto-connect set for your user NVDA settings and copy this set-up to
the secure screen settings, your work computer will drop its remote
connection when the secure screen appears but immediately re-establish
it when the secure screen NVDA settings are loaded. Similarly, when
you log into your work computer, the remote connection will drop again
and reconnect when your user NVDA settings are loaded. Your local
computer shows as being connected but this only indicates that it is
connected to the host server, not your work computer.

Cheers

Chris

--
Schrödinger's rule of data: the condition of any backup is unknown until a
restore is attempted.

Please reply to the

please *don't* CC
me.