HP CIFS Server and Terminal Server - Manual (Page 19)

19
Chapter 6 Summary
The default behavior of Terminal Server on Windows is to multiplex all user connections to
individual machines (Samba file and print servers) over a single TCP/IP connection, which
potentially results in multiple Terminal Server user sessions being serviced by one Samba smbd
process. The function of the TCP connection establishment behavior is an operating system
limitation, and not due to Terminal Server itself. Therefore, other applications (like Citrix
Metaframe) will encounter the same behavior when connecting to a Samba server.
At this time, Windows Server NT4, 2000, and 2003 all provide Terminal Server hotfixes that allow
Samba client connections to initiate separate TCP connections, which allow Samba to start a
discrete smbd process for every Terminal Server client connection.
In cases where the hotfixes may not be deployable, the configuration flexibility and versatility of
Samba can compensate for the Terminal Server on Windows default behavior, and thus provide
fast and reliable file and print services. Also, many environments run Terminal Server and Samba
with no modifications at all, with perfectly acceptable performance. A representative test
environment and test suite is recommended for vetting new Terminal Server and Samba
configurations using the workarounds, or the default behavior.