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