samba - May 2010 - URGENT! Issues after upgrade from Ubuntu Dapper to Lucid

?hello!

I need urgent help. I upgraded from dapper to lucid (samba version 3.0 ->
3.4). Now I cannot log in to domain anymore (domain controller not available
message), also new clients cannot join domain (semaphore timeout message after
typing root username and password). If I take LAN cable out, so i can login,
then shares work normally. What could have changed so i have issues? My smb.conf
is same as before (samba 3.0):

[global]
log level = 2
interfaces=eth0
smb ports = 139
passwd program = /usr/bin/passwd %u
passdb backend = smbpasswd
log file = /var/log/samba/log.%m
logon drive = H:
null passwords = no
domain master = yes
encrypt passwords = true
netbios name = LINUX
server string = PROCESS Linux Server
hosts allow = 10.0.0. 127.0.0. 192.168.1. 5.16.0.42 5.16.9.205 5.23.148.49
5.115.69.13 5.141.108.161 5.184.75.181 5.177.169.242
#hosts deny = 0.0.0.0/0
load printers = yes
max log size = 50
dos charset = CP852
UNIX charset = CP852
display charset = CP852
#client code page = 852
#valid chars = ??:??,??:? ,??:??,??:??,??:??
create mask = 0770
directory mask = 0770
force create mode = 0770
force group = smbacc
logon script = %U.bat
#wins support = yes
socket options = TCP_NODELAY SO_SNDBUF=65536 SO_RCVBUF=65536
unix password sync = yes
local master = yes
workgroup = PROCESS
os level = 99
add user script = /usr/sbin/useradd %u
add machine script=/usr/sbin/useradd -g machines -c Machine -s /bin/false %u
security = user
preferred master = yes
#domain admin group = @samadm
domain logons = yes
smb passwd file = /etc/samba/smbpasswd
hide unreadable = yes
vfs objects = full_audit
full_audit:failure = none
full_audit:success = mkdir rename unlink rmdir open pwrite
full_audit:prefix = %u|%I|%m|%S

[netlogon]
path = /mnt/data1/netlogon
public = no
browsable = no
read only = yes
guest ok = yes
admin users = root


And else are shares so I dont paste here!

Any help would be greatly appreciated!! Thank you very much!

So... a LOT has changed.  Your best bet is to revert that machine back 
to a samba 3.0 and build up a test machine with samba 3.4.

