I've set up a web/file server at work. I'm running Ubuntu 12.04 with Samba 3.6.3. We have a windows server that functions as the domain controller (i think that's what it's called, the server that stores usernames and passwords so you can log onto the domain). I am just trying to set up file server to free up some disk space on the windows server (also acting as a file server). I am especially frustrated because I had this working for me to be able to access the root directory of the server for about three months now, but when I tried to add a share it stopped working. Now when try to map a network drive, it asked for a username and password and when I provide the samba username and password it pops up again requesting the same information. No errors, no indication of the problem. It just keeps asking for credentials until I cancel. Attached is screen shot of the credentials windows I'm talking about. Here is what I would like to do:

- create a unix user called engineering with a password for the Ubuntu server
- create a samba user also called engineering with the same password
- create a share called EngArchive accessible by any Windows XP client and user as long as they use the samba username engineering and provide the password
- map the engineering network drive on windows XP client supplying the samba username
and password


Here is my smb.conf file:

[global]
workgroup = (workgroup shown in Windows XP client's My Computer properties)
netbios name = srv-ubuntu1
security = user
wins support = yes

[EngArchive]
comment = EngArchive
valid users = engineering
read only = no
browseable = yes


Here is my testparm output:

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[EngArchive]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
workgroup = (matchesexpected workgroup)
wins support = yes
idmap config * : backend = tdb

[EngArchive]
comment = EngArchive
path = /EngArchive
valid users = engineering
read only = no



I have been combing all over forums and blogs to try to figure this out with no luck. I hope someone can help me thank you in advance

Might be an idea to install samba-swat and configure the following

Logon Options
domain logons
init logon delayed hosts
Browse Options
os level
preferred master
local master
domain master

It's obviously not authenticating.
If you can, take the Windows server out of the equation.
I presume the Windows server has an engineering user and the same password?

No there is no user "engineering" on the windows server. I was hoping to use engineering as a samba username for multiple people.

What is smb-swat ?

I have come come accross most of those directives before, but I don't really understand what they do. For instance OS level, master domain? What do those control?

swilsy,
It's time for you to do a little reading on the subject.
Start with what a PDC does - here is what wikipedia says.
The PDC emulator master receives preferential replication of password changes within the domain. As password changes take time to replicate across all the domain controllers in an Active Directory domain, the PDC emulator master receives notification of password changes immediately, and if a logon attempt fails at another domain controller, that domain controller will forward the logon request to the PDC emulator master before rejecting it.
The PDC emulator master also serves as the machine to which all domain controllers in the domain will synchronise their clocks. It, in turn, should be configured to synchronise to an external NTP time source.

To get you started disconnect the network cable to the samba server then connect just 1 win box it with a crossover cable or small switch and see if that works. If it does then you have a pdc issue.

You could also set the samba to share instead of user mode to see if that at least gives you access.

Ok I was able to get this working and here is the explanation:

I was trying to get the server to act a stand alone server, which it was. When my Windows username and password matched the samba user listed as a valid user in the samba share, I was able to map the network drive with no issues. I didn't even have to provide any credentials, because the samba server was able to use my Windows username and password provided when I logged into the Windows client. However, when I tried to access a samba share with valid users = engineering after I had already connected to a share using my Windows client username and password (which is swilson), I was unable to connect to the EngArchive share. I can only chalk this up to conflicting credentials. I was trying to access one share on the samba server with the username swilson and another using the username engineering all from the same Windows client. Samba didn't like that. When I added my Windows client username as a valid user to both shares, I was able to map both shares as network drives with no problem. I was also able to access EngArchive from other Windows clients with various usernames using the samba and unix username engineering and providing the proper password. Even though these other clients' Windows login were not engineering, the i was able to access the samba share EngArchive using engineering because there was no conflict between credentials used to access the samba server.

Moral of the story, if you are going to access a samba server for multiple shares, be consistent with the username and password you provide.