Re: [Samba] Can't join Windows 7 Pro/XP to samba PDC

2011-03-31 Thread Gérard Guével
Andres,

Your smb.conf seems right at a first glance. Is it a choice not to set the
local master to yes ?

What are your charsets ? Something like 
dos charset = CP850, unix charset = UTF-8, display charset = LOCALE
I already have a connection problem with the dos charset set to CP850.
Try with dos charset set to ASCII.

Please increase your log level to 10 and give me the results of the
following commands.
You can launch these commands locally and/or from a Linux station if
possible :
•   testparm -v |grep charset
•   nmblookup -B yourboard __SAMBA__
•   nmblookup -M ARAMDA
•   nmblookup -d 2 '*'
•   findsmb
•   smbclient -L yourboard –Uxxx
Check if you detect some protocol negotiation failed in your samba.log
file.

At the end, you can launch a full testparm -v to display  all your samba
parameters values.
It can be convenient to detect a problem.

Good luck
Gérard


-Message d'origine-
De : atara...@gmail.com [mailto:atara...@gmail.com] De la part de Andres
Tarallo
Envoyé : mercredi 30 mars 2011 15:04
À : Gérard Guével
Cc : samba
Objet : Re: [Samba] Can't join Windows 7 Pro/XP to samba PDC

Gerard:

Here is my smb.conf

[global]
  workgroup = ARAMDA
  map to guest = Bad User
  passdb backend = ldapsam:ldap://localhost
  log level = 3
  log file = /var/log/samba.log
  printcap name = cups
  add user script = ldapsmb -a -u %u
  delete user script = ldapsmb -d -u %u
  add group script = ldapsmb -a -g %g
  delete group script = ldapsmb -d -g %g
  add user to group script = ldapsmb -j -u %u -g %g
  delete user from group script = ldapsmb -j -u %u -g %g
  set primary group script = ldapsmb -m -u %u -gid %g
  add machine script = /usr/sbin/smbldap-useradd -t 0 -g 1515 -w %u
  logon path = \\%L\profiles\.msprofile
  logon drive = Z:
  logon home = \\%L\%U\.9xprofile
  domain logons = Yes
  os level = 65
  preferred master = Yes
  domain master = Yes
  wins support = Yes
  ldap admin dn = cn=replicasamba,dc=aramda,dc=uy
  ldap group suffix = ou=Groups
  ldap idmap suffix = ou=Idmap
  ldap machine suffix = ou=Computers
  ldap passwd sync = yes
  ldap suffix = dc=aramda,dc=uy
  ldap ssl = no
  ldap user suffix = ou=People
  add share command = /var/lib/samba/scripts/modify_samba_config.pl
  delete share command = /var/lib/samba/scripts/modify_samba_config.pl
  usershare allow guests = Yes
  hosts allow = 127.0.0.1, 172.16.1.
  cups options = raw

I will test your suggestions.

Andrés


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


Re: [Samba] Can't join Windows 7 Pro/XP to samba PDC

2011-03-30 Thread Gérard Guével
For a windows 7, I modify the following key in the windows registry :
 
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Para
meters]
DNSNameResolutionRequired=dword:
DomainCompatibilityMode=dword:0001

Some calls to check the SAMBA PDC :
•   testparm -v
•   nmblookup -B myboard __SAMBA__
•   nmblookup -M mygroup
•   nmblookup -d 2 '*'
•   findsmb
•   smbclient -L myboard –Uxxx
•   smbclient //myboard/public -Uxxx

Can send me your smb.conf to check.
Gérard

-Message d'origine-
De : samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] De
la part de Andres Tarallo
Envoyé : mercredi 30 mars 2011 12:25
À : samba
Objet : Re: [Samba] Can't join Windows 7 Pro/XP to samba PDC

2011/3/24 Chris Weiss cwe...@gmail.com:
 On Thu, Mar 24, 2011 at 8:40 AM, John Drescher dresche...@gmail.com
