RE: [newbie] SAMBA (was: internet sharing setup)
If you are having problems connecting to shares from Win2K it may be due to how Win2K handles passwords... Make sure you have encrypted passwords turned on in samba. Also make sure that the hash level parameter is set to 8 in Samba. This causes Samba to accept various combinations of upper case and lower case in the password. Effectively if Samba doesn't recognize the password coming from Win2, samba will try sucessive combinations of upper case and lower case letters using the password that was passed to it, in attempting to find a match. Re: Copying files Remember that the Windows browser is showing you the shares. Under Winblows it's easier to Map a drive letter to a share. Then most Windows programs will use the Samba share without a UNC. You can copy files via the windows browser, etc. -JMS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Lee Roberts Sent: Saturday, December 08, 2001 11:12 PM To: [EMAIL PROTECTED] Subject: RE: [newbie] SAMBA (was: internet sharing setup) At 09:01 PM 12/8/2001 -0500, Jose M. Sanchez wrote: I hope you set up your Win2K machine to be a member of a workgroup and not a domain. Yes, it is a member of the workgroup. But, I get an error message, when double-clicking on the Computers near me icon, that states that I'm not permitted to connect to the workgroup from this location (something like that). But, I am able to connect both ways between the Linux Win95 boxes after straightening out the user/password lists. I can connect to the Win2K machine from the Linux box. I have to figure out how to transfer files now. ls q works but cp doesn't. And I can't seem to connect to the homes directory from the Win95 box even though the homes share icon shows up. But, as I mentioned above I can't connect to the Linux box or Win95 box from my Win2K box. Anyway, thanks for your help the tutorial. It helps me to understand what's going on. There sure is a lot to understand about networking! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
RE: [newbie] SAMBA (was: internet sharing setup)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 06:12 PM 12/7/2001 -0500, Jose M. Sanchez wrote: First: Are all three machines members of the same workgroup? Yes, they are. Are you SURE that you've defined the Workgroup name in Samba the SAME as that used on your other Winblows boxes? Yes, I have. Second: When you log into windows you are asked for a user name and password. This user name and password, gets passed to Samba whenever you connect to a share and browse the network. Not on the Win95 machine. The Win95 machine prompts for a password. Thus a Linux/Unix account AND a corresponding Samba account must exist for each of these login name/password pairs. In other words, both the Windows computers and the Linux box has to have identical user/password combinations? I.E. you need to use smbadduser and smbpasswd to add the SAMBA users to Linux's SAMBA user/password lists. ALWAYS double check this using SMBCLIENT smbclient -L LINUXBOX -U WINUSER Asks the Samba Linuxbox, to log in as WINUSER and present the shares. LINUXBOX WINUSER == the machine name? When you configured SAMBA, you should have also enabled the NMB component and enabled SAMBA to be the BROWSE MASTER for your network or domain. Done. This is what presents the shares to the Winblows workstations. (the icons). If you havent increase the OS LEVEL in samba, the browse master will be decided by election amoung your computers (REALLY they vote!). When things change the browse list(s) dissappear for awhile until things get sorted out again. The OS level was not changed. If your Linux box is up all the time, make it the BROWSE MASTER so that things will not keep shifting and disappearing. Did you also remember to define the DEVICES (aka IP ADDRESSES) using the INTERFACES = Line? Yes. If not Samba will not broadcast it's information until something nudges it. -JMS I made some progress. I am able to access the Win95 machine from the Linux box but not vice-versa. I am unable to connect to the Win2K machine and vice-versa. Here's one error I get: added interface (addressing deleted) added interface (addressing deleted) session request to N0SQ failed (Not listening for calling name) session request to *SMBSERVER failed (Not listening for calling name) |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]] On Behalf Of Lee Roberts |Sent: Friday, December 07, 2001 5:40 PM |To: [EMAIL PROTECTED] |Subject: Re: [newbie] internet sharing setup | | |Speaking of Samba, I get the icon for the Linux box to show |up on my Win2K Win95 clients but I can't browse the Linux |box. And if I restart Windows, I have to restart the services |on the Linux box before I can display the network icons again |- that sucks. Win95 asks for a password to try to access the |Linux box - that fails, of course. I used the procedure for |Samba from the techtv.com website. Apparently, it's not that |easy to set up Samba. So, what am I doing wrong? BTW, I can |ping all 3 machines on my network - can't share files with any |of them even though the icons show up on the Windows boxes. |And internet connection sharing works OK. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8EmqgjCg8oFTHzFARArlLAJ9vGRPgIf1csO5j9NG0nonirXoz2gCgnd/m 6TuGqPJfO/waGmtpPTTO11o= =QaWl -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
RE: [newbie] SAMBA (was: internet sharing setup)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Lee Roberts Sent: Saturday, December 08, 2001 2:32 PM To: [EMAIL PROTECTED] Subject: RE: [newbie] SAMBA (was: internet sharing setup) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 06:12 PM 12/7/2001 -0500, Jose M. Sanchez wrote: First: Are all three machines members of the same workgroup? Yes, they are. Are you SURE that you've defined the Workgroup name in Samba the SAME as that used on your other Winblows boxes? Yes, I have. Second: When you log into windows you are asked for a user name and password. This user name and password, gets passed to Samba whenever you connect to a share and browse the network. Not on the Win95 machine. The Win95 machine prompts for a password. --- No, you misunderstand. Whenever your Win9x machine attempts to access a Samba resource or share, what happens first behind the scenes is that Samba requests a user name and password from the Windows machine attempting to access it's share. Windows then passes the user name and passwords you originally used to log into WINDOWS, to SAMBA. Thus if Samba doesn't know the username and/or password, it will fail to show you the share you've created. A symptom of this is exactly what you describe. That is, Windows puts up a dialog box asking for a password, when trying to access the Samba share. Why? Well Windows passed the username and password you used to log in, to Samba, but Samba rejected them. Samba doesn't have the username and password in it's database of valid SAMBA users. Thus a Linux/Unix account AND a corresponding Samba account must exist for each of these login name/password pairs. In other words, both the Windows computers and the Linux box has to have identical user/password combinations? --- Correct, but more importantly Windows and SAMBA must have identical user/password combinations. As a result of this you should also have corresponding LINUX/UNIX logins passwords (though this is not strictly true, for the moment say it is...) Consider SAMBA to be another computer on your network with it's OWN set of logins. Linux is yet another, and so is your Windows box. Windows ONLY passes the user name and passwords to of the currently logged in user to Samba. (Purely as an aside; sitting on your Windows hard drive is a file called USERNAME.pwl The PWL stands for Pass Word List. This file contains the usernames and passwords used by the person logged in as USERNAME. Thus if you log in as Joe, there will be a JOE.PWL on the hard drive. This file is what Windows creates as it builds up a password database for other shares on your LAN...) I.E. you need to use smbadduser and smbpasswd to add the SAMBA users to Linux's SAMBA user/password lists. ALWAYS double check this using SMBCLIENT smbclient -L LINUXBOX -U WINUSER Asks the Samba Linuxbox, to log in as WINUSER and present the shares. LINUXBOX WINUSER == the machine name? --- No. Linuxbox is the NETBIOS/NMB name of your SAMBA server. If you named it Blue_Linux_Box you would type in smbclient -L Blue_Linux_Box -U WINUSER WINUSER is a login name that you are using on your WINDOWS machine to log in there! This effectively tests the ability of Windows to log into Samba. Say at the Windows Login screen you enter Joe for a login name and BigDogs for a password. Then you would type; smbclient -L Blue_Linux_Box -U Joe at your Linux console. This tells Samba that you want to log in as Joe, the same userNAME you are using on your Windows machine. You do this to test if Samba recognizes the Joe account and password. Normally after doing this, Samba will reply Password: You then enter the SAME password you normally use on the Windows machine to log in. If Samba has a correctly configured account for Joe it will then show you a list of all of the shares it has available. When you configured SAMBA, you should have also enabled the NMB component and enabled SAMBA to be the BROWSE MASTER for your network or domain. Done. This is what presents the shares to the Winblows workstations. (the icons). If you havent increase the OS LEVEL in samba, the browse master will be decided by election amoung your computers (REALLY they vote!). When things change the browse list(s) dissappear for awhile until things get sorted out again. The OS level was not changed. --- By default Samba is the equivalent of a Windows NT 3.51 server. It pays to raise the OS level a bit. Why? All of your Windows machines query the network to see who has the highest OS level. The machine with the highest level is normally elected to be the browse master. If your Linux box is up all the time, it's the best browse master. The browse master keeps a list of all the shareable resources on your network, even from other windows computers. If your Linux box is up all the time, make it the BROWSE MASTER so that things will not keep shifting and disappearing. Did
