Never mind. User error. I'd forgotten to set the DHCP server to hand out
the WINS IP. :(
On 10/11/2012 08:44, Nick Howitt wrote:
Hi,
I've been running Samba 3.5.18 on ClearOS 5.2 for a while now. I have
a server on its own LAN's (192.168.2.0/24 and 192.168.3.0/24) and an
IPSec VPN through to 192.168.10.0/24. The remote LAN is just one
machine on the other side of a router. I've been successfully seeing
its netbios name and I've been able to ping the remote PC by name and
browse it and vice versa. A few weeks ago I upgraded to ClearOS 6.3
with Samba 3.6.7 and with the same config I can no longer use the
remote PC's name or browse it. Both ends of the VPN are on the same
Workgroup.
I believe these are the relevant bits of smb.conf:
[global]
# General
netbios name = Server
workgroup = HOME
server string = Server
# Network
bind interfaces only = yes
interfaces = lo eth2 eth1
smb ports = 139 445
# WINS
wins support = Yes
wins server =
# Other
preferred master = Yes
domain master = Yes
remote announce = 192.168.10.255 192.168.10.120
hosts allow = 127.0.0.0/24 192.168.2.0/24 192.168.3.0/24
192.168.10.0/24 10.8.0.0/24
With 3.6.7 I also use:
max protocol = SMB2
The remote PC is running WinXP.
In my log files in /var/log/samba I see logs for mum-blue - the remote
PC - as it connects to a shared drive. On the XP machine I am forcing
it yo use NetBIOS over TCP/IP and its WINS server entry is pointing to
my server. Its firewall is open to UDP/TCP 137-139 and 445. The PC is
on 192.168.10.120.
Have I got something wrong or is there a problem with Samba?
Regards,
Nick
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
