Topic: Status for Samba XP clients for SME 6.0.1, 6.5 and 7.0 ?!

[arne]

Hello everybody !

I belive that the SME 6.0.1 will require a minor modification of the Windows XP client to be able to log on the XP to the Samba/Sme domain, when the SME 6.0.1 act as a Primary Domain Controller.

Don't know if this is necessary if the SME/Samba is set up as a work group member and not a PDC.

Is there anybody of you SME users who knows which installations that can be done with the Sme 6.0.1/6.5/7.0 that will not require modifications of the Windows XP clients ??

If anybody knows about installation alternatives that will permit use of unmodified Windows XP clients, please leave a message !!??

After all it is just a minor modification of the Win XP, but still it is a mod that require som data knowledge, so things are just more easy, it it is just to connect the new Windows XP PC.

What about the Windows XP Home (Not professional edition). It can not log on to a domain, but what if the Samba server is sat up like a Workgroup member, it is still possible to log on a XP Home client with individual work group acounts ? (One should believe that ?!)

(The SME servers I have sat up before has ben set up like PDC, but I guess they can be set up as work group members as well. Don't have a SME server available here at my place just now, so I can check it out. I hope that you bear over with me if I'm wrong.)

Best reg Arne.

Best Reg Arne.

[arne]

My only recent experience with Windows XP clients agaist SME/Samba is with SME 6.0.1 configured as a Primary Domain Dontroller.

On that installation I needed to make modifications on the Windows XP clients to make things to work.

I have heard rumers that there exist Sme distribution(s) where it is not required to make the Windows XP client modification.

Is there anybody that has tested some setup/configurations with Windows XP Samba clients exept for the one I have tested.

By the way .. I installed a Suse 8.1 server some months ago, and on that one the XP clients clold log into the domain without any modifications, so I know it can be done with the right Samba revision and configuration.

Arne.

[raem]

arne

> ...it is just a minor modification of the Win XP, > but still it is a mod that require som data knowledge

How much easier can it get, just double click on a reg file, not much knowledge needed there.

[FoxFriend]

You can also use a login script (domain conroler only) that set a variable, for exemple mod_xp=ok and if this variable is not set, then you appy the .reg file.
Not very diificult, doesn't it ?

[arne]

RayMichell ->

"How much easier can it get, just double click on a reg file, not much knowledge needed there."

Something I have missed ?! Think I do the thing like this eplanation on the bottom of this link. There is some more easy method ??

http://www.ccs.uky.edu/docs/samba.htm

Foxfriend ->

"You can also use a login script (domain conroler only) that set a variable, for exemple mod_xp=ok and if this variable is not set, then you appy the .reg file."

Don't understand "how". Mod to the server only and/or the client ?

Thanks  

Arne.

[arne]

Here is a shortone of the way I do it, that hopefully might be "not so smart":

Appendix A: Windows XP Setup
This supplemental page describes how to set up Windows XP Professional to connect to your server. Note that only Windows XP Professional can join a domain. Windows XP Home can still access the SME server, but these directions are not needed, and it will see the server as simply another fileshare on your network.

1. Run the regedit32 command. We will patch the registry keys to enable access to the domain login functionality of SME server.
a. Locate this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\netlogon\parameters/
b. Set "RequireSignOrSeal" = dword:00000000
c. Locate this key:  
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System\
d. Set “CompatibleRUPSecurity”=dword:1
2. Right click MyComputer, select Properties. Go to 3. Change and click on Domain and enter the workgroup/domain-name of your server.
4. Reboot and then the changes will be effective.

[raem]

The registry patch for Win XP is located in
/home/e-smith/files/server-resources/regedit/winxplogon.reg

Just copy this file to a server share & then it is easily available to transfer to each workstation by the network connection (logged on to workgroup) or floppy disk.

Then just double click on the winxplogon.reg file and the settings will be added to the Windows Registry, no need for expert knowledge & danger using regedit.

Same goes for the Win98 reg patch, win98pwdcache.reg

[arne]

Great news ! Thanks a lot ! I have allways done it in "the manual way"  

Arne.

[RobRoye]

Wow, it seems the dev team has indeed thought of everything!

Great job!

[dhardy]

Guys,

You're making this a tough job

http://your-server/server-resources/

the last / is important. It's not accessible from the interweb so I guess you _could_ add other stuff in there.

All I do is ....

1. Get new XP client
2. Complete XP install wizard
3. Connect to LAN
4. Goto http://fleable/server-resources/ (because my server is called fleable)
5. Browse to regedit folder
6. Download winxplogon.reg and double click it.

