Are you saying you have two WINS servers on your network or is this two different networks. If it is two servers on one network, then I think only one should be configured as a WINS server and the other one should point to the first one. Both need to be in the same workgroup/domain.

If it is two different networks then Windows is PITA. It depends if you are domain joined or not and if you have SMB1 enabled, I think. I will need to dig out some old notes to see what I discovered, but it was a lot of experimenting.

Nick Howitt wrote:

Are you saying you have two WINS servers on your network or is this two different networks. If it is two servers on one network, then I think only one should be configured as a WINS server and the other one should point to the first one. Both need to be in the same workgroup/domain.

If it is two different networks then Windows is PITA. It depends if you are domain joined or not and if you have SMB1 enabled, I think. I will need to dig out some old notes to see what I discovered, but it was a lot of experimenting.

WINS is making no difference. I have one computer on one network and another on the other side. I do get an error when using the WebUI on SAMBA.

I'm not understanding your set up. What you you mean by "I have one computer on one network and another on the other side" and what do you mean by "using the WebUI on SAMBA"? What is the error and where do you see it?

Have you checked your DNS set up, looking at the output of "ipconfig /all" on the Windoze boxes?

Two networks, my home network 192.168.0.x which on the External side of my target ClearOS and 192.168.1.x which is on the LAN side of my target ClearOS.
Network Neighbourhood to use an XP term is not showing the server but it works if I use smb://catsvr/ by name from Mint.

The Windows Networking method in Windows from Windows 95 all the way down until today was NEVER multi-network friendly. Discovery in that Module is NOT based on WINS but rather on the Master Browser process. If your server is not in the same broadcast domain, it is unlikely that you will get it to show up in Network Neighborhood because it is in a different neighborhood.

I've heard of people setting up broadcast relays in order to get the aesthetic of showing up in Network Neighborhood between two broadcast domains working. For me it was never worth it since WINS made it so that by typing \\servername always works when properly configured. If WINS is NOT working properly, you will need to type \\IP_ADDRRESS

Dave, OK but what about the PC which is on the LAN side, it can't see the server listed either yet accesses it with smb://catsvr/
I think I screwed up something in SAMBA by messing about with multiple network setups.
I suppose I need to ask the right question.

How do I get SAMBA to sort itself out?

So many of these problems where people dive into details can be solved without details using a slightly more sophisticated version of TURN IT OFF and ON AGAIN.

After I added the new card SAMBA would not even run so I restored the config backup and it then ran. That could have been a tonne of config files that needed examining.

To re-initialise samba, you can probably get away with running:

/usr/clearos/apps/samba/deploy/install

It may be a good idea to also run:

/usr/clearos/apps/samba/deploy/upgrade

But the changes it makes may have already been incorporated in the default smb.conf, /usr/clearos/apps/samba/deploy/smb.conf which gets used as a template.

Nick Howitt wrote:

To re-initialise samba, you can probably get away with running:

/usr/clearos/apps/samba/deploy/install

It may be a good idea to also run:

/usr/clearos/apps/samba/deploy/upgrade

But the changes it makes may have already been incorporated in the default smb.conf, /usr/clearos/apps/samba/deploy/smb.conf which gets used as a template.

Nick that's the sort of method a country bumpkin like me can get along with. I'll give that a go and mark this thread as solved if it works. Cheers.

Nick I ran your SAMBA install and upgrade instructions and it broke LDAP. So I wiped the server and started again using a fresh ISO download using the onboard NIC as External and the ASUS as LAN. Set up as a gateway server. Still the same problem with SAMBA. It works but does not get listed in the network. Tried it from Mint 19 and Windows 7.

I suspect there is some kind of WINS announcement/discobery message that the ASUS NIC is not passing to/from the wire. Unless it's the new Kernel that's broken.

Can you post your /etc/samba/smb.conf and /etc/dnsmasq.d/dhcp.conf?

From notes I have from a while ago:

I've had another test today.

1 - Without the SMB1.0 client enabled in Win10, with a domain logon, my server never shows in the Network tab.
2 - With the SMB1.0 client enabled in Win10, with a domain logon my server always shows immediately in the Network tab. I can then click on the server icon and see its shares.

Restricting Samba to SMB1/NT1 is irrelevant.

I don't know if this helps.

Nick Howitt wrote:

Can you post your /etc/samba/smb.conf and /etc/dnsmasq.d/dhcp.conf?

....

[root@catuksvr ~]# cat /etc/samba/smb.conf

[global]

unix password sync = Yes

# General

netbios name = catuksvr

workgroup = CAT

server string = CA Trust Server

security = user

ntlm auth = yes



# Logging

log level = 1

log file = /var/log/samba/%L-%m

max log size = 0

utmp = Yes



# Network

bind interfaces only = No

interfaces = lo enp10s0



# Printing

printcap name = /etc/printcap

load printers = Yes



# Security settings

guest account = guest

#restrict anonymous = 2



# WINS

wins support = Yes

wins server = 



# PDC/BDC

domain logons = Yes

add machine script = /usr/sbin/samba-add-machine "%u"

logon drive = U:

logon script = logon.cmd

logon path = 

logon home = \\%L\%U



# Winbind

idmap config * : backend = ldap

idmap config * : range = 20000000-29999999

winbind enum users = Yes

winbind enum groups = Yes

winbind expand groups = 1

winbind offline logon = Yes

winbind use default domain = true

winbind separator = +

template homedir = /home/%U

template shell = /sbin/nologin



# Other

preferred master = Yes

domain master = Yes

passwd program = /usr/sbin/userpasswd %u

passwd chat = *password:* %n\n *password:* %n\n *successfully.*

passwd chat timeout = 10

username map = /etc/samba/smbusers

wide links = No

allow trusted domains = Yes



