I started a thread when I had problems with Slackware's Samba, including Slackware 14's Samba 3.6.8. Now I also have problems with OpenBSD's 5.2's Samba 3.6.6. This is mostly a Windows XP question, but it involves Samba bugs (as it is designed to work with Windows, but is not working for me :) in fact I found one specific bug, described at the bottom, though I do not know how serious it is.
These Samba versions on these operating systems (OSes) work fine with each other, and Windows XP is still able to share its own folders with computers that have these two POSIX-type OSes. I have full privileges on all these systems.
I mentioned in my Slackware Samba thread that I had got Samba working with OpenBSD. Then, I got it working with Slackware. However, one day, Windows XP was suddenly no longer able to access the stuff shared with Samba on Slackware. A few days later, Windows XP was suddenly no longer able to access the stuff shared with Samba on OpenBSD. I will post my smb.conf from each machine. They were basically the same when they started working one after another (and I may have entered a certain username or password, though I should not have had to, because they are set to guest-only access ;) they were the same when they stopped working; today I added a printer in Samba on OpenBSD, which is the only difference--and of course, I could not access this printer from Windows XP yet.
I do not recall how I gained access on Windows XP, and I do not think it was as automatic or clear as described, but I will describe how I lost access. I decided to change the shared folder on OpenBSD, so I deleted the instance of the shared folder on Windows, updated smb.conf, and never regained access by either refreshing the network location list or entering the network path manually, though I can access OpenBSD Samba shares on Slackware. The other time, I was editing in notepad and tried to save directly to the shared folder on Slackware (which I had copied back and forth to regularly on the LAN,) and then my access was immediately cut off and could never be regained in the normal sorts of ways.
I installed a so-called 'fix' from microsoft.com, which did nothing.
my smb.conf on Slackware 14
Code:
# Samba config file created using SWAT
# from UNKNOWN (127.0.0.1)
# Date: 2013/01/18 21:32:13
[global]
workgroup = MSHOME
server string = Samba Server
log file = /var/log/samba.%m
max log size = 50
dns proxy = No
idmap config * : backend = tdb
hosts allow = 192.168.1., 192.168.2., 127.
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
print ok = Yes
browseable = No
[u]
path = /home/u
read only = No
guest ok = Yes
guest only = Yes
In the following file, I am only trying to access /home/u/share from Windows.
my smb.conf on OpenBSD 5.2
Code:
# Samba config file created using SWAT
# from UNKNOWN (127.0.0.1)
# Date: 2013/02/01 22:19:59
[global]
workgroup = MSHOME
server string = Samba Server
log file = /var/log/samba/smbd.%m
max log size = 50
dns proxy = No
idmap config * : backend = tdb
hosts allow = 192.168.1., 192.168.2., 127.
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
print ok = Yes
browseable = Yes
[www]
path = /var/www
valid users = d
read only = No
[d]
path = /var/www/users/d
read only = No
[share]
path = /home/u/share
read only = No
guest only = Yes
guest ok = Yes
[InkJet]
comment = hp_photosmart_7350
path = /var/spool/samba
read only = No
guest ok = Yes
printable = Yes
print ok = Yes
printer name = InkJet
oplocks = No
share modes = No
I also set printers 'browseable' above, but SWAT would not do it and would not recognize that I had modified that in smb.conf, even after restarting all Samba daemons and reloading the 'view' page.
After access suddenly stopped working, I think I still tried everything I had tried the first time.
