Topic: Samba 2.2 is missing in SME

[Craig Foster]

Following the instructions *very* carefully will get you very close to working. After that it's the full moon, ritual chicken sacrifice, etc.

As I understand it, that is why it's not in SMES 5.0000

And to demonstrate things, 2.2.1 works *very* well for me except for one thing during shutdown of W2KProSP2.

[2001/08/11 07:37:19, 0] rpc_server/srv_samr.c:api_samr_set_userinfo(672)
  api_samr_set_userinfo: Unable to unmarshall SAMR_Q_SET_USERINFO.
[2001/08/11 07:40:39, 0] rpc_server/srv_samr_nt.c:_samr_query_useraliases(2454)
  _samr_query_useraliases: Not yet implemented.
[2001/08/11 07:52:12, 0] smbd/nttrans.c:call_nt_transact_ioctl(1798)
  call_nt_transact_ioctl: Currently not implemented.
[2001/08/11 07:52:13, 0] rpc_server/srv_samr_nt.c:_samr_query_useraliases(2454)
  _samr_query_useraliases: Not yet implemented.
[2001/08/11 08:30:16, 0] smbd/open.c:open_directory(1044)
  open_directory: unable to create craigf/Application Data/Microsoft/Word/STARTUP. Error was No such file or directory
[2001/08/11 08:30:16, 0] smbd/open.c:open_directory(1044)
  open_directory: unable to create craigf/Application Data/Microsoft/Office/Recent. Error was No such file or directory
[2001/08/11 08:30:16, 0] smbd/open.c:open_directory(1044)
  open_directory: unable to create craigf/Application Data/Microsoft/SystemCertificates/My/CTLs. Error was No such file or directory
[2001/08/11 08:30:16, 0] smbd/open.c:open_directory(1044)
  open_directory: unable to create craigf/Application Data/Microsoft/Internet Explorer/Quick Launch. Error was No such file or directory
.
.
.
[2001/08/12 03:45:27, 0] rpc_server/srv_netlog.c:api_net_sam_logon(208)
  api_net_sam_logon: Failed to marshall NET_R_SAM_LOGON.
[2001/08/12 03:45:27, 0] rpc_server/srv_pipe.c:api_rpcTNP(1215)
  api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.
[2001/08/12 03:45:50, 0] rpc_server/srv_samr_nt.c:_samr_query_useraliases(2454)
  _samr_query_useraliases: Not yet implemented.


And it comes up on the W2K machine as "Unable to save profile. Another program may be using files on your machine...etc"

Could you image the flak the SMES team would get if everybody with a Samba 2.2.1a problem would ask for help, also considering the move to shore-up income for Mitel?

[WXP]

Here are some new stuff !

Someone told me to reinstall Windows 2000. I just did it..
At the end of the installation there was the "Network Identification Wizard"
I choosed the option : "This computer is part of a business network, and I
use it to
connect to other computers at work."
Then : "My compagny uses a network with a domain."
It asked me for my username and password and the domain.
I entered "pbrossin" / "mypassword" / server (which is the workgroup name
under e-smith)
And it told me : "Windows cannot find an account for your computer on the
SERVER domain."
And it asked me for a "Computer Name" and a "Computer Domain"
I put "WXP" and "SERVER"
Then it told me : "Type the name and password of an account with permission
to join the domain."
I entered : "root" / the password I choosed with "smbpasswd root" / and the
domain "SERVER"
it told me : "Your computer could not be joined to the domain because the
following error
occurred : The account used is a computer account. Use your global user
account or local user
account to access this server."

So it's not working... I installed a Fresh 4.1.2 server and upgraded Samba to
2.2.1a as dan brown say in his HowTo and Windows just got installed !

So I thought.. Humm maybe the server does not have an account for my
computer
I went on my server and typed "./machine-account-create
create-machine-account WXP"
and it told me : "Use of uninitialized value in string eq at
./machine-account-create line 47.
Account WXP is not a machine account; create account failed."
So I tried with wxp and not WXP
"Account wxp is not a machine account; create account failed."
no more "use of initialized ......"
That's a start..

