[Samba] KVM install failure

[Rowland Penny]

On 07/12/13 19:55, Eric Smith wrote:
> That is the exact setup I'm running, yes. As I said in the original,
> as far as I know my setups are identical with the exception that one
> is running on a KVM VPS and the other runs on an internal server.
> However, I'm open to the idea. That I'm obviously missing something in
> my setup...
>
>> On Dec 7, 2013, at 1:42 PM, Rowland Penny <rowlandpenny at googlemail.com> wrote:
>>
>>> On 07/12/13 19:30, Eric Smith wrote:
>>> The IP address of the VM in both instances.
>>>
>>>> On Dec 7, 2013, at 1:29 PM, Rowland Penny <rowlandpenny at googlemail.com> wrote:
>>>>
>>>>> On 07/12/13 19:03, Eric Smith wrote:
>>>>> Just as a means of testing and toying with some AD integrations I’ve been trying to create a working Samba4 AD DC on a KVM VPS. I am using Ubuntu 12.04.3 64-bit LTS server as the OS, scratch install from .ISO. I run through exactly the same steps as I do for creating a local Samba4 DC that works like a charm, but when I try to join a Windows 7 client to my KVM Samba4 AD DC I get a credential request and then after some time an error on the client that says:
>>>>> “The following error occurred attempting to join the domain “domain.com”
>>>>> The network path was not found”
>>>>>
>>>>> The client’s sole DNS i server is set to the AD DC either case. So on the internal AD DC it’s manually set to the internal IP for the Samba4 server (which works) and for the KVM VPS it’s set to that server’s IP.
>>>>>
>>>>> I have run through the DNS tests as described in the samba.org AD DC how-to wiki article and they come back as expected. I am using to following as my DNS setup and have my authoritative external DNS servers pointing to the DC’s subdomain as well:
>>>>>
>>>>> Server Hostname:        DC3
>>>>> DNS Domain Name:  add.domain.com
>>>>> NT4 Domain Name:        domain
>>>>> IP Address:             my external IP
>>>>> Server Role:            DC
>>>>>
>>>>> Any clues as to which logs/what I can look at to get a better handle on why this is failing? It’s not an ACL issue, etc, but I’m guessing something DNS related. The funny thing is the exact same setup on my internal network works like a charm…
>>>>> Any thoughts would be greatly appreciated.
>>>>>
>>>>> thanks!
>>>> what do you mean by ' IP Address:             my external IP', do you mean the ip address of the VM or the ip address of the machine it is running on?
>>>>
>>>> Rowland
>> OK, the samba4 server will be running its own DNS server (unless you set
>> it up to use bind) and as such /etc/resolv.conf should be set to point
>> to either its own ip or 127.0.0.1, the forwarder in smb.conf should
>> point to another DNS for any name resolution outside the samba DNS zone.
>> The clients should be set to point to the Samba 4 server, anything to do
>> with the domain is handled by the internal DNS server, anything it knows
>> nothing about is forwarded to the external nameserver.
>>
>> Is this how you have set up your VM & the windows 7 client?
>>
>> Rowland
OK, then is something else running on port 53 on the server, is the 
firewall running and blocking the required ports, is apparmor running. I 
have run a similar setup as yours to test and I have never had a 
problem. Just one more thought, can you connect to the network from the 
S4 server running in the VM.

Rowland