Log on problems since update from 2.2.12 to 3.0.10 - SMB

This is a discussion on Log on problems since update from 2.2.12 to 3.0.10 - SMB ; Hi,
I want to move from Samba 2.2.12 to 3.0.10. I downloade the 3.0.10
sources and compiled them (Solaris 8). Everything went fine. After the
install, I tested the new 3.0.10 Samba with the old smb.conf from 2.2.12
(the docs ...

Log on problems since update from 2.2.12 to 3.0.10

Hi,

I want to move from Samba 2.2.12 to 3.0.10. I downloade the 3.0.10
sources and compiled them (Solaris 8). Everything went fine. After the
install, I tested the new 3.0.10 Samba with the old smb.conf from 2.2.12
(the docs say this should work). I could not log in anymore.

I switched back to 2.2.12 and tried the 3.0.10 install on a Suse Linux
8.0 - with the same results. I used most parts from the solaris
smb.conf.

This is the Samba config of the Linux sytem. It acts as samba server,
and later for testing as client too.

The server is not member in our company domain EMEA. At the moment it is
not possible to use 'security = domain', so we use 'security = server'.
The server is in the workgroup ERS, witch is the name of our department.
Authentication happens against the EMEA password server with the
UID/PASS users have in the EMEA domain. Mapping between the unix UIDs
and domain UIDs is done with the option 'username map'. This worked fine
with 2.2.12.

I did the tests on the linux system (both client and server).
ralfgro is my EMEA domain account, rg the local unix account.

If I change workgroup in the smb.conf file to EMEA it works. But the
server should stay in the ERS workgroup. Users always set the
workgroup/domain name during the login process. Most of the windows
standard clients are in the EMEA domain, so this is no problem.

This worked fine in 2.2.12. Have there been any changes in Samba 3.x.x
that could be important in this case? I know that Samba 3 comes with
winbind, but since the server is not member of the EMEA domain, I can't
use it (or am I wrong in this?).