Topic: Probs with domain logon to SME 6.0.1-01 from winXP

[bluefire]

Hi!

For the past 3 months I've used my SME as a domain controller but I've just logged my workstations on to a workgroup. Works fine but now I'd like to get to use the domain controller feature so I tried to logon to the domain but got refused. I'll see if I can translate the errormessage properly from Danish :

"More than one connection to a server or shared resource at the same time by the same user with more than one username is not allowed. Disconnect all prevously connections to the server or shared resource and try again!"

I've tried to disconnect all my shares and even log off ICQ and MSN but without any luck.

I've tried to add my workstation as a user but with the same result.

Any clue?  


Rgds,

[SSBN]

Did you use the xp regerstery fix that is on sme to allow xp/2000 domain logins. Also you have to use the admin account to log the computer on the domain. Then you can log on as the user.

[bluefire]

Yes, I did use the registry fix and I've tried to logon both as admin and as my self but go luck. I get the same errormessage anyhow...  

[briank]

From memory I think net view from a dos commandline will let you see if you have a hidden connection.

[girkers]

I had exactly the same problem and the way I fixed it was to do a reboot and then immediately join the domain before doing anything else.  As I found that as soon as I even opened Explorer, bang I got that message.

I suppose you could even hold down the shift key as you boot into windows to stop your startup programs to help if a standard reboot doesn't work for you.

Just letting you know what worked for me.  

[bluefire]

I had exactly the same problem and the way I fixed it was to do a reboot and then immediately join the domain before doing anything else.  As I found that as soon as I even opened Explorer, bang I got that message.

I suppose you could even hold down the shift key as you boot into windows to stop your startup programs to help if a standard reboot doesn't work for you.

Been there, done that. No go....
Then I got another message : "The entered user does not exist!"  


Rdgs,

[Blue]

Hi,

I also experienced the domain login refusal problems, in the past with Redhat 8 and recently with SME 6.5b2. Actually it appears to be quite simple to sort if you have a clearer understanding of the mechanism involved - I think.

The principal of domain login is that the accounts are not setup on the workstation but on the server (domain controller - DC). This is for centralised management of accounts. When you first attach a workstation to the domain controller/server it needs the initial login to be that of the server administrator, i.e. "admin" in the case of SME. This generates a secure link or relationship between that workstation hardware and the server. Once this is done you normally reboot the workstation and then use any of the already setup server user accounts to login to the server.

Note: the server admin login from the workstation only happens once at the initial setup of the domain attachment. Note also that you do not setup user accounts on the workstation for the domain - only on the domain controller server.

I hope this helps.

Blue.

[bluefire]

I did get it working but I went back to the workgroup setup. I missed my simple-logon screen (my wife missed it... Since I couldn't get that and the domainlogon at the same time I preferred the simple-logon...

[felipevidal]

I found that I had to use 'root' as the username not 'admin' when prompted by Windows for the domain admin. The 'root' user has the permissions to automatically create the machine account (in the passwd file) using a built-in script in Samba.  This is necessary for the machine to be on the domain.

Also take note if you have any printer shares or running applications or services with UNC path names to the server that could cause the 'More than one connection' problem.  It essentially means that your local Windows user (non-domain) is using some resource on the server and has passed its auth information to it.  

Please note if you are using the Samba 2.2.8 that comes with SME server without updating to 2.2.11 or 3.0.7 that Samba can misbehave if the XP workastations are running SP2.  I ran the original 2.2.8 with about 10 stations on SP1 without issue.

-felipe