similar to: Updating samba and change server

Greetings, I have tried a few days on an off to get samba to work, but need some help. Samba version Samba 3.0.23a-1.FC5.1 Linux Fedora 5 (localhost) User: dsmith 192.168.1.104 Windows XP SP2 with lastest updates (T2385) User: dan 192.168.1.100 Linksys 8 port router I found a couple problems with the checklist and fixed them. A couple problems I wasn't able to solve. Here are the

I hope that someone can let me know what I have done wrong. I need to replace and existing server (server1) with a new server (server2). Server1 is currently running LDAP/Samba (3.0.14). Profiles stored in /opt/samba/profiles I installed all of the pieces, and LDAP works (mostly, I have an issue, see below) I ran net getlocalsid DOMAINNAME on server1 used the SID value in net setlocalsid

Hello, I have just performed a yum update on my Fedora 5 machine, which I think included a samba update, and I cannot connect from WinXP to the shares defined on Fedora. When I select the samba server from WIndowsXP, a dialog box prompts for the userid and password. When userid and password are entered the dialog box just redisplays and I am not logged on, no matter how many time I try. I

Hi, I am trying a test of migrating a NT4 Domain to Samba 3 Beta 3 configured to use LDAP on Redhat 8. Is this possible? Details ------- I previously had Beta 2 on LDAP running as it's own domain controller without problem and could create users (in LDAP) with smbpasswd -a. XP clients could join and login OK. Now I have flushed that setup and have loaded Beta 3 configured to use LDAP,

Hello, now I still have a problem with my Samba installation. Userprofiles don't work under W2K SP4. They work fine with Windows NT 4. When loggin on for the first time the user profile directory is created. After loggin off however no data is written to the profile directory on the Samba PDC. My smb.conf looks like this: =====> # Samba config file created using SWAT # from 192.168.0.1

hi list&john, i read in the documention about BDCs: The domain SID has to be the same on the PDC and the BDC. In Samba versions pre-2.2.5, the domain SID was stored in the file |private/MACHINE.SID|. For all versions of Samba released since 2.2.5 the domain SID is stored in the file |private/secrets.tdb|. This file is unique to each server and cannot be copied from a PDC to a BDC; the BDC

I dowloaded from samba.org samba-3.0alpha24.. I refered http://samba.org/~jht/NT4migration/Samba-HOWTO-Collection.pdf chapter 31 it also mentioned in the how chapter 31 that it is a rough explanation but i decided to follow this and started doing things as i explaned below i looked google and samba mailing lists i did'nt see anything related to my problem anywhere Trying to Migrate from

Hello, I still have a problem with my Samba installation. Userprofiles don't work under W2K SP4. They work fine with Windows NT 4. When loggin on for the first time the user profile directory is created. After loggin off however no data is written to the profile directory on the Samba PDC. When logging on there ist the following activity in the logs (debug level = 1; log.pc1): =====>

Hi, i try to set up a samba print server with cups, but when i use the cupsaddprinter command, all copy start & stop with no problem, and when the rppcclient command is launch to add the printer driver, it fails and show me this error: # cupsaddsmb -v -U root -a [...many lines...] result was WERR_INVALID_PRINTER_NAME I try to find somthing on the net and other ML & i find this to

Morning, I have three machines, two xp and one win2k, that join the samba pdc fine. I have tried to join others to this same samba pdc using the same accounts for authentication without success. The xp machine first says the user does not exist, I click ok and go back to the screen for the domain account authorized to join the domain and press ok (or next) again and this time the xp box says the

Hi List, I'm currently migrating from win2000 to linux ( samba 3.0.10-1.4E ). Domain = TESTDOMAIN Windows Box Name = TESTPDC Linux Box = LINUXPDC I have joined the windows pdc from the linux box. Next I use: net getsid -S TESTPDC -W TESTDOMAIN which puts my SID in secrets.tdb. All is fine here. Next I use net getlocalsid which gives me an error so I use net getlocalsid TESTDOMAIN

I have a server roark (fedora core 5 with samba 3.0.23a-1.fc4.1) with a home directory awilliam. I'm trying to mount it on my linux workstation (fedora core 5, samba 3.0.23a-1.fc5.1). On my workstation I do: mount -t cifs "//roark/awilliam" /mnt/roark-awilliam/ -o username=awilliam,password=xxxxxx and when I cd to /mnt/roark-awilliam, ls works, but if I cat a file I get the

I have a linux box, Samba 3.0.23a, that is joined to a W2K3 domain. I cannot connect to the "MP3s" share (all legal!) on this system - I can connect to home directories and printers. When I try to connect to MP3s as any user on the domain, I get an Access is denied message, or it prompts me for the username and password again. I am using Winbind (if that matters), so none of these

Using Samba 3.0.23a-1.fc5.1 When I try to add XP workstation to the domain using Network ID wizard (from XP) it fails. add machine script is: /usr/sbin/useradd -d /dev/null -g 500 -s /bin/false -M %u What happens is a unix account (in passwd file) is created with LOWER-CASE username. Account is added to smbpasswd in UPPER-CASE. XP reports error "A device attached to the system is not

On a client running FC5 with all packages updated from yum (running samba 3.0.23a-1.fc5.1 and the 2.6.17-1.2157_FC5 linux kernel), I cannot access multiple samba shares that have share-level security using cifs. 0. To reproduce, use a server that serves two shares with share-level security. Make sure the shares have different passwords. 1. Using the standard mount command and specifying cifs

Hello, I have a test environment with 1 windows 2000 AD domain pdc ( mixed mode install ), 1 linux server ( to become pdc ) and a win xp box to test logon when the migration was completed. The problem is no matter what I try after the migration the win xp's logonserver = windows server not linux server. I have no idea what is going on here. I've listed the process for migration

I had the same problem after upgrading to 3.0.23a. I have one samba PDC running a basic setup back to the smbpasswd file, and one that runs OpenLDAP. The former did exactly as yours, and I ended up rolling back to version 3.0.23. On the latter, the smb process refused to run, reporting that it could not contact the database. I ended up having to remove all the database files and reinstall

I have a Samba 3.0.23a-1.fc5.1 configured on a Fedora 5 server. It's joined to an Active Directory 2003 domain controller using Winbind, etc. I'm able to connect from various workstations using active directory user accounts/credentials just fine to shares on this server, permissions work, and all is well. I'm guessing this is set up correctly. However, from another Fedora 5 server,

Okay my smb.conf file is correct. Firewall is configured correctly to allow Samba on local network. smbd and nmbd are running. Her computer still cannot connect to my printer share. I read my Samba version wrong its actually 3.0.23a-1.fc5.1, here is my smb.conf: [global] workgroup = HOME realm = SHAUN server string = Samba Server security = SHARE encrypt passwords = No log file =

I have a new server running CentOS 6.4 x64, which will serve as our new Samba4 server. It is set up in a test environment, and I've copied over the tdb files and the smb.conf file from our samba3 server (Same OS and version). I'm trying to do an in-place upgrade on the copied files, but keep hitting an assert / uncaught exception during the upgrade: # /usr/local/samba/bin/samba-tool