I have 30 users on a Terminal Server Windows 2008 R2.
Users have to access a folder shared on remote server, for example \\SERVER1\Documents
At the beginning the users are able to access the remote share but after some variable time the share desappears and it is impossible to contact the remote share until I restart the Terminal Server.
I know that Terminal Server relies on the underlying Windows operating system to establish the transport for the client pool, and Windows will only issue ONE TCP/IP connection to the remote server – this results in all virtual client sessions
and share mounts being multiplexed over a single TCP/IP transport pipe to the remote server (SERVER1)
On a `Windows Server 2008 R2 RDS Server` I'm trying to maintain a separate `TCP` virtual circuit per EACH user - this for allow separate connections to the remote \\SERVER1\Documents share per each user.
On old Windows server, you can allow each terminal server client to maintain a separate virtual circuit using `regedt32`, navigate to: `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters` and adding a value named `MultipleUsersOnConnection`
as a type `REG_DWORD` entry and setting the data value to 0.
I'm not able to find the same registry setting for Windows Server 2008 R2 with Remote Desktop Services rolde installed.
How I can maintain a separate TCP virtual circuit per each user to access the remote share instead the only one that transports multiple virtual circuits ?
In older Windows server the registry keys was named also MultiUserEnabled or EnableMultiUser or MultipleUsersOnConnection ... I think ...
Thank you in advance,
Ivano Carrara
Ivano Carrara