# LDAP settings

include = /etc/samba/smb.ldap.conf



# Winbind LDAP settings

include = /etc/samba/smb.winbind.conf



#============================ Share Definitions ==============================



# Flexshare

# include = /etc/samba/flexshare.conf



	include = /etc/samba/flexshare.conf



[homes]

	comment = Home Directories

	path = /home/%U

	valid users = %D\%S, %D+%S, %S

	read only = No

	browseable = No

	available = Yes



[printers]

	comment = Print Spool

	path = /var/spool/samba

	printing = cups

	cups options = raw

	use client driver = Yes

	printable = Yes

	read only = No

	browseable = No

	available = No



[print$]

	comment = Printer Drivers

	path = /var/samba/drivers

	read only = No

	browseable = No

	available = No



[netlogon]

	comment = Network Logon Service

	path = /var/samba/netlogon

	read only = No

	locking = No

	browseable = No

	available = No



[profiles]

	comment = Profile Share

	path = /var/samba/profiles

	read only = No

	profile acls = Yes

	browseable = No

	available = No

	force group = domain_users

	force directory mode = 02775

Wayland Sothcott wrote:

Nick Howitt wrote:

Can you post your /etc/samba/smb.conf and /etc/dnsmasq.d/dhcp.conf?

....

[root@catuksvr ~]# cat /etc/samba/smb.conf

[global]

unix password sync = Yes

# General

netbios name = catuksvr

workgroup = CAT

server string = CA Trust Server

security = user

ntlm auth = yes



# Logging

log level = 1

log file = /var/log/samba/%L-%m

max log size = 0

utmp = Yes



# Network

bind interfaces only = No

interfaces = lo enp10s0



# Printing

printcap name = /etc/printcap

load printers = Yes



# Security settings

guest account = guest

#restrict anonymous = 2



# WINS

wins support = Yes

wins server = 



# PDC/BDC

domain logons = Yes

add machine script = /usr/sbin/samba-add-machine "%u"

logon drive = U:

logon script = logon.cmd

logon path = 

logon home = \\%L\%U



# Winbind

idmap config * : backend = ldap

idmap config * : range = 20000000-29999999

winbind enum users = Yes

winbind enum groups = Yes

winbind expand groups = 1

winbind offline logon = Yes

winbind use default domain = true

winbind separator = +

template homedir = /home/%U

template shell = /sbin/nologin



# Other

preferred master = Yes

domain master = Yes

passwd program = /usr/sbin/userpasswd %u

passwd chat = *password:* %n\n *password:* %n\n *successfully.*

passwd chat timeout = 10

username map = /etc/samba/smbusers

wide links = No

allow trusted domains = Yes



# LDAP settings

include = /etc/samba/smb.ldap.conf



# Winbind LDAP settings

include = /etc/samba/smb.winbind.conf



#============================ Share Definitions ==============================



# Flexshare

# include = /etc/samba/flexshare.conf



	include = /etc/samba/flexshare.conf



[homes]

	comment = Home Directories

	path = /home/%U

	valid users = %D\%S, %D+%S, %S

	read only = No

	browseable = No

	available = Yes



[printers]

	comment = Print Spool

	path = /var/spool/samba

	printing = cups

	cups options = raw

	use client driver = Yes

	printable = Yes

	read only = No

	browseable = No

	available = No



[print$]

	comment = Printer Drivers

	path = /var/samba/drivers

	read only = No

	browseable = No

	available = No



[netlogon]

	comment = Network Logon Service

	path = /var/samba/netlogon

	read only = No

	locking = No

	browseable = No

	available = No



[profiles]

	comment = Profile Share

	path = /var/samba/profiles

	read only = No

	profile acls = Yes

	browseable = No

	available = No

	force group = domain_users

	force directory mode = 02775

[root@catuksvr ~]# cat /etc/dnsmasq.d/dhcp.conf
# This file is managed by the API. Please add custom options in dnsmasq.conf.
dhcp-option=enp10s0,1,255.255.255.0
dhcp-option=enp10s0,28,192.168.1.255
dhcp-option=enp10s0,3,192.168.1.1
dhcp-option=enp10s0,6,192.168.1.1
dhcp-range=enp10s0,192.168.1.100,192.168.1.254,12h

So Samba is listening on all ports (from smb.conf)

Assuming your server is also the DHCP server, it is not setting the WINS server. Have you configured it in the webconfig?

Your Workgroup/Domain is set to CAT. What has been set in the Windows computer?

If you have the opportunity, can I suggest you come off the 192.168.1.0/24 subnet and also avoid 192.168.0.0/24. What is the output of "ifconfig | grep ^e -A 1"?

Nick Howitt wrote:

So Samba is listening on all ports (from smb.conf)

Assuming your server is also the DHCP server, it is not setting the WINS server. Have you configured it in the webconfig?

Your Workgroup/Domain is set to CAT. What has been set in the Windows computer?

If you have the opportunity, can I suggest you come off the 192.168.1.0/24 subnet and also avoid 192.168.0.0/24. What is the output of "ifconfig | grep ^e -A 1"?

It's a fresh install from a 7.6 USB stick. Everything is as normal as you could expect. It's what's always worked in the past. The only difference is it's 2 NICs; RealTec as External and ASUS as LAN.

I can set WINS and I can set the workgroup. It makes no difference.
The 192.168.0.x subnet is what Virgin use so that stays like that. The 192.168.1.x subnet is what everyone else uses. Only a problem if using VPN from Linux.

I'm pretty sure it's some netbios announcement that the new NIC does not do. The server was fine when using the RealTec NIC on it's own. It only stopped working when I tried to do LAN on the ASUS.

I can get round it using DNS. It seems SMB can do a lookup of the name but not discover the names of server in this setup.