similar to: Roaming Profiles Problem

I've posted about this problem several times but so far nothing has worked. Whenever I restart my samba servers the member server refuses to authenticate users. Sometimes is will only authenticate some users on some shares. Usually by fiddling with it I can eventually get it to work but I can't identify the solution so I can replicate it. Once it finally starts to work it works

This might be simple, but I have been banging my head against google for awhile now and not an answer in sight... Anyway, Samba PDC with roaming profiles. When a user logs out the profile isn't written because it says that "The specified network name is no longer available" Whatever that is supposed to mean. Following is my smb.conf. Please CC me in replies as I am not subbed to the

I have set samba server as PDC and I can see the network in others computers but not in the server, any idea? thx for advance my smb.cnf: # Samba config file created using SWAT # from 0.0.0.0 (0.0.0.0) # Date: 2007/03/09 22:38:36 [global] workgroup = DOMINI server string = %h Domain server (Samba, Ubuntu) obey pam restrictions = Yes passdb backend = tdbsam

We have a Windows Domain NT. We are setting up four samba Servers, two new and 2 legacy servers. The new server are Ubuntu AMD64 Linux with Samba 3.0.22 One of these is the PDC. The legacy Servers are Solaris 8 running Samba 3.0.24. We are using winbindd and local tdb files on the PDC for authentication. We plan to migrate to LDAP latter. I have used SWAT to configure each server. I have

I have two servers running Samba 2.3.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. I am don't understand the results. As far as I can tell I have everything configured as it should be. The basic globals for the DC [global] workgroup = ATLANTA time server = Yes

I'm confused about how this works in Samba. Its been a while since I set up a server and I've gotten myself confused. The new server are Ubuntu AMD64 Linux with Samba 3.0.22 One of these is the PDC. The legacy Servers are Solaris 8 running Samba 3.0.24. We are using winbindd and local tdb files on the PDC for authentication. We plan to migrate to LDAP latter. I have used SWAT to

I have a problem with accessing two share. Sigma works as expected one Windows always asks for a login name even though their smb.conf entries are the same; I even tried adding public to the Windows share with no success. [Sigma] Comment = Sigma Design Data path = /files/Lucretia/Sigma writeable = yes browseable = yes create mask = 0764 directory

I'm running out of things to check. I have two servers running Samba 2.3.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. On the Member Server when I access the [Projects] share everything works as expected. When I access the [Windows] share I get prompted for a user name and password

I just upgraded my Member Server to 3.2.4 on Ubuntu. I have a permissions problem. Users can create files on the Samba shares but they cannot delete files. Here is a typical share definition. [Testing] comment = Test for Samba path = /files/test browseable = yes writeable = yes create mask = 0764 directory mask = 0775 On the Linux side I can do

Hi List, I want to store users Profile in a NFS mount, but the problem is after joining the client to the domain It's not creating the corresponding folder structure for roaming profiles, Here is my smb.conf under Debian [global] workgroup = LOCAL netbios name = LOCAL-DOMAIN server string = %h server (debian, DC) passdb backend = tdbsam security = user username map =

Hi! First, let me apologize for the length of this message. I wanted to include as much relevant info as I could and it got a bit lengthy. For reasons that I won't bother to detail here, I ended up volunteering to upgrade the server at my kids school. It's a small private school with an all-volunteer tech support staff (me!). We currently have about 40 computers serving about 150 people.

Hi all, Yesterday, i changed from samba 2.2.3 to samba 3.0, and also i changed the machines which samba is running on. Samba worked and should work as a PDC. It runs on a Debian sid, the test client is a notebook with XP Professional. Yesterday, immediately after migrating, everything worked fine. Even after several reboots, i could logon as a domain user, and i could use the shares. Today, i

I need help understanding what is happening and trouble shooting. I have two servers running Samba 2.3.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. I have two shares on the member server and as far as I can tell they are identical. [Projects] works as expected but [Windows] always asks

In a related problem. I've tried linking my Office365 account. I get through the sign-in process but when it is attempting to link the device I can an error message stating: *We weren't able to register your device and add your account to Windows. Your access to org resources may be limited.* The domain account I am logged in with is part of the Domain Admins group so I don't think

I have having problems with what should be a fairly simple configuration. I have a PDC and a Member server accessed by several windows workstation. The PDC seem to be working fine, but every time I restart the network (usually for an update) all users have problems accessing the shares on the Member Server. Sometimes only a few share are accessible. sometime none. I have been able to get it

Hey List, I was wondering if and how one would go about tracking file activity on a Samba server, for basic auditing purposes. I'd ideally like to see what files where edited, by whom and when. I've done some RTFM and a bit of searching around the 'net, but haven't found anything yet. Even pointers to documentation on the subject would be welcome. Thanks in advance for

I have a problem with a Member Server on Samba 3.0.28a running on Ubuntu Heady. Both systems were recently upgraded using Ubuntu's automated upgrade. It's also possible I broke a working configuration by accident. The shares on the Member server are visible on the XP clients and some users can authenticate properly. At least one user on one XP desktop cannot. The shares are visible

Hello! This is my setup Using 3.0.14a-3sarge on Deb. This is my smb.conf file ---------------------------------------- # Global parameters [global] workgroup = MYWORKGROUP server string = Samba Server obey pam restrictions = Yes passwd program = /usr/bin/passwd %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n

I'm wondering if anyone has run across that and MUCH more importantly, if the data can be recovered somehow. I'll put as much details as I can at the bottom but here's the gist of the problem: I added my wives computer (which contains 8 years worth of pictures) to the domain. When I logged into the new domain account it was empty and my wives domain users had no access so I did the

Hi, I've recently upgraded our Samba 3.2.5 to 3.5.5 from Debian testing repositary. This because of a future Windows 7 roll out. Installation and all the server stuff seemed to go fine (all deamons started) but when some of our (not all) users try to log on they get an error message saying "Procedure number is out of range". There is no difference between the XP clients that users