2
I have a samba share on a VM with CentOS inside my company network. For authentication only one user was added, which works fine.
security = user
username map = /etc/samba/smbusers
Furthermore I enabled ntlmv2 support
client ntlmv2 auth = yes
The share config looks like:
[ShareName]
comment = Comment string
path = /usr/data/path/to/shared/folder/
read only = no
browseable = yes
inherit acls = yes
guest only = no
force user = forcedUserName
The CentOS image has following configuration in the /etc/sysconfig/network-scripts/ifcfg-eth0 configuration script:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
HWADDR=XX:XX:XX:XX:XX:XX
DHCP_HOSTNAME=hostname
This is because the VM image has to be distributable between different companies, we also did not add the vm's IP to the local DNS server.
My problem is that the name resolution for "hostname" using the UNC name works only on SOME machines inside the network. I just cannot figure out what the differences are between those on which the name resolution works and the once on which it does not. Using the IP address of the vm (\\a.b.c.d\ShareName) also works on all machines. All machines are in the same subnet (255.255.128.0) and use the same DHCP server and wins server.
However, on the same vm there is also a DokuWiki installed and name resolution using any browser works fine on all machines inside the office.
So there ought to be a problem with the samba share.
I would need working name resolution on every machine so that it is possible for our office girls e.g. to create shortcuts inside the samba share without using the IP address.
PS: Firewall is not the problem either.
1Did you try adding a record to the DNS and testing it? Depending on how your machine is configured it either tries to resolve the "hostname" using broadcasts or through DNS. Manually adding the record will help narrow down the factors. – surfasb – 2011-12-22T20:59:57.100