samba - Jan 2010 - Upgrading from samba-3.0.34 to 3.4.4 - result: domain controller unavailable

Hi.

Today I upgraded samba from 3.0.34 to 3.4.4 without changing anything in 
smb.conf but with changing local and domain sid:
old samba 1) net getdomainsid and getlocalsid
new samba 2) net setdomainsid and setlocalsid to ones (both the same) 
from 1)

after restarting samba I can't log into domain: XP says : domain 
controller unavailable ... I tried to rejoin domain - and I can ;) 
however again login fails with such message.

Switching back to 3.0.34 results in proper log in

What can be wrong? Have I forgotten abut something?

Thanks,
Marcin

What form is your domain name in the previous version of Samba?  - DOMAIN.COM
etc or just DOMAIN?

I recently ran into a similar problem - 
http://old.nabble.com/Samba-PDC-workgroup-%3D-domain.com-support-td27139137.html
Samba PDC workgroup = DOMAIN.COM support .

When I went to access the domain from a windows machine it would only find a
domain controller for the DOMAIN domain not the DOMAIN.COM domain even if
DOMAIN.COM was the value for workgroup in the smb.conf file.

I am wondering if samba has stopped supporting dotted domain names in their
recent releases.


Marcin Giedz-5 wrote:
> 
> Hi.
> 
> Today I upgraded samba from 3.0.34 to 3.4.4 without changing anything in 
> smb.conf but with changing local and domain sid:
> old samba 1) net getdomainsid and getlocalsid
> new samba 2) net setdomainsid and setlocalsid to ones (both the same) 
> from 1)
> 
> after restarting samba I can't log into domain: XP says : domain 
> controller unavailable ... I tried to rejoin domain - and I can ;) 
> however again login fails with such message.
> 
> Switching back to 3.0.34 results in proper log in
> 
> What can be wrong? Have I forgotten abut something?
> 
> Thanks,
> Marcin
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
> 
-- 
View this message in context:
http://old.nabble.com/Upgrading-from-samba-3.0.34-to-3.4.4---result%3A-domain-controller-unavailable-tp27152208p27153056.html
Sent from the Samba - General mailing list archive at Nabble.com.

Marcin Giedz pisze:

nobody ;)

ok further investigation...

[2010/01/13 21:21:16,  2] 
lib/interface.c:340(add_interface)

  added interface eth0 ip=192.168.89.3 bcast=192.168.89.255 
netmask=255.255.255.0                                 
[2010/01/13 21:21:16,  2] 
lib/interface.c:463(interpret_interface)

  interpret_interface: using netmask value 24 from config file on 
interface eth0.90                                             
[2010/01/13 21:21:16,  2] 
lib/interface.c:340(add_interface)

  added interface eth0.90 ip=192.168.90.3 bcast=192.168.90.255 
netmask=255.255.255.0                            
[2010/01/13 21:21:16,  2] 
lib/smbldap_util.c:277(smbldap_search_domain_info)

  smbldap_search_domain_info: Searching 
for:[(&(objectClass=sambaDomain)(sambaDomainName=XXX))]
[2010/01/13 21:21:16,  2] 
lib/smbldap.c:856(smbldap_open_connection)

  smbldap_open_connection: connection 
opened

[2010/01/13 21:21:17,  2] 
lib/util_sock.c:938(open_socket_in)

  bind failed on port 445 socket_addr = 
0.0.0.0.

  Error = Address already in 
use

[2010/01/13 21:21:17,  0] 
smbd/server.c:457(smbd_open_one_socket)

  smbd_open_once_socket: open_socket_in: Address already in 
use                                                     
[2010/01/13 21:21:17,  2] 
lib/util_sock.c:938(open_socket_in)

  bind failed on port 139 socket_addr = 
0.0.0.0.

  Error = Address already in use
[2010/01/13 21:21:17,  0] smbd/server.c:457(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2010/01/13 21:21:17,  2] smbd/server.c:676(smbd_parent_loop)
  waiting for connections


Could this be the problem of "domain unavailable"? I have only ONE
smbd
and nmbd deamon starting in my /etc/init.d/samba script :

/opt/samba-3.4.4/sbin/smbd -D;
/opt/samba-3.4.4/sbin/nmbd -D;

doing netstat -an gives me some tcp6 samba related items... I can't find 
such things running 3.0.34 ON the same machine. My smb.conf file only 
defines interfaces = 192.168.89.0/24 192.168.90.0/24. But then again: 
3.0.34 works perfect, 3.4.4 doesn't


.......

I also found this problem in host related log file in samba whenever I 
try to login into domain:


[2010/01/13 21:22:24,  2] lib/smbldap.c:856(smbldap_open_connection)
  smbldap_open_connection: connection opened
[2010/01/13 21:22:24,  2] auth/auth.c:320(check_ntlm_password)
  check_ntlm_password:  Authentication for user [] -> [] FAILED with 
error NT_STATUS_NO_SUCH_USER

Thanks,
Marcin
> Hi.
>
> Today I upgraded samba from 3.0.34 to 3.4.4 without changing anything 
> in smb.conf but with changing local and domain sid:
> old samba 1) net getdomainsid and getlocalsid
> new samba 2) net setdomainsid and setlocalsid to ones (both the same) 
> from 1)
>
> after restarting samba I can't log into domain: XP says : domain 
> controller unavailable ... I tried to rejoin domain - and I can ;) 
> however again login fails with such message.
>
> Switching back to 3.0.34 results in proper log in
>
> What can be wrong? Have I forgotten abut something?
>
> Thanks,
> Marcin
>
>