similar to: "map to guest" parameter

We're encountering a problem with AstTAPI crashing on Windows 2000 Workstations. The program we're using is called Amicus Attorney, it uses a standard TAPI interface to be able to dial our clients, but on the 2 Windows 2000 workstations we've tried it on it has crashed, no errors or anything. When we select the Asterisk TAPI driver, the whole windows just closes/crashes w/ no apparent

this was previously posted only on samba-ntdom, but that was probably not the right list so i'm cross-posting to both samba and samba-ntdom. here's the problem: on NT4 w/ SP4 or SP5, self-extracting 16-bit install files work just fine in directories w/ Long File Names. on SAMBA 2.0.5a, i can get none of the aforementioned files to install from directories w/ Long File Names. a good

Hi, Amicus Attorney is a server/client Practice Management software for law firms. We run it on a Windows 2000 server. We have our file sharing on SMBS Linux server I run a dual boot PC. I have installed Amicus Client successfully with Wine. The fonts look pretty good. All the database info gets installed fine. The problem is it does not synchronise so it cannot add to or collect info

I have it running on my Windows 2000 mahcine using STI products and don't have much of a problem. I would guess that it might be something on the workstations instead of the AstTAPI. Also, might be a little faster, easier, cheaper to just upgrade your existing workstations? Just a thought. Feel free to contact me off list if you would like. Thanks, Dustin -----Original Message-----

I have a very simple Samba 3.0.1 install without LDAP/ADS/winbind support compiled into it. I have noticed a strange problem with supplementary groups I noticed with Mac OS X (10.3.2). The SAMBA server is using 'ntdomain' authentication. When someone connects to the SAMBA server and gives their username in uppercase (the OS's default), then none of the secondary UNIX groups the

Hi, Installed latest Samba3.0.2a on NT4 domain, security = domain and net rpc join successfully. everything work great, but group permission failed, error message is "user_in_winbind_group_list: nametogid for group NTGROUP failed". smb.conf on shares as below: ===================== omitted base configurations... [shareA] path = /public/shareA valid users =

We have a windows domain "AD" and a samba domain "SAD" running Samba 4.9 in AD-mode. We also have an old NT4 domain called "Samba" running Samba 3.6 + OpenLDAP. We have the same users and passwords in all three. The user objects in the "SAD"-domain have the same uidNumber as in the "Samba"-domain. Workstations and users log on to the windows

hy jerry that's what i needed. seems to work. thinking about to go with this version in production on friday, old 2.2.x version get's some performance problems. i'll test for 2 days (with low load). let you know if we have further problems. (Our infrastructur on tru64, 500 users mapped down to arround 20 samba users) who get the documents from smb-share. one last question, is it

Hi, I'm using 3.0.21b and I cannot get the guest account to work. some of smb.conf: ------------------------------ security = user hosts allow = 192.168.2. 127. guest account = visiteur log level = 2 log file = /var/log/samba/samba.%m max log size = 1024 socket options = TCP_NODELAY [publique] path = /vol2/samba/publique browseable = yes guest ok = yes

Hello Samba users, I'm trying to configure my samba server as a PDC for some Win2k machines. I'm running Red Hat 8.0 and samba-3.0.0rc4. Everything seems to be ok, when using workgroup configuration, all the shares works fine. But I cant get the Win2k clients to log in the Domain. It says I have a unknown user or an incorrect password. But at least it prompted me for a user/password, so I

Hello, I'm having some difficulty trying to join a WinXP client to our Samba domain. When I try to join the client to the domain and I submit the computer name and the domain name in the computer identification control panel, I'm prompted for the root user and password on the server, so I enter root and the root password on our Samba server. I then get a message saying that it

After upgrading to samba-3.0.30 on domain member servers using NT4 as PDC and running winbind users can no longer access the shares, they get prompted for passwords (which shouldn't happen) yet still cannot connect. Dropping back to 3.0.28a works (even after adding the recent security patch) fine. What can I provide to get this fixed? Thank you, -- Chris

Hello, I have a configuration issue that I cannot seem to fix. Running Samba 2.2.2 on Sun Solaris servers using NIS Scenario: I have 5 different samba servers that I map permanent drives to in Windows 2000. When I boot 2000 I get a login for my username and password then it starts to automatically map the samba drives. I am then prompted for a username and password for each separate samba

We have setup a Samba member server using Winbind (3.0.14a and NT4). I am trying to "map" the NT Domain ids to root (root = admin administrator rdehn) but this seems to be ignored when I try and connect to a share. The "username map = /etc/samba/smbusers" line is in the Global section of smb.conf and testparm is OK. What am I missing? Is this not possible? Thanks in

I have been using the "username map" parameter for some time on various versions of Samba 2, and it has worked nicely. Last week I upgraded to Samba 3 and integrated with Active Directory. Since I am using Solaris 8, and "nsswitch.conf" doesn't support winbindd, I am using the "add user script" parameter to add users. What is happening is that users in

Hi all, Set-up: Local NT4-RESOURCE domain which the Samba server is a member off. One NT4-ADMIN domain with users accounts and one W2K domain with some other user accounts. A one way trust from NT4-ADMIN to NT4-RESOURCE and a one way trust from W2K to NT4-RESOURCE. Samba version 2.0.7 running on Solaris 2.6. According to the NT admins, the W2K domain is in native mode, but they still use

Rowland said: >> Is there a set of settings to restore the mapping of AD users to pre-existing Unix Users? >No >> >> Does the official Samba distributed project source continue to support AD Users mapping to pre-existing Unix Users? >I do not think it ever did. I found this reference quickly from google describing the previous behavior. Winbind was always optional

when using an nt 4.0 client, i can get non-guest access to all shares as i want. however, i cannot get access to any printers unless the printer is setup as a guest printer. nt 4.0 always seems to try to use the printer as guest user. nt 4 never gives me the chance to give a passwd for access to the server. (i do have SP3 on nt). if i use win 95 client, i can get access to all shares and

I am trying to establish a domain trust between a Samba 3.024 domain and a PC Netlink 2.0 domain. Currently, we are using PC Netlink as our primary Windows file server and "NT4" domain controller. (Lets say that the domain is called LEGACY and the domain controller LX1) Windows 2003 servers are unable to join a PC Netlink domain (even with the SignOrSeal option disabled.) For

Greets Anyone on the list using newer HP G4 or G5 server hardware like DL36X or DL38X with Centos? Or other HP hardware? Are you running Intel, AMD, or both? Are you using SAS or SATA or a mix? Are you using Centos 3, CentOS 4, or starting migration to CentOS 5 Are things rock solid stable without any issues? I know older Compaq and HP boxen have been rock solid for us for years yet we