I didnt go farther... I tried under Windows, after the installation but I
still get the error that it's a computer user account bla bla... or the Credentials error..

Any idea ?

Thank you !

[Kelvin Lee]

Hello again.

Personally, when I reinstalled W2K Pro, I did not allow it to join the domain at the end of installation (at first boot after install). Instead, I chose to just configure the W2K Pro machine to be part of the default "WORKGROUP" workgroup. After I finished installing the base W2K Pro, I went through and did all the drivers, etc. followed by SP2. After all that, THEN I rebooted and from the desktop, right-clicked My Computer -> Properties -> Network Identification -> Properties.

Select the Domain radio button, then typed in my Domain name,  and hit OK. However, since I did this a while back, I can't remember whether I used the root account or the admin account as the account with permission to join the network. Try them both, I suppose. After that, it works straight away -> ie. I got the magical (and elusive) Welcome to the XXXXXX domain message.

Best of luck !

Unfortunately, some of this is still pretty much plug and pray at the moment

[WXP]

>
> Try them both, I suppose. After that, it works straight away
> -> ie. I got the magical (and elusive) Welcome to the XXXXXX
> domain message.
>

I will never have that fucking message... Windows 2000 doesnt care if you did the Service Pack update... it doesnt care if you try to join a domain at first boot or when you are installing it... it doesnt care of any drivers...

I just reinstalled my network !! and properly...

What I am trying to say is that something is missing on the server side.. It's not working any better now.

I even tried to install SME5 and the samba upgrade and it didnt work.

I dont think the Service Pack upgrade does anything in the domain problem.
Neither when you are trying to join it..

Damn if I could ask god why is wrong !!!! I'm fed up with that @!#$ now... really....

I think I'm gonna install a NT4 PDC and try to connect my computer to it.. if it works, it's a samba or e-smith problem...

[Kelvin Lee]

> I will never have that fucking message...

Like you, when I couldn't get my W2K machine to logon to the e-smith domain originally,  I was fairly dissappointed (yes, dissappointed but not totally unprepared for it because, I can remember back when NT 4 PCs could not logon to samba servers either).

> Windows 2000 doesnt care if you did the Service Pack update... it doesnt care
> if you try to join a domain at first boot or when you are installing it... it doesnt
> care of any drivers...

Aahh yes, W2K doesn't care.... but then again, we're not talking about a W2K or an NT 4 Domain either now are we ....

In any case, if you read my post properly, I did not say you HAD to do it this way. I only said that this is the way I did it.


> I just reinstalled my network !! and properly...
>
> What I am trying to say is that something is missing on the server side.. It's not
> working any better now.

And I have no reason to not believe you.

> I dont think the Service Pack upgrade does anything in the domain problem.

Yes it does. If you are using SP2, you MUST use the latest samba upgrade, and yes, I know you have put it in.


> Neither when you are trying to join it..

Cannot confirm this. Like I said, this is NOT a W2K or NT 4 PDC. My first post clearly indicated that my original W2K machine had absolutely no problems loging on to either an NT 4 PDC or a W2K Server. However, it will not log on to the e-smith server even after the samba upgrade not matter which How-To I followed. It wasn't until I reformatted and reinstalled W2K that it successfully logs on to e-smith now (Without changing e-smith in anyway since my initial failed attempts).


> I think I'm gonna install a NT4 PDC and try to connect my computer to it.. if it
> works, it's a samba or e-smith problem...