wrote:
 On Thu, Mar 24, 2011 at 9:36 AM, Andres Tarallo atara...@acm.org wrote:
 2011/3/23 Gaiseric Vandal gaiseric.van...@gmail.com:
 Did you try manually creating a unix user account for the samba
machine?
  Does getent passwd show that machine?


 Yes, I've created a user account with smbldap-passwd. We can login 
 through ssh and from console.


 Did you create the a account for the machine you are trying to add?

 John

 add machine script is in the conf, so manual creation should not be
needed.

 better question is: does the machine account actually get created in 
 the right place?

Yes, tne machines account are created under the Computers OU, where samba
should lookup them.

As said before: we runned out of ideas. So your ideas are highly
appreciated.

Andrés

PS: Did you see something wrong in our smb.conf.?

Andrés
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

__ Information provenant d'ESET NOD32 Antivirus, version de la base
des signatures de virus 5999 (20110330) __

Le message a été vérifié par ESET NOD32 Antivirus.

http://www.eset.com



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


[Samba] Samba 3.2.15 : DOS charset problem on powerpc big endian architecture

2011-03-28 Thread Gérard Guével
Hello,

 

With a default CP850 dos charset, I can’t connect and receive a “protocol
negotiation failed” error message

# testparm -v |grep charset

Load smb config files from /etc/samba/smb.conf

Module '/usr/lib/charset/CP850.so' loaded

Server role: ROLE_STANDALONE

dos charset = CP850

unix charset = UTF-8

display charset = LOCALE

 

# smbclient -L MYSERVER -Uadmin

protocol negotiation failed

 

The samba log file gives me 

 

[2011/01/11 13:22:53, 10] lib/util.c:dump_data(2230)

  [000] 02 50 43 20 4E 45 54 57  4F 52 4B 20 50 52 4F 47  .PC NETW ORK PROG

  [010] 52 41 4D 20 31 2E 30 00  02 4D 49 43 52 4F 53 4F  RAM 1.0. .MICROSO

  [020] 46 54 20 4E 45 54 57 4F  52 4B 53 20 31 2E 30 33  FT NETWO RKS 1.03

  [030] 00 02 4D 49 43 52 4F 53  4F 46 54 20 4E 45 54 57  ..MICROS OFT NETW

  [040] 4F 52 4B 53 20 33 2E 30  00 02 4C 41 4E 4D 41 4E  ORKS 3.0 ..LANMAN

  [050] 31 2E 30 00 02 4C 4D 31  2E 32 58 30 30 32 00 02  1.0..LM1 .2X002..

  [060] 44 4F 53 20 4C 41 4E 4D  41 4E 32 2E 31 00 02 4C  DOS LANM AN2.1..L

  [070] 41 4E 4D 41 4E 32 2E 31  00 02 53 61 6D 62 61 00  ANMAN2.1 ..Samba.

  [080] 02 4E 54 20 4C 41 4E 4D  41 4E 20 31 2E 30 00 02  .NT LANM AN 1.0..

  [090] 4E 54 20 4C 4D 20 30 2E  31 32 00 NT LM 0. 12.

…

[2011/01/11 13:22:53, 10] lib/util.c:set_remote_arch(2205)

  set_remote_arch: Client arch is 'UNKNOWN'

…

[2011/01/11 13:22:53,  0] smbd/negprot.c:reply_negprot(675)

  No protocol supported !

[2011/01/11 13:22:53,  5] smbd/negprot.c:reply_negprot(680)

  negprot index=-1

 

 

With an ASCII dos charset, it works fine.

# testparm -v |grep charset

Load smb config files from /etc/samba/smb.conf

Server role: ROLE_STANDALONE

dos charset = ASCII

unix charset = UTF-8

display charset = LOCALE

 

# smbclient -L MYSERVER -Uadmin

Enter admin's password: 

Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.2.15]

 

I have some other samba servers on Intel architecture which runs with CP850
dos charset.

What I miss with my powerpc architecture ?

 

Thanks for all tips.

Gérard

 

 

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


