Hi Monte, ---- Monte Milanuk wrote:
[snip...] copy of O'Reilly's Using Samba,
Nice. BUT Samba 2.0.5a related. Although it is "THE REFERENCE", and you can't work it without it.
[snip...] Win98 client can't even find itself on the LAN w/o NetBEUI. Is this just something I am doing wrong? If so, what?
Detail LAN setup please, after on next post, i will tell you some on NetBEUI. Which are the machines involved, hardware, OS's and versions included?? NetBEUI is the clue, as far as _windoze_ knows.
Next, I usually can get thru the 'smbclient -L -U% localhost' test. I say usually, because the last time, I couldn't, getting a message that 'Connection to -U% failed'.
NetBEUI related, Sir.
...error 53...
...error 59...
_windoze must boot_ warning...
Mixed NetBEUI and TCP/IP stacks on the _windoze_ bitch. Erratically _windoze_ behavior resulting, i can see it.
..._SAMBA_... Unfortunately, I didn't capture those.
No need.
lot of lines like this:
[2000/08/08 21:09:37, 1] smbd/files.c:file_init(216) file_init: Information only: requested 10000 open files, 1014 are available. [2000/08/08 21:09:37, 1] smbd/server.c:main(641) smbd version 2.0.7 started. Copyright Andrew Tridgell 1992-1998 [2000/08/08 21:09:37, 1] smbd/files.c:file_init(216) file_init: Information only: requested 10000 open files, 1014 are available.
Normal log msgs after all, Samba 2.0.7 always reacts equal and traces his/her startup activity.
Not what I'd expect to see in the log file while I'm just testing out the initial test setup!
Figure out, there has been a lot of changes and enhancements on Samba 2.0.7, including high performance updates, and new msgs also. This is the release to use, trust me.
Any ideas?
Monte
Yes but first let the "dirty sonofagun" (as you posted), go back to Samba 2.0.7 and do not desperate, is much easier than you can see it now.
I figured out that the problem w/ the 'smbclient -L -U% localhost' was the syntax ... should be 'smbclient -L localhost -U%.
Good.
I removed 2.0.7, and reinstalled 2.0.6, and now the dirty sonofagun won't fire up swat, telling me that:
400 Server Error
chdir failed - the server is not configured correctly
Aarrggghhh!!!! I have now wasted over 4.5 hrs on this, w/ absolutely no progress. I am probably going to download the source and try it that way, unless anyone has any wisdom to share.
Do not use the sources, just use SuSE rpm's and do not bother more. Result of mixed Samba versions, thought, how did you downgrade your Samba, did you do it manually with _rpm_ or just using YaST(1)?? Post small snip of your SWAT lines on /etc/inetd.conf and on /etc/services. You can do, as root: # cd /etc # grep swat * Snip the preceding garbage, and post the _swat_ related, they are no more than 5 lines. [TIP] Although you must have on your /etc/smb.conf: [global] ... encrypt passwords = Yes ... On some share also: [share] browseable = Yes Or leave it without the "browseable =" parameter (defaults to "Yes") for _windoze_ to see some Samba share, or the Samba server at all on the WorkGroup. Without this tip it won't work, it will not be visible on the Network Neighborhood from the _windoze_ side. Use _smbpasswd_ and setup users/encrypted passwords on the Linux side.
Thanks for your time,
You are welcome, Sir.
Monte
-- HTH Best regards, Eduardo Carriles [-- Better a smile than a flame --] (Long time SuSE-Linux [preferred distro] user). [-- Se me nota mucho? -- Notices me much?] [-- Have a lot of fun...] -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq