>I've got a user (10.3) who is having some specific trouble.
>I've verified that she doesn't have this issue if she goes to a PC
>and accesses the same system there.
The default settings in tn3270 add some features which can be useful,
but which result in a deviation from strict 3270 emulation. You can
try disabling those features and see if that makes any difference.
To do that, select Features... under the Session menu, and change the
first three items and the last item from Yes to No.
>This is bound to be something simple, but I just don't know where to start.
>Strangely, I'm using Brown 3.1.1 on her box and on mine for testing
>and I don't seem to have the same problem.
Might you be using different settings for your sessions? If you have
a settings file that works on your machine, you could try that
settings file on her machine.
Do you know whether her keyboard is never unlocked, or it just takes
a long time? If she had a poor network connection, with a
significant number of lost packets, it could take a couple minutes
for the unlock to be received, due to how TCP/IP handles packet
retransmission when many packets are being lost.