Hp CIFS Server and Terminal Server Manuel d'utilisateur

HP CIFS Server and Terminal ServerVersion 1.06 October, 2007SNSL Advanced Technology CenterE0300Printed in: U.S.A.©Copyright 2007 Hewlett-Packard Comp

10Chapter 5 Terminal Server WorkaroundsThere is no easy way to generate a new TCP/IP connection for every Terminal Server client that connects to a ba

11Prior to Samba version 3.0.2, the Samba code data structure for “netbios aliases =” was 1024 bytes long. Therefore, the total number of aliases tha

125.1.2 Terminal Server Hosts File Aliases The Windows Terminal Server can be configured with a hosts file that is similar in function to theUNIX/Linu

13Managing synchronization between the user logon and the Samba share alias could occur via numerous methods in a consolidated fashion on the Terminal

14Filtering the WINS display for the Samba server emonster IP address shows the static mapping table for the users that looks similar to the hosts fil

155.3 Home Share ConfigurationSamba allows for considerable customization of user home share definitions. At least one method of home share configurat

16The Terminal Server sees the service name as \\EMONSTER\HOME-SHARE, and not \\emonster\buffy. If the user spike opens a session on the same Termina

17Using the [homes] share definition, Terminal Server sees the service name as \\EMONSTER\BUFFY. File access and file locking tasks perform correctly

18When using the Samba “netbios aliases =” workaround or the Terminal Services hosts file for Samba aliases, the MAX_CONNECTIONS issue does not occur

19Chapter 6 SummaryThe default behavior of Terminal Server on Windows is to multiplex all user connections to individual machines (Samba file and prin

2Legal NoticesThe information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this

3ContentsLegal Notices...2Chapter 1 Int

4Chapter 1 IntroductionMany organizations host file server and print server services on HP CIFS Server and Samba open source servers, usually running

5Chapter 2 Samba and Terminal Server IntegrationThe fundamental Samba design is to manage each client connection to the server with a discrete user pr

6Naturally, the expectation of Terminal Server is that the six remote client connections and subsequent share mounts to the Samba server will result i

7Chapter 3 Samba with TS on Windows NT4/2000/2003Terminal Server on Windows NT4, 2000, and 2003 is configurable to allow the underlying Windows operat

8behavior provides the system resources per client connection that Samba was designed for, and thus Samba performance for Terminal Server connections

9Chapter 4 Without the HotfixIf the Windows Terminal Server is not configurable with the hotfixes listed in Chapter 3, the resulting Terminal Server f