[Samba] Migration from NT4 to Samba PDC : NT_STATUS_INVALID_NETWORK_RESPONSE

2008-12-17 Thread Gérard Guével

Hello,

I want to migrate from an old NT4 PDC to a Samba version 3.0.26a.

My BDC configuration for migration is
[global]
workgroup = DOMAIN
server string = %h server Samba %v
interfaces = eth0, 192.168.1.0/24, lo
bind interfaces only = Yes
security = DOMAIN
map to guest = Bad User
passdb backend = tdbsam
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n
*passwd:*password\supdated\ssuccessfully* .
unix password sync = Yes
log level = 4
syslog = 0
log file = /var/log/samba.log
max log size = 1000
name resolve order = lmhosts hosts wins bcast
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
add user script = /usr/sbin/useradd -g users -c 'SMB Users
Account' -d /dev/null -s /bin/false '%u'
delete user script = /usr/sbin/userdel -r '%u'
add group script = /usr/sbin/groupadd '%g'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/bin/gpasswd -a '%u' '%g'
delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
set primary group script = /usr/sbin/usermod -g '%g' '%u'
add machine script = /usr/sbin/useradd -g machines -c 'SMB Machine
Account' -d /dev/null -s /bin/false '%u'
domain logons = Yes
os level = 33
preferred master = No
local master = No
domain master = No
dns proxy = No
wins server = 192.168.1.204
panic action = /usr/share/samba/panic-action %d
admin users = root

I can join the NT4 PDC as BDC
net rpc join BDC -S NTSERVER -w DOMAIN -U admin%pwd
Joined domain DOMAIN.

But when I want to vampire or samdup the NT server, I have the following
message
net rpc samdump -S NTSERVER -w DOMAIN -U admin%pwd
[2008/12/17 19:38:39, 0]
rpc_client/cli_pipe.c:cli_rpc_pipe_open_schannel(2679)
  cli_rpc_pipe_open_schannel: failed to get schannel session key from server
NTSERVER for domain DOMAIN.
[2008/12/17 19:38:39, 0] utils/net_rpc.c:run_rpc_command(151)
  Could not initialise schannel netlogon pipe. Error was
NT_STATUS_INVALID_NETWORK_RESPONSE

I have already read many recommended web tuto about NT4 migration.

Any tip would be welcome
Thanks
Gérard


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Migration from NT4 to Samba PDC : problem with machine sid ?

2006-08-25 Thread Gérard Guével

Hello,

I'm trying to migrate a PDC from NT4 to Samba.
Samba version is 3.0.7 with a passdb backend = tdbsam.

The migration goes right and I retreived the users, groups
and machines accounts with the net rpc vampire command.

The domain SID is S-1-5-21-1957908234-1424639752-1538882281

for my user account, I get these informations :
Unix username:geg
NT username:  geg
Account Flags:[U  ]
User SID: S-1-5-21-1957908234-1424639752-1538882281-1011
Primary Group SID:S-1-5-21-1957908234-1424639752-1538882281-1038
Full Name:Gerard Guevel

for my machine account I get these informations :
Unix username:GEG2400$
NT username:  GEG2400$
Account Flags:[W  ]
User SID: S-1-5-21-1957908234-1424639752-1538882281-1144
Primary Group SID:S-1-5-21-1957908234-1424639752-1538882281-513

It seems to be right for me because all sid are formed as
S-1-5-21 -  domain SID - sequence. The uid/gid are right.

So when I turn the samba server on PDC, I can connect to the domain
with my name and I can go through the shared directories on the PDC.

The problem is that Samba does not see the other servers in the domain
as if the machine sid are wrong.

If I use a psgetsid tool, I get the following sid :
SID for \\geg2400:  S-1-5-21-1090110705-1600816324-972832914
SID for \\samba3000:S-1-5-21-1957908234-1424639752-1538882281

I don't understand if machine sid on the PDC have to be formed as
user account sid S-1-5-21 -  domain SID - sequence or
must be the external domain sid ?

Thanks for any tips
Gérard


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba