similar to: MultipleUsersOnConnection, WTSE

On NT4 terminal server it is possible to change a registry setting to make it create one connection to samba per user .... I know there has been a lot of discussion around this but I can't find a definative answer in any of the posts: How do you do this with 2000? The fact that it only runs one smb process is causing serious problems on my samba server. Anybody? Andre -------------- next

I'm sending this as an FYI since we don't have all the details worked out and this isn't a Samba problem. We have seen problems (on the one system we tried it on) with MultipleUsersOnConnection registry entry for Windows 2000 Terminal servers that was mentioned in http://lists.samba.org/archive/samba/2004-April/084427.html It may only happen with users who map through Microsoft

Hi. I am running SAMBA 2.0.7 on HP-UX 11.00 and HP-UX 10.20. I have tried adding the MultipleUsersOnConnection registry key onto my Microsoft Windows NT Server 4 Terminal Server Edition servers, running with Service Pack 6. After I make this change in the registry and reboot my WTS servers all my samba connections from the servers are still being made with one process instead of being split

Hi, Back in 1997 the list was full of tips on making Microsoft Visual C++ Studio (v6) use files over Samba (v2.2.2 on Solaris). Could someone please point me to the definitive answers... (beyond speed.txt?) and their current status. We have an added complication of having 5 developers using each NT4 box over citrix/Terminalserver. Some days we are fine, but some days we slow to a crawl of over a

Hello Everybody, I hope everybody is doing well and that you can help me out as I am approaching my wit's end. I am running a Citrix server on a Windows 2000 SP 3 server. One of my published applications on this server needs to access samba for multiple users. So basically every user who logs on to the Citrix server needs to have access to their home directory on our Unix server.

On Samba 1.9.18p10 and previous versions, each of the multiple users on the same Windows Terminal Server Edition machine would get their own smbd process. With Samba 2.0.x (I'm currently testing 2.0.4b), this has changed so that every user on a WTSE machine uses the same smbd process. File ownerships are assigned correctly, but file locking does not work. If one user on a WTSE machine has a

Hi, We a re planning to migrate from the Windows NT 4.0 Terminal Server to the Windows 2000 version sometime within the next few weeks. From the newsgroups and have gathered that the MULIPLEUSERSONCONNECTION registry option that allowed each connection from the Terminal Server to start a separate smb process has been disabled in the 2000 version. Is there any work arounds that can be done in

I'm running a NT4.0 Terminal Server with 50+ peopleon it. All the users' home directories / data etc. is located on a samba server (2.2.1a) on a RedHat7.1 box. All the users on the server are shown in samba under the same connection as they're all on the same machine... this means samba only runs one copy of smb for all these users. Everything seems to be working / set up fine but

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

Does this work for: security = domain situations? Do you have to do anything special with regard to joining the domain. >>> <Drew.Zeller@statcan.ca> 11/27/02 09:16AM >>> I saw your postings and thought I would through in my two cents for the Windows 2000 Terminal Server and Samba. The MultipleUsersOnConnection does not seem to work in Windows 2000 version of Terminal

We have about 10 citrix servers (WTS 4.0, Citrix 1.8 SP2) that connect up to our file server (Enterprise 3500 Running Solaris 2.6 and Samba 2.0.7). The smb connection to the file server exists as a single smbd process for each citrix server. We belive this is causing a couple of different problems. We've applied the registry "fix" as indicated in the samba digests'.

Hi people! Does anybody remember a key in NT terminal server's registry to enable multiple connections from NT to samba (e.g. every terminal server user's request to samba volume opens a NEW connection to the samba server)? -- Yours truly, WBR, Paul Argentoff. +------------------------------------------------------- | e-mail: Paul Argentoff <argentoff@rtelekom.ru> | homepage:

Troy, This does work in the security=domain situations (This is what I am currently using in my smb.conf). You do not need to do anything special for joining the doman when using the aliases. Date: Wed, 27 Nov 2002 10:15:44 -0600 From: "Troy.A Johnson" <troy.johnson@health.state.mn.us> To: <samba@lists.samba.org> Subject: [Samba] security=domain and Citrix MetaFrame on

Hi, My setup: RedHat 7.3 PDC server with samba 2.2.7 rpm rebuilt with max connections patch and ldapsam and a few other minor changes, openldap 2.0.23-4. Windows 2000 Terminal Server with SP3, with various pre SP4 updates too. Various Win2K Pro, Win95 OSR2 clients. [homes] comment = Home writable = yes valid users = %S nt acl support = no oplocks = no path = /md3/profiles/%U

\\Pettit Connect As: Password: On the server side, I didn't get far because the domain name come up NULL so it failed on that test. Below are two logs log98.txt and log2000.txt that show full debug info. I might just have a stupid configuration or installation mistakes. I am sure that my basic configuration must work since it is a very typical setup. Any help will be highly appreciated

copy d:\bugs.ps \\ouessant\lexmark after having deleted all the samba log files and restarted the SMBd daemon from the SWAT Web interface. This leads to the INTERNAL ERROR, see samba.oulx Now, to locate the problem, I tried the same kind of command on the same file, bugs.ps, but using the SMBCLIENT application from the Linux server itself, without changing anything, nor restarting the SMBd