I'm trying to setup a RH5.2 Linux PC with samba-1.9.18p10. I want it to share its disk space with NT clients, ultimately using password encryption. I'm testing my setup with a NT4SP3 client. Initially: The client has IP# 152.1.61.175, registered to kaon.csc.ncsu.edu; its TCPIP has DNS for Windows resolution enabled, and has no WINS servers. The server has IP# 152.1.61.159, which is registered to backpack.csc.ncsu.edu. I did the following: * Deleted the logs in /var/log/samba to start afresh. * Copied the following into inetd.conf from http://metalab.unc.edu/LDP/HOWTO/SMB-HOWTO-4.html> netbios-ssn stream tcp nowait root /usr/sbin/smbd smbd > netbios-ns dgram udp wait root /usr/sbin/nmbd nmbd* Copied /usr/doc/samba-1.9.18p10/examples/smb.conf.default to /etc/smb.conf * Commented out> ; load printers = yessince none are attached to the Linux box. * Changed> ; guest account = pcguestto> guest account = guestwhich has> guest::508:508:guest:/home/guest:/bin/bashin /etc/passwd * Commented entire [printers] block * Uncommented entire [tmp] block * Ran> killall -HUP inetdas stated in my inetd.conf. * I ran the diagnostics, logged in as root. I pass tests 1-7. Note that I pass test 7: "smbclient '\\BACKPACK\TMP'" with no user set (i.e. as current user == root), with -U guest, and -U tlroche. In each case I get> Added interface ip=152.1.61.159 bcast=152.1.255.255 nmask=255.255.0.0 > startlmhosts: Can't open lmhosts file /etc/lmhosts. Error was No suchfile or directory and am prompted for a password (except as guest). * Test 8: On the PC type the command "net view \\BACKPACK". I get> System error 5 has occurred. > Access is denied.Note that \\BACKPACK was used with success in steps 2, 3, 4, and 7. Also, I am able to net view NT hosts. * I assume there's a problem with name resolution. As previously mentioned, the client's TCPIP is configured with no WINS server, but with DNS and LMHOSTS lookup enabled. I add the line> 152.1.61.159 backpackto c:/WINNT/system32/drivers/etc/hosts, import LMHOSTS, and restart the client. No change: I get the same system error 5. I also try> net view \\backpack > net view \\backpack.csc.ncsu.edugetting the same error. Note that if I> ping backpackI get> Pinging backpack [152.1.61.159] with 32 bytes of data:> Reply from 152.1.61.159: bytes=32 time<10ms TTL=64until ^C. * I try using WINS. I change> ; wins support = yesto> wins support = yesI set the PC to use 152.1.61.159 (the IP# of the Samba server, backpack) as its primary WINS server. I run> killall -HUP inetdon the server, and restart the client. I repeat tests 1-7 for sanity, and pass all. I fail test 8 identically. * I copy the client's c:/WINNT/system32/drivers/etc/hosts, which has> 127.0.0.1 localhost > 152.1.61.159 backpackto /etc/lmhosts, adding the line> 152.1.61.175 kaonfor completeness. I> killall -HUP inetdNo change: I pass tests 1-7, and fail test 8. Can anyone diagnose the problem? I can send testparm.out and smb.conf as desired. Please note again that my objective is simply to share disk on the Linux Samba server, hopefully using password encryption (though I have not yet enabled that). I don't understand why everything works using smbclient and nmblookup, but nothing works from a real NT client. Your assistance is appreciated, Tom_Roche@ncsu.edu
Mr. Kuehn never works by us. Please actualize your Mail-Listings. Thank you samba@samba.org schrieb:> Your posting to list SAMBA was rejected. > Reason: message size limit exceeded (maximum allowed: 40000 bytes) > The first few lines of your message are included herein for reference: > > Mr. Kuehn never works by us. Please actualize your Mail-Listings. > > Thank you > > samba@samba.org schrieb: > > > SAMBA Digest 2015
David Lee <T.D.Lee@durham.ac.uk> wrote:> Samba 2.0.0 on Solaris 2.5/sparc > 14,000 users (samba released to small group, but intend to release to all)Send me mail re sizing: I have an estimating model.> When editing a WORD document (or Excel, and probably others), the revised > file written back to the UNIX home directory loses its original ownership, > group-ownership and permissions (modes) and gets a default set (me, my > primary group, 644).This can be addresses with force create mask: Word and friends edit files by first renaming the input file to .bak, and then creating a new output file and filling it with edited output. The creation tends to take permissions off (windows doesn't grok such), so you need to "force" them on. Case 1: the user is of the "right" group for sharing. Add "force create mask = 0660", which will or in the bits for rw-rw---- Case 2: the user's primary group is foo, but you want the file's group to be bar. Use the force create mask, and either use g+s on the directory or "force group = bar" in the smb.conf. These options can be set on a share-by-share basis, so you can tune them a bit.> Supplementary question: Any ideas what other solutions, (e.g. TAS, Sun's > "Project Cascade" or Network Applicance Filers) do in this situation?Blush: I don't know. --dave -- David Collier-Brown, | Always do right. This will gratify some people 185 Ellerslie Ave., | and astonish the rest. -- Mark Twain Willowdale, Ontario | http://java.science.yorku.ca/~davecb Work: (905) 477-0437 Home: (416) 223-8968 Email: davecb@canada.sun.com
When the world was young, "Tom Roche" <tom_roche@ncsu.edu> carved some runes like this:> I'm trying to setup a RH5.2 Linux PC with samba-1.9.18p10. I want it > to share its disk space with NT clients, ultimately using password > encryption. I'm testing my setup with a NT4SP3 client.I have a few more questions:> The client has IP# 152.1.61.175, registered to kaon.csc.ncsu.edu; its > TCPIP has DNS for Windows resolution enabled, and has no WINS servers. The > server has IP# 152.1.61.159, which is registered to backpack.csc.ncsu.edu.Are you saying the client is pointed to a DNS server but no WINS server? WINS resolution should be disabled if there's no WINS server to point to.> * I ran the diagnostics, logged in as root. I pass tests 1-7. Note > that I pass test 7: "smbclient '\\BACKPACK\TMP'" with no user set > (i.e. as current user == root), with -U guest, and -U tlroche. In > each case I get > > > Added interface ip=152.1.61.159 bcast=152.1.255.255 nmask=255.255.0.0 > > startlmhosts: Can't open lmhosts file /etc/lmhosts. Error was No such > file or directoryWith no WINS server, you should have an /etc/lmhosts file on the samba box that looks something like this: IP# backpack IP# kaon ... The client lmhosts should probably have the preload thing after the samba box: IP# backpack #PRE IP# kaon ...> and am prompted for a password (except as guest). > > * Test 8: On the PC type the command "net view \\BACKPACK". I get > > > System error 5 has occurred. > > Access is denied.What about Net Use? Even though Net View doesn't work, it doesn't mean mounting a share should necessarily fail.> * I assume there's a problem with name resolution. As previously > mentioned, the client's TCPIP is configured with no WINS server, but > with DNS and LMHOSTS lookup enabled. I add the line > > > 152.1.61.159 backpack > > to c:/WINNT/system32/drivers/etc/hosts, import LMHOSTS, and restart the > client. No change: I get the same system error 5. I also try > > > net view \\backpack > > net view \\backpack.csc.ncsu.edu > > getting the same error.Does the samba box show in the browse list when you just "net view" with no hostname?> * I try using WINS. I change > > > ; wins support = yes > to > > wins support = yes > > I set the PC to use 152.1.61.159 (the IP# of the Samba server, > backpack) as its primary WINS server. I run > > > killall -HUP inetd > > on the server, and restart the client. I repeat tests 1-7 for > sanity, and pass all. I fail test 8 identically. > > * I copy the client's c:/WINNT/system32/drivers/etc/hosts, which has > > > 127.0.0.1 localhost > > 152.1.61.159 backpack > > to /etc/lmhosts, adding the line > > > 152.1.61.175 kaon > > for completeness. I > > > killall -HUP inetd > > No change: I pass tests 1-7, and fail test 8.I'm still not sure; did you put an lmhosts file on the samba box, or just on the client? Also, you can change the lookup order on the samba side (name resolve order) and on the linux side (see /etc/nsswitch.conf). Also, RedHat has a few issues with loopback vs. localhost in /etc/hosts, and I would put the hostname (kaon) first after the IP address, *then* the FQDN (see above for the lmhosts). Finally, I can Net View all win95 boxes and the samba box by name from the NT box, but a can't Net View the NT box from either win95 or smbclient (and I stil don't know why...). Hope this helps, Steve **************************************************************** Stephen L. Arnold Senior Systems Engineer ENSCO Inc. email: arnold.steve@ensco.com P.O. Box 5488 www: http://www.ensco.com Vandenberg AFB, CA 93437 voice: 805.806.8838 fax: 805.734.4779 #include <std_disclaimer.h> ****************************************************************
When the world was young, "Tom Roche" <tom_roche@ncsu.edu> carved some runes like this: [snip]> - net use X: \\backpack\tmp /user:guest > > gets > > - The password is invalid for \\backpack\tmp > - Type the password for \\backpack\tmp: > - System error 1240 has occurred. > - The account is not authorized to login from this station. > > [tmp] is setup public = yes.What happens when you try the above with a real user account, ie: net use X: \\backpack\tmp /user:jones Have you tried with a win95 client? Any problems with smbclient? Do you pass all the test steps in diagnosis.txt? As an experiment, I just tried mounting a share (using Net Use under NT4SP3) as a different user (on the samba side) than my current NT account and got the following error: System error 1219 has occurred. The credentials supplied conflict with an existing set of credentials. I really don't know much about NT at all (we've only had the machine for a few weeks, and I'm much more interested in learning things like SlickEdit, linux apps, etc). I'll do what I can though.> smbclient and lmblookup work without them. In any case, I tried > adding > > - hosts allow = 152.1 127.^^^^^^ You need a trailing dot to allow all addresses in your local address space, ie: hosts allow = 192.168.0. 127. Hope this helps, Steve ****************************************************************** Stephen L Arnold http://www.rain.org/~sarnold #include <std_disclaimer.h> ******************************************************************
When the world was young, "Sanders, Peter" <Peter.Sanders@dsto.defence.gov.au> carved some runes like this:> I am running Linux 2.0.30 with a few W95.SR2 boxen on an isolated > network. I am also running another Linux 2.0.30 with about 20-40 W95 > boxen on a corporate mixed ipx-Novell/tcpip network behind a firewall. I > have experienced the above with all Samba versions I have used but have > only taken notice since 1.9.18p4. I am now running 2.0.2 (or should that > be 2.0p2). Both of these Linux boxen are using small dead-time > values and I suspect that the invalid guest access occurs during > automatic reconnection. More worrisome is that I have occasionally > had the situation occur that several non-public shares would > only be connected to as guest, even immediately after a cold > reboot of the workstation. The cure in these cases was to > delete the username.PWL file (cached passwords) on the workstation; > reboot the workstation and login, typing in passwords as > requested. In a few of the worst cases I have also had to change > access passwords at the Linux end and/or disconnect the > workstation from the shares and reconnect. > > All of the above has led me to assume that the problem is at least > initiated by a W95 bug or is caused by poor installation. Since > someone else has had similar experiences I am finally moved > to announce it. Here follows a portion of my smb.conf. >[snip]> guest account = guestHave you tried a different guest account (such as nobody or ftp)? Just a thought, Steve **************************************************************** Stephen L. Arnold Senior Systems Engineer ENSCO Inc. email: arnold.steve@ensco.com P.O. Box 5488 www: http://www.ensco.com Vandenberg AFB, CA 93437 voice: 805.806.8838 fax: 805.734.4779 #include <std_disclaimer.h> ****************************************************************
When the world was young, Alex Yu <ayu1@nycap.rr.com> carved some runes like this:> I don't want smb to send clear text passwd, because there might be a > chance that people will sniff my subnet. BUT I don't want to have 2 > seperate passwds. I want samba to share /etc/passwd passwords. All I > need is SPEED and get PASSWORD share working. PLEASE HELP ME!!!The basic samba settings should be fine (speed-wise) unless something else is hosed (network setup, flaky NIC, etc). On a 10 Mbs ethernet, I get 750-900 k/sec on both SMB and ftp transfers. SMB is fastest between win95 boxes, and slowest between NT4 and samba. ftp transfers are pretty consistent (about 850 k/sec) across platforms. Also, our network has very little traffic. Another guy said (a while back) that Netblooie was sucking up about 70% of the available bandwidth on his network... I'll attach my smb.conf, but you'll have to adjust yourself if you're using 2.x (I'm still running 1.9.18p8). I suppose you've played with the read-raw and other settings. Also, strict locking can slow things down quite a bit. Check the speed.txt docs for more ideas. Encrypted passwords should work fine; just make sure you create smbpasswd in the right place for your setup and either add each user manually, or use the update encrypted switch (while using plaintext passwords) until all passwords have been updated in smbpasswd. You can use the unix-passwd-sync option as well. Here is my setup: [global] #==================Shortened for the list================= name resolve order = lmhosts host bcast guest account = ftp log file = /var/log/samba/log.%m max log size = 50 security = user username map = /etc/smbusers socket options = TCP_NODELAY local master = yes os level = 65 domain master = yes preferred master = yes wins support = no dns proxy = no preserve case = yes short preserve case = yes mangle case = yes #================== Share Definitions ===================[homes] comment = Home Directory browseable = no writable = yes alternate permissions = yes force directory mode = 0755 create mode = 0644 [printers] comment = All Printers path = /var/spool/samba browseable = no # Set public = yes to allow user 'guest account' to print guest ok = no writable = no printable = yes # This one is useful for people to share files [tmp] comment = Temporary file space path = /tmp read only = no public = yes # A publicly accessible directory, but read only, except for admin. [public] comment = HTML Document Tree path = /home/httpd public = yes writable = yes printable = no write list = arnold, root, admin, sarnold # Publicly accessible directory, but read-only, except for admin. # This is the /usr/doc tree [docs] comment = Linux docs path = /usr/doc public = yes writable = yes printable = no write list = arnold, root, admin, sarnold [source] comment = Source Code path = /usr/src valid users = [list of valid users] public = no writable = yes printable = no **************************************************************** Stephen L. Arnold Senior Systems Engineer ENSCO Inc. email: arnold.steve@ensco.com P.O. Box 5488 www: http://www.ensco.com Vandenberg AFB, CA 93437 voice: 805.806.8838 fax: 805.734.4779 #include <std_disclaimer.h> ****************************************************************
At 19:03 11/03/99 +1100, you wrote:>I spent more than 20 hours and tried to get Samba work along with Winbloz >"NT". But I failed many many many times. The speed is very slow. It >takes more than 2 mins to login and change folder. If your configuration >is what I need, would you please send me your configuration and tell me how >to speed NT up? >If you are getting 2 minute delays connecting to a Samba share, You have networking problems, not Samba problems. The most likely explanation is you have a DNS lookup failure which is timing out. Try putting the IP address of your NT workstation in /etc/hosts. If this doesn't fix things, you may have a problem elsewhere in the network. If your Samba configuration is wrong, the connection request will usually fail within a second or two. Best regards, Paul Paul Sherwin Consulting 22 Monmouth Road, Oxford OX1 4TD, UK Phone +44 (0)1865 721438 Fax +44 (0)1865 434331 Pager +44 (0)7666 797228
> SAMBA Digest 2016> 8) Unable to Browse or Connect From Win98 to Samba 2.0.3 > by CLIFFORD ILKAY <clifford_ilkay@dinamis.com>...>The smb.conf file is as follows. > ># Samba config file created using SWAT ># from localhost (127.0.0.1) ># Date: 1999/03/11 02:14:19 > ># Global parameters > workgroup = UCBL1 > server string = Samba Server > encrypt passwords = Yes > unix password sync = Yes > log level = 3 > log file = /var/log/samba/log.%m > max log size = 50 > name resolve order = wins lmhosts bcast > socket options = TCP_NODELAY > logon path = \\%L\Profiles\%U > domain logons = Yes > os level = 255 > preferred master = Yes > domain master = Yes > dns proxy = No > wins support = Yes > hosts allow = 192.168.1. 127. >Could there be a space in ^^^^^^^^^ ? ----------------------------------------------------------- Richard Neale v: (408) 735-6810 ex 30 IntraCom Corp. f: (408) 735-6816 1309 S. Mary Ave. Richard.Neale@IntraCom.Net Sunnyvale, CA 94087