No floppies, scripts, funny permissions on ibays or mucking about with regedit or anything  

HTH

David.

[cosy]

HI
 
  Just install reg file from the server reboot
but i can't joing to the domain????

[azche24]

Hi,

but i can't joing to the domain????

Try using "root" better than "admin" when joining the domain.

Was often discussed here. Try a search, if my tip does not work.

[cosy]

Hi,

 I already try root same error unknown user or bad password.
 
 

[arne]

Can not guarantee that I remember things correctely, but I think (hope) this will work:

1. Log on from a win pc to your sme server using the free program winscp (find it with google.)

2. Log on using root and root password.

3. Find the windows registry mod file in this directory:
/home/e-smith/files/server-resources/regedit

4. Copy over this file to the win xp pc and klick on it. Then the registry will be modified.

By the way, I checked just now that the reg mod file were there on a sme 7.0 B4

Best reg Arne.

[arne]

http://winscp.net/eng/download.php

[cosy]

HI Arne,
 
  What i did exactly same. Download & run that reg file from
 http:\\server\server-resources\regedit

  Can you able to joing any XP to your SME7 B4?

[arne]

Sorry - I do not have the oportunity to test out now. All my network servers and Workstations are set up to test out Asterisk telephone server. Actually I have not tested sme 7.0 as a domain controller. (But as a work group file server, and that worked ok.)

[cosy]

hi Arne,

 It's OK. I think i'll map all the network drive using local logon Script.

 I just try with SME 6.0.1 domain, all working fine.
i think this SME 7.0 B4 may need some modifications.

[dhardy]

Cosy,

What is the exact error message you get when trying to join the XP client to the domain?

If it is an authentication error it may be something to do with the root/admin user and samba.

Have you installed any samba contribs? - the advanced workgroup contrib buggered things up for me on 6.01 .....

David.

[cosy]

HI,

 It's a fresh install of SME7 B4. I didn't install anything. Ther error msg was unknown user name or bad password.

[jumba]

...just would like to confirm that I face the same experience as Cosy.

Ther error msg is "unknown user name or bad password"

...and yes, I tried with "admin" as well as "root", - same shit.

I also tried to create a user group with the describtion "Domain Admins" as mentioned earlier on Contribs.org, but same error...

Just a thought:

Since I test with Swedish version of XP, would there be any connections to the name of the local XP Administrator account?

(Of course, this account name differs from one language edition to another in XP   )

[dhardy]

This sounds to me like the root user is not properly linked to a samba account.

This post http://forums.contribs.org/index.php?topic=16336.msg63165#msg63165 worked for me with SME6.01-Plus and the advanced workgroup contrib when all else failed ....

Anyway, I have found that adding a root samba user with the same password as your linux root account allows things to work better.

Add root user:

At root command line type: smbpasswd -a root
Enter your root password twice.

To make sure account is enabled: smbpasswd -e root

I'm guessing that the root samba user is not enabled ... if anyone can confirm this as a bug in 7b4 then please submit it to the bug tracker at sourceforge as per the stickies on the forums.

 (My 7b2 box has been sacrificed to be a testbed for sync4j on W2K - http://www.sync4j.org - or I'd have a crack at it myself).

HTH

David.

[fritzferr]

Hey all,

I've been running 7.1 with XP with no problem.  I recently started testing Longhorn with the same problems listed above.  I've done all the things listed as well, including regedit fix from the resources page, manually adjusting the registry, and doing the snbpasswd.  So far I just get the darn bad password or login.  Please help.  Very frustrated.

I just updated the server to 7.4 with some hope, but the same thing occurred.

F

[jumba]

Hello everybody!

Maybe I've found an explanation for the behavour described above (not being able to join a domain):

I used to have a very LONG password for admin/root, - something like 19 characters long.

In that situation, I vas totally unable to add a new machine account on the server from an XP-box ("join a domain")

As soon as I changed that password to a shorter one (6 characters right now") the "domain joining" suddenly started to work again....

It should be very interesting to learn from the other people with the same problem how long passwords you were using, and if there might be a (hidden) limit of the number of characters (Maybe it has to do with smbpassword, I'm not an expert here)

[jumba]

Hello again!

I've just confirmed with an experienced NT-technican that the number of characters in an SMB passord is supposed to be 15 or 16.

So my theory seems to be true, - I used 19 characters and it just didn-t work!

I don't know if this is supposed to be considered as a "bug", but shouldn't it be better to implement a maximum limit of the number of SMB passwords in SME-server???

What do you think, friends?