[SLE] Samba 2.0.7 from SuSE Updates broken? (or just me?)
Hello, all. I am trying to set up Samba on my local network. I have both a hard copy of O'Reilly's Using Samba, and the updated html version that came w/ the v.2.0.7 that I downloaded from ftp.twoguys.org from the suse 6.4 update directory. Which makes this all the more frustrating. I have walked thru this as closely as I can, at least twice, and I am a) no closer than I was when I started to having an operational SMB network, b) not really sure about where things are going wrong; they seem to not work one time, work the next, w/ no real changes, c) perplexed by the log entries. I have verified that yes, my lan does work. I can ping by name and ip address from linux to windows, and windows to linux. I can use nfs, vnc, telnet, ftp, etc around the network, so tcp would seem to work. The first problem comes about w/ the Win98 client, and isn't really related. The book says to get rid of NetBEUI if at all possible, but my Win98 client can't even find itself on the LAN w/o NetBEUI. Is this just something I am doing wrong? If so, what? 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'. testparm didn't give any errors; it shouldn't since I created the /etc/smb.conf w/ SWAT. Assuming I get thru that, I eventually manage to get thru the 'smbclient '\\ishamael\test'' test, w/ a passwd prompt. Then the 'net use * \\ishamael\test' trial gave me an error 53, 'Cannot Locate specified computer' the first two times, then an error 59 '... Must reboot computer' message the next two times. I haven't made it that far since. When I did get the error 53, it seemed to indicate a name service issue, so I went to the section on Troubleshooting w/ nmblookup, and tried 'nmblookup -B ishamael __SAMBA__, and the messages I got didn't match the book, but didn't really seem like error messages. Unfortunately, I didn't capture those. The reason I think there may be something wrong w/ the software, or at least the setup on my box, is the /var/log/samba file, which contains a 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. Not what I'd expect to see in the log file while I'm just testing out the initial test setup! Any ideas? Monte -- 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
Quick update: I figured out that the problem w/ the 'smbclient -L -U% localhost' was the syntax ... should be 'smbclient -L localhost -U%. but my concern about the log entries remains. 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. Thanks for your time, Monte -- 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
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
Eduardo Carriles wrote:
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??
Internet <--->[shaitan.inet]<--->[10/100M Switch]<--->[lanfear.inet] | [ishamael.inet]<--------+-------->[sammael.inet] | [asmodean.inet]<--------+-------->[demandred.inet] Relevant host data: haitan.inet OS: FreeSCO 0.26 Use: Firewall/Gateway IP: 10.0.0.1 on eth0 H/W: Celeron 266 w/ 64M RAM, 3.2G HD, 3Com 905B TX nic lanfear.inet OS: Win98 Use: Kid's games, M$ Word, ClipArt, etc. IP: 10.0.0.2 H/W: Celeron 400 w/ 64M RAM, 10G HD, Netgear FA310TX nic HP DeskJet 722c sammael.inet OS: Dual-boot Win98/SuSE 6.4 Linux Use: Testing questionable (i.e. alpha-beta grade) software IP: 10.0.0.3 H/W: PII-300 w/ 64M RAM, 6G HD, needs new nic, 3Com pcmcia modem ishamael.inet OS: Dual-boot Win98/SuSE 6.4 Linux Use: Main day2day workstation, gaming box IP: 10.0.0.4 H/W: PIII-500 w/ 384M RAM, 10G HD, onboard nic (905B), HP LaserJet 2100 asmodean.inet OS: SuSE 6.4 Linux Use: Teenager's thrash box IP: 10.0.0.5 H/W: Celeron 266 w/ 64M RAM, 3.2G HD, Netgear FA310TX nic demandred.inet TBD, reserved for spare PII-400/128M/24G server Plan to have the Win98 box serve up the DeskJet printer to the other hosts, and initially have ishamael serve the laserjet to the lan, as well as a bit of drive space. Eventually, will migrate to using server to serve laserjet and drive space to the lan, among other things.
NetBEUI is the clue, as far as _windoze_ knows. 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.
Once I went back to Samba 2.0.7, SWAT is working fine.
[TIP] Although you must have on your /etc/smb.conf: [global] ... encrypt passwords = Yes ...
I copied the default /etc/smb.conf that the SuSE rpm installed, and used SWAT to create a basic smb.conf file as per the book [global] workgroup = INET netbios name = ISHAMAEL server string = SuSE Linux Workstation encrypt passwords = yes wins support = yes [test] comment = For testing only, please. path = /pub/export/samba/test I added the netbios name, since according to what I could read, it shouldn't matter, as it would default to that anyway, as that's whats set up in the dns on shaitan. The book makes it sound like you shouldn't use wins support if you just have a samba server and no NT servers, but the Samba section in the IBM Redbook on SuSE/Netfinity serverss set it on. In my case, it didn't make any difference (and I did make sure to go back and enable wins support on lanfear, and supply the address to ishamael, and reboot) An interesting sidenote: I tried this using the original /etc/smb.conf that came w/ the package, just adding the [test] share again, this time w/ a path of '/tmp', which allows me to do the 'smbclient '\\ishamael\test' ' successfully. Otherwise, w/ the original [test] share, I'd get the following error: Domain=[INET] OS=[Unix] Server=[Samba 2.0.7} tree connect failed: ERRSRV - ERRinvnetname (Invalid network name in tree connect) How the heck is this possible w/ such a simble share?
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.
Did this, but when I did (as root) 'smbpasswd -a monte', and entered a passwd for user monte, when I went to use smbclient as monte, it balked until I did (as monte) 'smbpasswd', and entered the old passwd, then entered and confirmed the new passwd (which was the same as the old one). Weird.
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
-- 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
Hi Monte and every one reading, On previous posts i said that the O'Reilly's "Using Samba" book is Samba 2.0.5a related. And this book is "The Reference(tm)". Every one who owns the book knows this. We are now on Samba 2.0.7. [Useful Samba documentation ahead] It is very useful to have some more _docs_ available that explain the _differences_ between 2.0.5a and the next releases, as they are 2.0.6 and the current 2.0.7. [General contents] It is located on the _whatsnew_ pages at samba.org. They include the _announce_ and the [WHATS NEW IN Samba 2.0.x] info. For the _whatsnew_ part it includes: 1- New Documentation in ..., if there are some. 2- Related Issues. 3- New/Changed parameters, which are completely necessary. 4- Changes between releases, which explain some of the issues you might have. 5- Changes in 2.0.x wich also explain a lot. 6- more info... [Pertinent locations] are: http://de.samba.org/samba/whatsnew/samba-2.0.5.html http://de.samba.org/samba/whatsnew/samba-2.0.5a.html http://de.samba.org/samba/whatsnew/samba-2.0.6.html http://de.samba.org/samba/whatsnew/samba-2.0.7.html ** Worth print them for detailed review (you need them). As of the "de.samba.org" server you can find the Worldwide mirrors on the _mirrors_ link that appears on page, or on the www.samba.org main page, all of them contain the same material. The rest of the link as: /samba/whatsnew/... is maintained. [Small bits of New/Changed parameters] [Samba 2.0.5a] - security mask (new) - force security mode (new) - directory security mask (new) - force directory mode (new) - level2 oplocks (new) [Samba 2.0.6 ] - wins hook (new) - debug hires timestamp (new) - debug pid (new) - debug uid (new) - preexec close (new) - rootpreexec close (new) - mangle locks (removed) * Syntax for the Linux-specific _smbmount_ (changed) [Samba 2.0.7] * New Documentation in 2.0.7 announcing on- line access from SWAT interface to the O'Reilly's "Using Samba" _donated_ book, as HTML. (Exact copy of book, thus Samba 2.0.5a related.) * Windows 2000 Issues (5) resolved. - utmp (new) - utmp dir (new) - utmp hostname (new) - utmp consolidate (new) - wtmp directory (new) - inherit permissions (new) - write cache size (new) - source environment (new) * SWAT Ability to delete users added. * Roving profile behavior finalized (using the "logon home" parameter instead of the "logon path" parameter) changed to default. [Warning] You must take into account that the _changed-to-default_ parameters will change the behavior of Samba on the release you use. Check them. [Clue] Default parameters, which you did not change, will not appear on your /etc/smb.conf, BUT if you upgrade to another release and maintain your params, you need to double check, and with SWAT open and save, as to see which ones appears on your config file, and what effect they cause. [Comments] It is a powerful and wonderful product, you will need some time to understand and dominate it, if you have some background on _windoze_ net will be of great help. It is also very well documented on- line. You can make a basic setup with it very quick, implemented _defaults_ work without a charm. To fully dominate it you will need profound skills on _windoze_ and test much. And last but not least, you will acquire knowledge that $MS did not write out at all. Have a nice day!! =`8) -- 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
Hi Monte and all friends reading, And now we go to the NETBEUI/NetBios things. [NETBEUI/NetBios things] 1- NETBEUI is not routable. 2- NETBEUI was designed by IBM for small, one net segment only. 3- $MS maintains it with the same capabilities. 4- It is small and efficient, necessary only for w95. 5- w98 uses TCP/IP for this, thus using a routable protocol. 6- The only inherent protocol necessary for _windoze_ and underlying the $MS nets is NetBios, designed also by IBM. 7- NetBios works packed under TCP/IP, but if you make a mistake on the $MS net config, and disable it, you would not see any $MS server on your _neighbor hood_. 8- Samba uses only TCP/IP, and it was a great a necessary decision that $MS also followed on intentions, as of W98, but maintains the protocol as they need. 9- NETBEUI degrades _shares_ access and performed if used, thus affecting Samba performance also. 10- NETBEUI if used in coincidence with TCP/IP to access _shares_ it confuses much $MS, in particular w95 and w98. 11- Simultaneous NETBEUI and TCP/IP make sometimes disappear the SMB/CIFS servers and sometimes _shares_ inside, because windoze caches much time (performance on access and retrieval related), while some times you see them as magic. 12- NetBios names names are different from _host_ names, but you can make it the same, and this is the recommended way, and you can make them to auto resolve. 13- NetBios names are resolved by WINS, or by a _broadcast_ search that you can see with some hard or soft tool as _tcpdump_, are performed packed on TCP/IP, or inserted on your _lmhosts_ file. (Linux /etc/lmhosts, windoze \windows\lmhosts) 14- $MS _workgroup_ names resolve on their own as WORKGROUP.domain under TCP/IP also. 15- _host_ names are resolved by a DNS or inserted on your _hosts_ file. (Linux /etc/hosts, windoze \windows\hosts) 16- _hosts_ file is always needed if you do not have a properly configured DNS. 17- The only real need, if you do not need WINS because you do not have NT's on your deploy, is to use a DNS or _hosts_ setup, you will not need WINS/lmhosts at all. 18- There is much more, but this small bit is all that you will need for now. And those where the [NETBEUI/NetBios things] that i referred on previous post. Beg your pardon if some conceptual mismatch appears. Understand?? =`8) [Monte related ahead] ---- Monte Milanuk wrote:
Eduardo Carriles wrote:
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??
Internet <--->[shaitan.inet]<--->[10/100M Switch]<--->[lanfear.inet] | [ishamael.inet]<--------+-------->[sammael.inet] | [asmodean.inet]<--------+-------->[demandred.inet]
Relevant host data:
shaitan.inet lanfear.inet sammael.inet ishamael.inet asmodean.inet demandred.inet TBD, reserved for spare PII-400/128M/24G server
Nice Linux and FreeSCO included deploy, powerful. You know your business!! =`:) Can't see any NT on your setup, that makes things much easier.
Plan to have the Win98 box serve up the DeskJet printer to the other hosts, and initially have ishamael serve the laserjet to the lan, as well as a bit of drive space. Eventually, will migrate to using server to serve laserjet and drive space to the lan, among other things.
Thus your Samba needs, isn't it??
NetBEUI is the clue, as far as _windoze_ knows.
As you can deduce.
Once I went back to Samba 2.0.7, SWAT is working fine.
You got the grip, thought.
I copied the default /etc/smb.conf that the SuSE rpm installed, and used SWAT to create a basic smb.conf file as per the book
Follow my previous post on "Useful Samba documentation [was:..." at: http://lists.suse.com/archives/suse-linux-e/2000-Aug/0928.html or on your own file, if you maintain it. It has a necessary [Clue] there.
I added the netbios name, since according to what I could read, it shouldn't matter, as it would default to that anyway, as that's whats set up in the dns on shaitan. The book makes it sound like you shouldn't use wins support if you just have a samba server and no NT servers, but the Samba section in the IBM Redbook on SuSE/Netfinity serverss set it on. In my case, it didn't make any difference (and I did make sure to go back and enable wins support on lanfear, and supply the address to ishamael, and reboot)
See the [NETBEUI/NetBios things] on top.
An interesting sidenote: I tried this using the original /etc/smb.conf that came w/ the package, just adding the [test] share again, this time w/ a path of '/tmp', which allows me to do the 'smbclient '\\ishamael\test' ' successfully. Otherwise, w/ the original [test] share, I'd get the following error:
Domain=[INET] OS=[Unix] Server=[Samba 2.0.7} tree connect failed: ERRSRV - ERRinvnetname (Invalid network name in tree connect)
May be some protocol confusion. Give a try to _nmblookup_ it helps much, and it is on pages 278,372 of your lovely "Using Samba" [The Reference(tm)] book.
How the heck is this possible w/ such a simble share?
Defaults, see defaults, they are always important.
Use _smbpasswd_ and setup users/encrypted passwords on the Linux side.
Did this, but when I did (as root) 'smbpasswd -a monte', and entered a passwd for user monte, when I went to use smbclient as monte, it balked until I did (as monte) 'smbpasswd', and entered the old passwd, then entered and confirmed the new passwd (which was the same as the old one). Weird.
This one you will have to study a bit. -- 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
participants (2)
-
eduardo.carriles＠teleline.es -
milanuk＠yahoo.com