Alright, so I'm upgrading my file server from Samba 3.6 to 4.4 (yeah I know, I'm a slacker) and I seem to have hit a brick wall.
The way it was setup before was an open (SHARE security in Samba) file server with two shares mapped to the same user: server. This is what my 3.6 config file looked like:
Here's the smb4.conf file I have so far:
This passes the sanity check, but when I navigate to \\MAINFRAME on a Windows machine, I don't see any shares. If I try typing the full path of the share like \\MAINFRAME\files it just times out. I also tried setting it up with guest ok = no, then adding the server user with
The way it was setup before was an open (SHARE security in Samba) file server with two shares mapped to the same user: server. This is what my 3.6 config file looked like:
Code:
[global]
server string = MAINFRAME
interfaces = re0
security = SHARE
guest account = server
log file = /usr/local/samba/var/log.%m
max log size = 50
dns proxy = No
idmap config * : backend = tdb
valid users = server
admin users = server
read list = server
write list = server
hosts allow = 10.0.0., 127.
[files]
comment = File Services
path = /usr/home/server/FILE_SHARE
read only = No
guest ok = Yes
[bulk]
comment = Video and Bulk Data
path = /usr/home/server/BULK_STORAGE
read only = No
guest ok = Yes
Code:
[global]
workgroup = WORKGROUP
netbios name = MAINFRAME
map to guest = Bad User
[files]
path /usr/home/server/FILE_SHARE
read only = no
guest ok = yes
[bulk]
path /usr/home/server/BULK_STORAGE
read only = no
guest ok = yes
smbpasswd -a server
then smbpasswd -e server
but I still get the same thing, it just asks me for a password before it times out. What am I doing wrong here?