Problems setting up (fresh) Samba 4 installation
Rowland Penny
repenny at f2s.com
Thu Jan 3 09:16:40 MST 2013
On 03/01/13 15:34, Mark Pilant wrote:
> Hi Bob.
>
>> looking through your output I saw 192.168.122.1 ( makes me want to say
> KVM virt might be involved in your troubles )
>
> As I'm running RHEL in a VM, the 192.168.122.1 address is assigned to the
> virbr0 interface. (If it matters, I'm running the VM under Microsoft's
> Hyper-V. Other than the current Samba issues, the RHEL VM is workign
> fine.) This is one reason I explicitly set the host IP address on the
> command line the later attempt at provisioning.
>
>> Is libvirt installed and dnsmasq running?? ( usually installed by
> default ) and if so do you need it? If not remove all the libvirt and
> dnsmasq packages and that might clear up your troubles.
>
> I'm not sure if it is needed for the VM environment in which RHEL is
> running. I'm going to try the same exercise on a separate system (bare
> metal) running RHEL 6.3.
>
> - Mark
>
Hi,
If during provision you do not set the DNS server, you use the internal
server. You also seem to be setting the forwarder to point to itself,
try setting it (in /usr/local/samba/etc/smb.conf) to point to a known
good dns server. Ensure that the nameserver in /etc/resolv.conf points
to either 127.0.0.1 or the machines ip address, check /etc/krb5.conf, it
should have just three lines in it, if it has more or doesn't exist,
copy the one from /usr/local/samba/private/krb5.conf. Now restart samba
4.0.0 and try again
Rowland
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the samba-technical
mailing list