similar to: Win 7 NT4 Domain Login

I may have a clue. I have two servers running Samba 3.2.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 but no combination

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

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

OK I'm back on this after a tour through firewalld and other issues. I see Louis has posted his how to on git-hub. It seems very helpful I also see his method uses the Ubuntu resolver but also uses bind9 so I'm not sure whether his method can be adapted to using the internal DNS in Samba. In setting this up one of my main goals is to limit the amount of customization I do as I have

Rowland Penny via samba wrote: > If you are only going to have one DC, then the internal DNS server is > okay, it just doesn't work as well as Bind9. Once you have more than > one DC (which is the recommendation), then it is better to use Bind9. I have two other servers. Once the ad-cd server is up the I plan to have the other servers moved to ad and act as alternate dcs > Louis

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

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

Thanks to everyone who responded. I have now figured out what happened and why it wasn't working. Apparently somethings changed between the time I set up the machine and my attempt to add another users. When I initially set up the workstation I installed the recommended registry settings. Those were still in place. I discovered that part of the problem was that somewhere the wins server

I have two servers running Samba, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10 and running smbd, nmbd and winbindd using the tdb back end. I am having a problem understanding ID mapping. The mapping is not the same on both machines. On the Domain Controller > root at thelma:/etc/init.d# wbinfo -i 'ATLANTA\rob' > rob:*:1000:2003:Robert

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

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 been running a small domain for years. I finally decided to move the domain to ad. I am also upgrading the server from Ubuntu i6.04 LTS to 18.04 LTS I installed the new server on a new RAID array and loaded the Ubuntu LAMP stack. I installed samba. I have gone through a few tutorials which offer differing recommendation on some things. All were based on either Debian or Ubuntu. I

All, Hey hey, am new so if this is way basic, flame on. ;-) I have a Dell Poweredge 2300 running RedHat 6.0 and whatever versions of samba and such that are part of that distribution. Samb 'works' from the standpoint of file sharing and printing in a sense. The issue is that the printer is an HP Laserjet 4 connected via an external HP Jetdirect box running IP. The only connection to

Looking to make some changes to an old but working LAN, that has about 10 samba servers serving printers and network shares and a NT 4 PDC server with Exchange 5.5 on it. The samba servers are members of the nt4 domain, XP systems are members of the nt 4 domain also. Samba servers are ldapbacked. We use the ldap component directly to login to the Linux servers. I'd like to be able to

I have had a long term problem with my set up. winbind authentication is erratic. Whenever I restart one of my 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 I get can finally get it to work it

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 have a client in a similar situation. NT4 PDC w/Exchange 5.5 and Samba member servers. Main problem is that >>they're running an old custom Outlook/Exchange workflow app which locks them in until it can be replaced. Similar situation - though we've been able to replicate it fairly easily in google apps. >>As you're aware newer then XP cannot join an NT4 domain

Hello, I published two new guides: * https://wiki.samba.org/index.php/Samba_NT4_PDC_quickstart A documentation, how to set up Samba as an NT4 PDC. I called it "Quickstart", because it covers only the basic stuff. * https://wiki.samba.org/index.php/Robocopy_based_SysVol_replication_workaround For those of you having Samba DCs and Windows DCs in their domain. This is a

Any problems serving up this plotter with Samba 2.2.4? I am using RH 7.3, the plotter has a jetdirect card. I am not using samba print drivers, just passing it through raw to 192.168.21.50:raw1. Planning to let windows 98 clients use their own drivers. I couldn't get a job to print (from linux or windows). I ran out of time for today, picking up again on Monday. Any gotcha's I need to

Well, I'm attempting to migrate my old NT4-based domain to Samba3. I've got Samba set up with an LDAP backend, I've extended my NDS schema, and I've got users in this new domain set up successfully and authenticating. I've decided that the best, most seamless way to migrate my domain is to create a new domain which will run alongside the old domain. A two-way trust