Hello! I have heard that there is a problem with using Samba along with Windows Terminal Services and that it's related to session IDs with multiple users coming from one server. I'm in the process of moving to Windows Server 2003 using Citrix and hoping to be able to revive our samba use. Has anyone had any success with using samba in a Terminal Server / Citrix environment? Thanks in advance for any information! Brad
Hi Brad, As it seems that nobody answered your quiry yet, here you have some feedback... We have used Samba with both windows-NT and Terminal servers(Citrix) for over a year now. It works just fine :-) Concerning the Terminal servers and Samba we have only been bothered with the following 2 problems: - we had to increase the constant MAX_CONNECTIONS in smbd/conn.c since the total number of drives being mapped from the Terminal server was higher than 128(default). We chose 1024 instead which gave us a reasonable margin. - originally we used %U and %G to point to the users login path and for our PDF generator. However, we had to give up using these "variables", since the user and group IDs were cached somewhere, resulting in user and group mixups on the Samba server. Even though it is a late answer(I subscribe to the digest version of the mailinglist), I hope you can use it. Regards, Hans.> Message: 38 > Date: Fri, 16 May 2003 14:59:02 -0400 > From: "Portelance, Brad" <Brad.Portelance@state.vt.us> > Subject: [Samba] Samba & Terminal Services / Citrix > To: "'samba@lists.samba.org'" <samba@lists.samba.org> > Message-ID: <2339EC5645409F45A896B1E764F0CF5702D5E42E@SOV_EXCHANGE5> > Content-Type: text/plain > > Hello! > > I have heard that there is a problem with using Samba along > with Windows > Terminal Services and that it's related to session IDs with > multiple users > coming from one server. > > I'm in the process of moving to Windows Server 2003 using > Citrix and hoping > to be able to revive our samba use. > > Has anyone had any success with using samba in a Terminal > Server / Citrix > environment? > > Thanks in advance for any information! > > Brad
Hi Brad, We use SAMBA here with our Windows 2000 Terminal Servers quite successfully. You are correct about the problems with the session id problem. What happens is that by default whenever any user from the same terminal server connects to the same SAMBA server they go through the same smb process. Thus, the more user's connecting from the terminal server, the worse your file access performance can get. In the Windows NT 4 version of Terminal Server Microsoft added a registry option which works around this problem. The registry entry is : [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters] "MultipleUsersOnConnection"=dword:00000000 (Note this should be listed in the SAMBA documentation) However, under the Windows 2000 version of TS, MS took out this registry value. The work around we have used here to give each user their own smb process is we created a local alias in the hosts file, on the Terminal Server, for the SAMBA server. For the alias we used the user id's of the user's access the machine. For example assume you have SAMBA server called samba1 with a share called myshare. Now if you have a user on a TS with the user id smitjoh who wants to connect to the share what we would do is the TS hosts file we would add an entry to the file that aliases the IP address for the server samba1 to be also known as smitjoh. Then when the user connects they would connect to the share as \\smitjoh\myshare <\\smitjoh\myshare> instead of \\samba1\myshare <\\samba1\myshare> . (Note : the one catch with this is that the user id alias is not visible in the browse list when you map network drives, however for the folder path can enter \\<userid <\\<userid> > and then click on the browse button and it will show you the server with the user id alias). Another option for this is you could try using the SAMBA netbios aliases smb.conf option to create the SAMBA server aliases. Hope this helps. ===========Message: 38 Date: Fri, 16 May 2003 14:59:02 -0400 From: "Portelance, Brad" <Brad.Portelance@state.vt.us> Subject: [Samba] Samba & Terminal Services / Citrix To: "'samba@lists.samba.org'" <samba@lists.samba.org> Message-ID: <2339EC5645409F45A896B1E764F0CF5702D5E42E@SOV_EXCHANGE5> Content-Type: text/plain Hello! I have heard that there is a problem with using Samba along with Windows Terminal Services and that it's related to session IDs with multiple users coming from one server. I'm in the process of moving to Windows Server 2003 using Citrix and hoping to be able to revive our samba use. Has anyone had any success with using samba in a Terminal Server / Citrix environment? Thanks in advance for any information! Brad
Hello Brad and Drew, We us Samba here with Windows 2000 Terminal Server and Citrix. Shares and printers are served from a Solaris 2.5.1 box running Samba 2.0.7 in "security=domain" mode and an NT4 PDC. We will upgrade when I can grab the time to make and thouroughly test one of the latest releases. We haven't been bitten by this problem, I assume, because we have very few users (usually 10-20) per server. Sorry I can help with this particular problem, but it is good see others using similar Samba setup. Troy Johnson --- Troy Johnson - troy.johnson@health.state.mn.us Programmer / System Administrator Minnesota Cancer Surveillance System - MDH>>> <Drew.Zeller@statcan.ca> 06/03/03 09:51AM >>>Hi Brad, We use SAMBA here with our Windows 2000 Terminal Servers quite successfully. You are correct about the problems with the session id problem. What happens is that by default whenever any user from the same terminal server connects to the same SAMBA server they go through the same smb process. Thus, the more user's connecting from the terminal server, the worse your file access performance can get. In the Windows NT 4 version of Terminal Server Microsoft added a registry option which works around this problem. The registry entry is : [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters] "MultipleUsersOnConnection"=dword:00000000 (Note this should be listed in the SAMBA documentation) However, under the Windows 2000 version of TS, MS took out this registry value. The work around we have used here to give each user their own smb process is we created a local alias in the hosts file, on the Terminal Server, for the SAMBA server. For the alias we used the user id's of the user's access the machine. For example assume you have SAMBA server called samba1 with a share called myshare. Now if you have a user on a TS with the user id smitjoh who wants to connect to the share what we would do is the TS hosts file we would add an entry to the file that aliases the IP address for the server samba1 to be also known as smitjoh. Then when the user connects they would connect to the share as \\smitjoh\myshare <\\smitjoh\myshare> instead of \\samba1\myshare <\\samba1\myshare> . (Note : the one catch with this is that the user id alias is not visible in the browse list when you map network drives, however for the folder path can enter \\<userid <\\<userid> > and then click on the browse button and it will show you the server with the user id alias). Another option for this is you could try using the SAMBA netbios aliases smb.conf option to create the SAMBA server aliases. Hope this helps. ===========Message: 38 Date: Fri, 16 May 2003 14:59:02 -0400 From: "Portelance, Brad" <Brad.Portelance@state.vt.us> Subject: [Samba] Samba & Terminal Services / Citrix To: "'samba@lists.samba.org'" <samba@lists.samba.org> Message-ID: <2339EC5645409F45A896B1E764F0CF5702D5E42E@SOV_EXCHANGE5> Content-Type: text/plain Hello! I have heard that there is a problem with using Samba along with Windows Terminal Services and that it's related to session IDs with multiple users coming from one server. I'm in the process of moving to Windows Server 2003 using Citrix and hoping to be able to revive our samba use. Has anyone had any success with using samba in a Terminal Server / Citrix environment? Thanks in advance for any information! Brad -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
DOELKER,RAINER (HP-Germany,ex2)
2003-Jun-23 12:51 UTC
[Samba] Samba & Terminal Services / Citrix
Hi Brad and Drew, one statement to the thread of yours in the samba-list: yes, terminal-server on NT had the switch to make the terminal use one virtual connect for each terminal-server-client. windows 2000 does not have the registry entry any more. so what happens is you might face the situation that you cannot connect all shares: [2003/03/10 10:38:35, 1] smbd/conn.c:(102) ERROR! Out of connection structures [2003/03/10 10:38:35, 0] smbd/service.c:(340) Couldn't find free connection. This is a fix value in the sources smbd/conn.c: #define MAX_CONNECTIONS 128 so if you have 40 terminal clients connecting 4 samba-shares (= 160 connections on one smbd) that would not match. Change the value to e.g. 256 and recompile your samba. Note: if you have to many connections to one smbd it might affect the performance. There is suggestion to make this a smb.conf configurable (max connections per client) but thats not yet accepted. hope that helps Kind regards. Rainer Doelker -------------------------------------------- Rainer D?lker Linux-Unix-Competency-Center Hewlett Packard