There is no server-side parameter that blocks remote desktop resizing.
There is a parameter in /etc/turbovncserver-security.conf
(max-desktop-size) that prevents the remote desktop from exceeding a
certain size, but that parameter applies to all sessions, so it wouldn't
explain why one session is resizable and another isn't. If you were
using the Windows native viewer, which stores viewer options separately
for each connection, then the behavior you're describing might make
sense if User A's session was using a different display number than User
B's session (meaning that the viewer might be recalling a different set
of options for each), but the Java viewer doesn't do that. The Java
viewer loads the same set of global options each time it is launched,
and if you modify the options and save them, those new options will be
used for all subsequent connections. Unfortunately, I have no clue what
might be causing the behavior you describe. Here are some things to
check, however:
(1) Verify whether the viewer options are the same between the failing
and successful connections (that is, actually open the Options dialog in
the viewer after connecting to the server session, and verify that
"Remote desktop size" is "Auto". The viewer *should* be using the same
options for both, but perhaps it isn't for some reason.
(2) Run xrandr in both sessions and verify that it produces reasonable
output. This will tell us whether both sessions have a working RANDR
extension.
(3) Try to resize the desktop using xrandr, e.g. "xrandr -s 1024x768".
That will tell us whether it is only remote desktop resizing that is
broken or whether the failing session can't be resized at all.
(4) Check the log of the failing session and see if there are any error
messages related to a failed attempt by the server to resize the desktop.