Oh, I'm pretty sure it's a samba issue (Samba team, please don't flame me). Considering Microsoft was never too open or forthcoming with the internal workings of their networking system to begin with, it's just about a miracle at all that you are even able to connect and share files from a Linux PC let alone make it emulate a domain controller - hats off to you Samba team. After all why should W2K's logon pre-SP2 be any different to it's logon after SP2, yet it is ......


All I can say is persistence and patience worked for me. That is not to say that it will for you, of course, but a little bit of both really does not hurt.

[WXP]

>
> Aahh yes, W2K doesn't care.... but then again, we're not
> talking about a W2K or an NT 4 Domain either now are we ....
>

I'm downloading it....
 
> In any case, if you read my post properly, I did not say you
> HAD to do it this way. I only said that this is the way I did
> it.
>

I know I know... I'm just trying to know where the problem..
I dont want to try upgrading stuff and reinstalling.. I need that PDC really fast...

>
> All I can say is persistence and patience worked for me. That
> is not to say that it will for you, of course, but a little
> bit of both really does not hurt.
>

You know, it's been a long while I'm trying to do this.. so i think I wont have patience anymore .. since it's doesnt work... it's doesnt WANT to work because some people like you just got it working...

I'm lost in the PDC world... oouuuuuhhhhhhhh

[WXP]

[root@server /]# /sbin/e-smith/db accounts set wxp machine
[root@server /]# /etc/e-smith/events/actions/machine-account-create
machine-create wxp
Changing password for user wxp
Locking password for user wxp
passwd: Success
Added user wxp$.

And guess what !!! IT WORK !!!!!!!!!!

YEESSS FINALLY I GOT IT WORK !!!

YEAH YEAH YEAH YEAH YEAH YEAH YEAH
YEAH YEAH YEAH YEAH YEAH YEAH YEAH
YEAH YEAH YEAH YEAH YEAH YEAH YEAH
YEAH YEAH YEAH YEAH YEAH YEAH YEAH
YEAH YEAH YEAH YEAH YEAH YEAH YEAH
YEAH YEAH YEAH YEAH YEAH YEAH YEAH
YEAH YEAH YEAH YEAH YEAH YEAH YEAH
YEAH YEAH YEAH YEAH YEAH YEAH YEAH
YEAH YEAH YEAH YEAH YEAH YEAH YEAH
YEAH YEAH YEAH YEAH YEAH YEAH YEAH

oh yeah

Thanx to Dan Brown because it took time to help !!!! THANK YOU VERY MUCH DUDE !!

And thanx to every people that told me that It will work someday !!!

You were right Kevin !! LoL

[Dan Brown]

Cool, glad to hear it's working!

[WXP]

I just have one problem.

When I log off, I get this error :

Windows cannot update your roaming profile. Contact your network administrator (Yes i am
DETAIL - The process cannot access the file because another process has locked a portion of the file.

Does it means my files are saved localy and not on the server ?!

Thanks

[Dan Brown]

Your computer is trying to save your profile (desktop settings, etc.) on the server, but didn't succeed.  You can either use local (non-roaming) profiles (don't know how to do this), or set strict locking=no in smb.conf.

[WXP]

> or set strict locking=no in smb.conf.

what does this option do ?

And why does he have problem to save my profile.
That's why I wanted a PDC
I want to be able to format my HD and to have my background picture, internet explorer favorites.. everything back
or to be able to log on any computer in my house and have my profile..

[Craig Foster]

To convert a roaming profile to local, right-click on My computer, choose properties from the menu, select the User Profiles tab. This should list the profiles on your machine.

Choose the DOMAIN\username (which should already mention Roaming) and click the Change-Type button at the bottom of the dialog box.

Done.

Regards,

Craig Foster

[WXP]

What does it change ?

If I format my computer.. and then relog to my account, am I gonna have all my stuff... like internet explorer favorite and my desktop background ?

Can I log on another computer which is connecte to the domain and have my stuff as well ?

Or are they saved locally ?

Thanx

[Oreo]

There's something strange with samba and my computer...

It says the same error but it saves the files on my server anyways...

Could you please help me to get rid of this box?

PS: I installed Service Pack I, and also it takes like 10 to 20 seconds to log in and off, but at the school where I go, they use a Win 2000 Server, and it takes like 5 seconds to do the same...