I don't know what's wrong with your setup (don't have one like it),
but
i do know that having time to work on a system is much easier to deal 
with than to do it under the gun.

good luck!


On 05/29/10 02:55 PM, Igor R. wrote:
> hello!
>
> I need urgent help. I upgraded from dapper to lucid (samba version 3.0
->  3.4). Now I cannot log in to domain anymore (domain controller not
available message), also new clients cannot join domain (semaphore timeout
message after typing root username and password). If I take LAN cable out, so i
can login, then shares work normally. What could have changed so i have issues?
My smb.conf is same as before (samba 3.0):
>
> [global]
> log level = 2
> interfaces=eth0
> smb ports = 139
> passwd program = /usr/bin/passwd %u
> passdb backend = smbpasswd
> log file = /var/log/samba/log.%m
> logon drive = H:
> null passwords = no
> domain master = yes
> encrypt passwords = true
> netbios name = LINUX
> server string = PROCESS Linux Server
> hosts allow = 10.0.0. 127.0.0. 192.168.1. 5.16.0.42 5.16.9.205 5.23.148.49
5.115.69.13 5.141.108.161 5.184.75.181 5.177.169.242
> #hosts deny = 0.0.0.0/0
> load printers = yes
> max log size = 50
> dos charset = CP852
> UNIX charset = CP852
> display charset = CP852
> #client code page = 852
> #valid chars = ??:??,??:? ,??:??,??:??,??:??
> create mask = 0770
> directory mask = 0770
> force create mode = 0770
> force group = smbacc
> logon script = %U.bat
> #wins support = yes
> socket options = TCP_NODELAY SO_SNDBUF=65536 SO_RCVBUF=65536
> unix password sync = yes
> local master = yes
> workgroup = PROCESS
> os level = 99
> add user script = /usr/sbin/useradd %u
> add machine script=/usr/sbin/useradd -g machines -c Machine -s /bin/false
%u
> security = user
> preferred master = yes
> #domain admin group = @samadm
> domain logons = yes
> smb passwd file = /etc/samba/smbpasswd
> hide unreadable = yes
> vfs objects = full_audit
> full_audit:failure = none
> full_audit:success = mkdir rename unlink rmdir open pwrite
> full_audit:prefix = %u|%I|%m|%S
>
> [netlogon]
> path = /mnt/data1/netlogon
> public = no
> browsable = no
> read only = yes
> guest ok = yes
> admin users = root
>
>
> And else are shares so I dont paste here!
>
> Any help would be greatly appreciated!! Thank you very much!
>

do your users still have Samba rights?

http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/rights.html

On May 29, 2010 5:06 PM, "Igor R." <igor.rakusa at gmx.com>
wrote:

hello!

I need urgent help. I upgraded from dapper to lucid (samba version 3.0 ->
3.4). Now I cannot log in to domain anymore (domain controller not available
message), also new clients cannot join domain (semaphore timeout message
after typing root username and password). If I take LAN cable out, so i can
login, then shares work normally. What could have changed so i have issues?
My smb.conf is same as before (samba 3.0):

[global]
log level = 2
interfaces=eth0
smb ports = 139
passwd program = /usr/bin/passwd %u
passdb backend = smbpasswd
log file = /var/log/samba/log.%m
logon drive = H:
null passwords = no
domain master = yes
encrypt passwords = true
netbios name = LINUX
server string = PROCESS Linux Server
hosts allow = 10.0.0. 127.0.0. 192.168.1. 5.16.0.42 5.16.9.205 5.23.148.49
5.115.69.13 5.141.108.161 5.184.75.181 5.177.169.242
#hosts deny = 0.0.0.0/0
load printers = yes
max log size = 50
dos charset = CP852
UNIX charset = CP852
display charset = CP852
#client code page = 852
#valid chars = ??:??,??:? ,??:??,??:??,??:?
create mask = 0770
directory mask = 0770
force create mode = 0770
force group = smbacc
logon script = %U.bat
#wins support = yes
socket options = TCP_NODELAY SO_SNDBUF=65536 SO_RCVBUF=65536
unix password sync = yes
local master = yes
workgroup = PROCESS
os level = 99
add user script = /usr/sbin/useradd %u
add machine script=/usr/sbin/useradd -g machines -c Machine -s /bin/false %u
security = user
preferred master = yes
#domain admin group = @samadm
domain logons = yes
smb passwd file = /etc/samba/smbpasswd
hide unreadable = yes
vfs objects = full_audit
full_audit:failure = none
full_audit:success = mkdir rename unlink rmdir open pwrite
full_audit:prefix = %u|%I|%m|%S

[netlogon]
path = /mnt/data1/netlogon
public = no
browsable = no
read only = yes
guest ok = yes
admin users = root


And else are shares so I dont paste here!

Any help would be greatly appreciated!! Thank you very much!
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

SNIP
>
> I need urgent help. I upgraded from dapper to lucid (samba version 3.0 
> -> 3.4). Now I cannot log in to domain anymore (domain controller not 
> available message), also new clients cannot join domain (semaphore 
> timeout message after typing root username and password). If I take 
> LAN cable out, so i can login, then shares work normally. What could 
> have changed so i have issues? My smb.conf is same as before (samba 
> 3.0):
Rejoin the workstations to the domain.  Likely corrupted/bad machine 
account entries.

Cheers,

TMS III
>
>
>
> [global]
> log level = 2
> interfaces=eth0
> smb ports = 139
> passwd program = /usr/bin/passwd %u
> passdb backend = smbpasswd
> log file = /var/log/samba/log.%m
> logon drive = H:
> null passwords = no
> domain master = yes
> encrypt passwords = true
> netbios name = LINUX
> server string = PROCESS Linux Server
> hosts allow = 10.0.0. 127.0.0. 192.168.1. 5.16.0.42 5.16.9.205 
> 5.23.148.49 5.115.69.13 5.141.108.161 5.184.75.181 5.177.169.242
> #hosts deny = 0.0.0.0/0
> load printers = yes
> max log size = 50
> dos charset = CP852
> UNIX charset = CP852
> display charset = CP852
> #client code page = 852
> #valid chars = ??:??,??:? ,??:??,??:??,??:??
> create mask = 0770
> directory mask = 0770
> force create mode = 0770
> force group = smbacc
> logon script = %U.bat
> #wins support = yes
> socket options = TCP_NODELAY SO_SNDBUF=65536 SO_RCVBUF=65536
> unix password sync = yes
> local master = yes
> workgroup = PROCESS
> os level = 99
> add user script = /usr/sbin/useradd %u
> add machine script=/usr/sbin/useradd -g machines -c Machine -s 
> /bin/false %u
> security = user
> preferred master = yes
> #domain admin group = @samadm
> domain logons = yes
> smb passwd file = /etc/samba/smbpasswd
> hide unreadable = yes
> vfs objects = full_audit
> full_audit:failure = none
> full_audit:success = mkdir rename unlink rmdir open pwrite
> full_audit:prefix = %u|%I|%m|%S
>
> [netlogon]
> path = /mnt/data1/netlogon
> public = no
> browsable = no
> read only = yes
> guest ok = yes
> admin users = root
>
>
> And else are shares so I dont paste here!
>
> Any help would be greatly appreciated!! Thank you very much!
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba

Hello,

2010/5/30 Igor R. <igor.rakusa at gmx.com>
> hello!
>
> I need urgent help. I upgraded from dapper to lucid (samba version 3.0
->
> 3.4). Now I cannot log in to domain anymore (domain controller not
available
> message), also new clients cannot join domain (semaphore timeout message
> after typing root username and password). If I take LAN cable out, so i can
> login, then shares work normally. What could have changed so i have issues?

Take a look at this:
http://www.mail-archive.com/samba at lists.samba.org/msg108209.html
Basically, try to re-join machines into domain at first.

---
wbr, Denis.

Hello,

rejoining was not possible (semaphore timeout when trying to rejoin). I 
tried to use .deb file for ubuntu 8.04 (Samba 3.0.28). Samba worked 
better but logging into domain was still not possible. So I tried to use 
deb file from Dapper Ubuntu (6.06) - Samba 3.0.22 (which was first 
version on this server). Doing that I had some issues with libraries and 
resolved them with some ugly hacking (basically copying some libraries 
.so -> .so.2). Now Samba 3.0.22 successfully launches and runs without 
problems. It seems that upgrading Samba is harder to do than I was 
thinking. Good to know for future. Always do it on a test machine before!

Thanks!

On 30.5.2010 15:14, Denis Fateyev wrote:
> Hello,
>
> 2010/5/30 Igor R. <igor.rakusa at gmx.com <mailto:igor.rakusa at
gmx.com>>
>
>     hello!
>
>     I need urgent help. I upgraded from dapper to lucid (samba version
>     3.0 -> 3.4). Now I cannot log in to domain anymore (domain
>     controller not available message), also new clients cannot join
>     domain (semaphore timeout message after typing root username and
>     password). If I take LAN cable out, so i can login, then shares
>     work normally. What could have changed so i have issues? 
>
>
> Take a look at this: 
> http://www.mail-archive.com/samba at lists.samba.org/msg108209.html
> Basically, try to re-join machines into domain at first.
>
> ---
> wbr, Denis.
>