samba - Oct 2016 - Can't access to \\ip and some cname after migration from samba 3 to samba 4.4.5

Hi,

Recently we have migrated from samba 3 nt domain to samba 4 AD (4.4.5) and
we have detected that some applications are not working correctly, this
applications need to access to \\ip resource, with name works, but we have
some applications that needs to work only by ip
Also detected this problem with some cname in dns are not responding we use
bind9 + dlz, and we if we access from \\name works... what could be the
problem... I have tried to update windows (windows 2003) to latest updates,
reinstall some updates that can generate the problems but without success..
and I don't know how to solve this issue


For problems with cname and some name seems that if in LOGON machines
(allowed) we define only some machine then some cname fails, tried to add
samba server, \\cname... without success, only if we disable logon machines
(allow all) then this works...

About \\ip any workaround is found... any solution?

Before migration all was working correctly, and we doesn't have added any
gpo or any other special change, only migrat from samba nt to samba 4 ad
4.4.5...

Anybody can help with both errors?

Thanks

On Wed, 26 Oct 2016 17:53:17 +0200
Trenta sis via samba <samba at lists.samba.org> wrote:
> Hi,
> 
> Recently we have migrated from samba 3 nt domain to samba 4 AD
> (4.4.5) and we have detected that some applications are not working
> correctly, this applications need to access to \\ip resource, with
> name works, but we have some applications that needs to work only by
> ip Also detected this problem with some cname in dns are not
> responding we use bind9 + dlz, and we if we access from \\name
> works... what could be the problem... I have tried to update windows
> (windows 2003) to latest updates, reinstall some updates that can
> generate the problems but without success.. and I don't know how to
> solve this issue
> 
> 
> For problems with cname and some name seems that if in LOGON machines
> (allowed) we define only some machine then some cname fails, tried to
> add samba server, \\cname... without success, only if we disable
> logon machines (allow all) then this works...
> 
> About \\ip any workaround is found... any solution?
> 
> Before migration all was working correctly, and we doesn't have added
> any gpo or any other special change, only migrat from samba nt to
> samba 4 ad 4.4.5...
> 
> Anybody can help with both errors?
> 
> Thanks
After you upgraded to AD, did you create the reverse zone ?
The reverse zone is not created automatically.

Rowland

hi rowland,

after migration one of past migration tasks were generare reverse zone and
add alla and ptr manually.
I have made some additional tests and seemsthat if we shutdown samba domain
controller or  disconnect network then we can access with \\ip with two
domain members server, and then if we reconnect network in samba ad server
we reproduces error with \\ip


any solution?

thanks

2016-10-26 17:53 GMT+02:00 Trenta sis <trenta.sis at gmail.com>:
>
> Hi,
>
> Recently we have migrated from samba 3 nt domain to samba 4 AD (4.4.5) and
> we have detected that some applications are not working correctly, this
> applications need to access to \\ip resource, with name works, but we have
> some applications that needs to work only by ip
> Also detected this problem with some cname in dns are not responding we
> use bind9 + dlz, and we if we access from \\name works... what could be the
> problem... I have tried to update windows (windows 2003) to latest updates,
> reinstall some updates that can generate the problems but without success..
> and I don't know how to solve this issue
>
>
> For problems with cname and some name seems that if in LOGON machines
> (allowed) we define only some machine then some cname fails, tried to add
> samba server, \\cname... without success, only if we disable logon machines
> (allow all) then this works...
>
> About \\ip any workaround is found... any solution?
>
> Before migration all was working correctly, and we doesn't have added
any
> gpo or any other special change, only migrat from samba nt to samba 4 ad
> 4.4.5...
>
> Anybody can help with both errors?
>
> Thanks
>
>
>

hi,

error message when we try to connect with \\IP with dc available "no
network provider accepted the given network path"

2016-10-27 22:34 GMT+02:00 Trenta sis <trenta.sis at gmail.com>:
> hi rowland,
>
> after migration one of past migration tasks were generare reverse zone and
> add alla and ptr manually.
> I have made some additional tests and seemsthat if we shutdown samba
> domain controller or  disconnect network then we can access with \\ip with
> two domain members server, and then if we reconnect network in samba ad
> server we reproduces error with \\ip
>
>
> any solution?
>
> thanks
>
> 2016-10-26 17:53 GMT+02:00 Trenta sis <trenta.sis at gmail.com>:
>
>>
>> Hi,
>>
>> Recently we have migrated from samba 3 nt domain to samba 4 AD (4.4.5)
>> and we have detected that some applications are not working correctly,
this
>> applications need to access to \\ip resource, with name works, but we
have
>> some applications that needs to work only by ip
>> Also detected this problem with some cname in dns are not responding we
>> use bind9 + dlz, and we if we access from \\name works... what could be
the
>> problem... I have tried to update windows (windows 2003) to latest
updates,
>> reinstall some updates that can generate the problems but without
success..
>> and I don't know how to solve this issue
>>
>>
>> For problems with cname and some name seems that if in LOGON machines
>> (allowed) we define only some machine then some cname fails, tried to
add
>> samba server, \\cname... without success, only if we disable logon
machines
>> (allow all) then this works...
>>
>> About \\ip any workaround is found... any solution?
>>
>> Before migration all was working correctly, and we doesn't have
added any
>> gpo or any other special change, only migrat from samba nt to samba 4
ad
>> 4.4.5...
>>
>> Anybody can help with both errors?
>>
>> Thanks
>>
>>
>>
>