Re: Samba help.
On 02/01/2017 08:02 PM, R. Ramesh wrote: On 1/29/2017 11:25 AM, John Darrah wrote: On 1/29/2017 12:25 AM, R. Ramesh wrote: I recently upgraded my debian jesse to 8.6. All of a sudden all samba guest access to this box stopped working. I did not update smb.conf file any time before or after. I vaguely remember that there was a flash of notes flying by when samba was upgraded, but do not recall what it is. BTW, I can mount if I provide an actual valid user with password. Only guest access does not work. Linux host 3.16.0-4-686-pae #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) i686 GNU/Linux Samba Version: 2:4.2.14+dfsg-0+deb8u2 Guest access to the following share fails after the upgrade: [data] path = /data create mask = 0755 directory mask = 0755 public = yes browseable = yes writable = yes guest ok = yes If it is not too much trouble, please copy me your responses Thanks Ramesh Check to see that smb.conf was not replaced. If it was, the previous version will be called smb.conf.dpkg-dist or smb.conf.ucf-dist. You will have to compare them with your smb.conf file and merge any differences. -- john Also check the following in [global] settings: Change: map to guest = Bad User to: map to guest = nobody -- john Thanks for your help. I remember that apt-get asked if I wanted my smb.conf to be replaced. I said "no." Quick tkdiff between smb.conf and dist version shows that I miss these server role = standalone server map to guest = bad user usershare allow guests = yes Of course, I will fix the second line and add all three and see what happens. Ramesh Adding the three lines with "bad user" replaced by "nobody" prevents nmbd from being restarted. It fails to restart and the syslong shows that it does not like nobody and commenting out the line allows restart of service. However I do not have guest mount permitted as before. I tried putting a valid user instead of nobody and nmbd does not like that either. So, I am lost. Ramesh Actually using "map to guest = bad user" is needed for guest mount to work. I read it on samba blog as part of an error report https://samba.plus/blog/ dated (5/3/16) So, problem solved for now (until I upgrade again :-) Ramesh
Re: Re: Samba help.
On 1/29/2017 11:25 AM, John Darrah wrote: On 1/29/2017 12:25 AM, R. Ramesh wrote: I recently upgraded my debian jesse to 8.6. All of a sudden all samba guest access to this box stopped working. I did not update smb.conf file any time before or after. I vaguely remember that there was a flash of notes flying by when samba was upgraded, but do not recall what it is. BTW, I can mount if I provide an actual valid user with password. Only guest access does not work. Linux host 3.16.0-4-686-pae #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) i686 GNU/Linux Samba Version: 2:4.2.14+dfsg-0+deb8u2 Guest access to the following share fails after the upgrade: [data] path = /data create mask = 0755 directory mask = 0755 public = yes browseable = yes writable = yes guest ok = yes If it is not too much trouble, please copy me your responses Thanks Ramesh Check to see that smb.conf was not replaced. If it was, the previous version will be called smb.conf.dpkg-dist or smb.conf.ucf-dist. You will have to compare them with your smb.conf file and merge any differences. -- john Also check the following in [global] settings: Change: map to guest = Bad User to: map to guest = nobody -- john Thanks for your help. I remember that apt-get asked if I wanted my smb.conf to be replaced. I said "no." Quick tkdiff between smb.conf and dist version shows that I miss these server role = standalone server map to guest = bad user usershare allow guests = yes Of course, I will fix the second line and add all three and see what happens. Ramesh Adding the three lines with "bad user" replaced by "nobody" prevents nmbd from being restarted. It fails to restart and the syslong shows that it does not like nobody and commenting out the line allows restart of service. However I do not have guest mount permitted as before. I tried putting a valid user instead of nobody and nmbd does not like that either. So, I am lost. Ramesh
Re: Re: Samba help.
On 1/29/2017 11:25 AM, John Darrah wrote: On 1/29/2017 12:25 AM, R. Ramesh wrote: I recently upgraded my debian jesse to 8.6. All of a sudden all samba guest access to this box stopped working. I did not update smb.conf file any time before or after. I vaguely remember that there was a flash of notes flying by when samba was upgraded, but do not recall what it is. BTW, I can mount if I provide an actual valid user with password. Only guest access does not work. Linux host 3.16.0-4-686-pae #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) i686 GNU/Linux Samba Version: 2:4.2.14+dfsg-0+deb8u2 Guest access to the following share fails after the upgrade: [data] path = /data create mask = 0755 directory mask = 0755 public = yes browseable = yes writable = yes guest ok = yes If it is not too much trouble, please copy me your responses Thanks Ramesh Check to see that smb.conf was not replaced. If it was, the previous version will be called smb.conf.dpkg-dist or smb.conf.ucf-dist. You will have to compare them with your smb.conf file and merge any differences. -- john Also check the following in [global] settings: Change: map to guest = Bad User to: map to guest = nobody -- john Thanks for your help. I remember that apt-get asked if I wanted my smb.conf to be replaced. I said "no." Quick tkdiff between smb.conf and dist version shows that I miss these server role = standalone server map to guest = bad user usershare allow guests = yes Of course, I will fix the second line and add all three and see what happens. Ramesh
Re: Samba help.
On 1/29/2017 11:25 AM, John Darrah wrote: On 1/29/2017 12:25 AM, R. Ramesh wrote: I recently upgraded my debian jesse to 8.6. All of a sudden all samba guest access to this box stopped working. I did not update smb.conf file any time before or after. I vaguely remember that there was a flash of notes flying by when samba was upgraded, but do not recall what it is. BTW, I can mount if I provide an actual valid user with password. Only guest access does not work. Linux host 3.16.0-4-686-pae #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) i686 GNU/Linux Samba Version: 2:4.2.14+dfsg-0+deb8u2 Guest access to the following share fails after the upgrade: [data] path = /data create mask = 0755 directory mask = 0755 public = yes browseable = yes writable = yes guest ok = yes If it is not too much trouble, please copy me your responses Thanks Ramesh Check to see that smb.conf was not replaced. If it was, the previous version will be called smb.conf.dpkg-dist or smb.conf.ucf-dist. You will have to compare them with your smb.conf file and merge any differences. -- john Also check the following in [global] settings: Change: map to guest = Bad User to: map to guest = nobody -- john
Re: Samba help.
On 1/29/2017 12:25 AM, R. Ramesh wrote: I recently upgraded my debian jesse to 8.6. All of a sudden all samba guest access to this box stopped working. I did not update smb.conf file any time before or after. I vaguely remember that there was a flash of notes flying by when samba was upgraded, but do not recall what it is. BTW, I can mount if I provide an actual valid user with password. Only guest access does not work. Linux host 3.16.0-4-686-pae #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) i686 GNU/Linux Samba Version: 2:4.2.14+dfsg-0+deb8u2 Guest access to the following share fails after the upgrade: [data] path = /data create mask = 0755 directory mask = 0755 public = yes browseable = yes writable = yes guest ok = yes If it is not too much trouble, please copy me your responses Thanks Ramesh Check to see that smb.conf was not replaced. If it was, the previous version will be called smb.conf.dpkg-dist or smb.conf.ucf-dist. You will have to compare them with your smb.conf file and merge any differences. -- john
Samba help.
I recently upgraded my debian jesse to 8.6. All of a sudden all samba guest access to this box stopped working. I did not update smb.conf file any time before or after. I vaguely remember that there was a flash of notes flying by when samba was upgraded, but do not recall what it is. BTW, I can mount if I provide an actual valid user with password. Only guest access does not work. Linux host 3.16.0-4-686-pae #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) i686 GNU/Linux Samba Version: 2:4.2.14+dfsg-0+deb8u2 Guest access to the following share fails after the upgrade: [data] path = /data create mask = 0755 directory mask = 0755 public = yes browseable = yes writable = yes guest ok = yes If it is not too much trouble, please copy me your responses Thanks Ramesh
Re: Newbie Samba help (solved)
On 4/26/07, John K Masters [EMAIL PROTECTED] wrote: On Wed, 25 Apr 2007 22:03:47 -0400 Jan Sneep [EMAIL PROTECTED] wrote: snip Interestingly from the Win Xp machine I can see a whole bunch of files and folders with names that start with a . that I can't see from the Gnome desktop. These are hidden files. Not shown by default in Gnome. You can see them by using the -a switch with ls or Ctl-H if using the Gnome GUI. Yes, sometimes, the huge list might be overwhelming. In XP's explorer, you can turn off showing the hidden files. IIRC, from explorer, Tools Folder options View (second tab) (scroll down) Do not show hidden files. Apply OK. -- Regards PK -- http://counter.li.org #402424 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Newbie Samba help (solved)
Thanks I was just going to ask if there was some way of filtering out the hidden files so they wouldn't be presented to the Xp users. -Original Message- From: P Kapat [mailto:[EMAIL PROTECTED] Sent: April 26, 2007 2:33 AM To: debian-user@lists.debian.org Subject: Re: Newbie Samba help (solved) On 4/26/07, John K Masters [EMAIL PROTECTED] wrote: On Wed, 25 Apr 2007 22:03:47 -0400 Jan Sneep [EMAIL PROTECTED] wrote: snip Interestingly from the Win Xp machine I can see a whole bunch of files and folders with names that start with a . that I can't see from the Gnome desktop. These are hidden files. Not shown by default in Gnome. You can see them by using the -a switch with ls or Ctl-H if using the Gnome GUI. Yes, sometimes, the huge list might be overwhelming. In XP's explorer, you can turn off showing the hidden files. IIRC, from explorer, Tools Folder options View (second tab) (scroll down) Do not show hidden files. Apply OK. -- Regards PK -- http://counter.li.org #402424 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.463 / Virus Database: 269.6.1/776 - Release Date: 2007.04.25 12:19 PM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.463 / Virus Database: 269.6.1/776 - Release Date: 2007.04.25 12:19 PM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Newbie Samba help
I just installed the latest OS using a NetInst CD and during the install I checked the boxes for File Server and Print Server and I have been to HYPERLINK http://localhost:901Http://localhost:901 to verify that Samba is up and running. I can see the Debian server from my Win XP machines, and also from the Debian side I can access files in the Shared Documents folder on the Win Xp machine open them and copy them back to the Debian desktop. So Samba must be up an running properly.However, I can't access the Debian folders from the Win Xp machine. I have setup a User on the Debian side called Jan and logged in using that password on the Debian machine no problem. I have renamed my Win Xp user account to Jan and used the exact same password. When I try to access the Debian server (through Network Places) I am prompted for a User and Pswd, to which I provide the same Jan and the Pswd and it fails to connect. I have tried it both logged out and logged in on the Debian server using User Jan. I have looked at the settings at HYPERLINK http://localhost:901http://localhost:901 and compared them to the manual at HYPERLINK http://www.faqs.org/docs/samba/toc.htmlhttp://www.faqs.org/docs/samba/toc. html. As best I can figure everything looks fine. As I said I haven't changed so much as one setting from the default Samba setup that installs right from the NetInst CD. Is there some overall security setting on the Debian that I need to allow? Is there a default firewall that I need to configure to allow access? Or does this sound like a problem from my Win Xp side? Cheers, Jan No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.463 / Virus Database: 269.6.0/775 - Release Date: 2007.04.24 5:43 PM
Re: Newbie Samba help
On Wednesday, 25.04.2007 at 14:58 -0400, Jan Sneep wrote: I just installed the latest OS using a NetInst CD and during the install I checked the boxes for File Server and Print Server and I have been to HYPERLINK http://localhost:901Http://localhost:901 to verify that Samba is up and running. I can see the Debian server from my Win XP machines, and also from the Debian side I can access files in the Shared Documents folder on the Win Xp machine open them and copy them back to the Debian desktop. So Samba must be up an running properly.However, I can't access the Debian folders from the Win Xp machine. I have setup a User on the Debian side called Jan and logged in using that password on the Debian machine no problem. I have renamed my Win Xp user account to Jan and used the exact same password. When I try to access the Debian server (through Network Places) I am prompted for a User and Pswd, to which I provide the same Jan and the Pswd and it fails to connect. I have tried it both logged out and logged in on the Debian server using User Jan. Note that Samba typically requires you to create a dedicated Samba user on the server, not a 'normal' user account. It's unclear what you did when you said I have setup a User on the Debian side... If you can't figure it out, post your /etc/samba/smb.conf and we may be able to help. Dave. -- Please don't CC me on list messages! ... Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] All email from me is now digitally signed, key from http://www.sungate.co.uk/ Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92 signature.asc Description: Digital signature
RE: Newbie Samba help
You are asked to setup a non-root user as part of the NetInst. This is the User that I setup. -Original Message- From: Dave Ewart [mailto:[EMAIL PROTECTED] Sent: April 25, 2007 3:15 PM To: debian-user@lists.debian.org Subject: Re: Newbie Samba help On Wednesday, 25.04.2007 at 14:58 -0400, Jan Sneep wrote: I just installed the latest OS using a NetInst CD and during the install I checked the boxes for File Server and Print Server and I have been to HYPERLINK http://localhost:901Http://localhost:901 to verify that Samba is up and running. I can see the Debian server from my Win XP machines, and also from the Debian side I can access files in the Shared Documents folder on the Win Xp machine open them and copy them back to the Debian desktop. So Samba must be up an running properly.However, I can't access the Debian folders from the Win Xp machine. I have setup a User on the Debian side called Jan and logged in using that password on the Debian machine no problem. I have renamed my Win Xp user account to Jan and used the exact same password. When I try to access the Debian server (through Network Places) I am prompted for a User and Pswd, to which I provide the same Jan and the Pswd and it fails to connect. I have tried it both logged out and logged in on the Debian server using User Jan. Note that Samba typically requires you to create a dedicated Samba user on the server, not a 'normal' user account. It's unclear what you did when you said I have setup a User on the Debian side... If you can't figure it out, post your /etc/samba/smb.conf and we may be able to help. Dave. -- Please don't CC me on list messages! ... Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] All email from me is now digitally signed, key from http://www.sungate.co.uk/ Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.463 / Virus Database: 269.6.0/775 - Release Date: 2007.04.24 5:43 PM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.463 / Virus Database: 269.6.0/775 - Release Date: 2007.04.24 5:43 PM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie Samba help
On Wednesday, 25.04.2007 at 16:14 -0400, Jan Sneep wrote: You are asked to setup a non-root user as part of the NetInst. This is the User that I setup. That's not enough for Samba. You probably need to create the user for Samba too, via smbpasswd. As I said, please send your /etc/samba/smb.conf if you want more help. Dave. -- Please don't CC me on list messages! ... Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] All email from me is now digitally signed, key from http://www.sungate.co.uk/ Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92 signature.asc Description: Digital signature
Re: Newbie Samba help
You probably need to create the user for Samba too, via smbpasswd. As I said, please send your /etc/samba/smb.conf if you want more help. As Dave was suggesting, you need to modify smb.conf. There are a few GUIs that do that for you (http://us4.samba.org/samba/GUI/). Its easier to edit the file for small purposes like this, if you know what you want. Edit you /etc/samba/smb.conf to look like this: (this is mine; remember to undo the linebreaks that are caused by this mail text.) [global] # change the WORKGROUP to whatever you see from XP Network Neighborhood. workgroup = WORKGROUP server string = %h server # the following line was added/changed encrypt passwords = true obey pam restrictions = Yes passdb backend = tdbsam passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* . syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 dns proxy = No panic action = /usr/share/samba/panic-action %d invalid users = root # 192.168.a.b is the IP of my XP machine, replace a, b accordingly hosts allow = localhost, 192.168.a.b socket options = TCP_NODELAY load printers = No [homes] comment = Home Directories create mask = 0700 directory mask = 0700 browseable = Yes writable = Yes This should work with the defualt Jan passwd, otherwise, use smbpasswd Jan at the comand line and provide a password (need not be the one you are using for usual login, but helps to keep it same). I generally map a network drive to the HOME directory of the samba server (Debian box). HTH -- Regards PK -- http://counter.li.org #402424 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie Samba help
You are asked to setup a non-root user as part of the NetInst. This is the User that I setup. Yes, as Dave said, you have to use smbpaswd as root to add new users which can access samba. Then you have to setup your /etc/samba/smb.conf file to define shares, which are portions of your filesystems viewable through samba. Do 'man smb.conf' to find out all the details. As a minimum you should setup: netbios name = name - this is the name given to your samba server. users will be able to access it by //name/share To setup a share, do: [test_share} path = /home/Jan/shared_dir writable = yes public = yes To connect to it use //netbios_name/test_share . You can also setup default per-user shares, which will show linux home directory of a samba user if it exists, such as /home/Jan. To access it do //netbios_name/Jan. To setup home directories do (this should be inside your smb.conf already, but might be commented out by default): [homes] comment = Home Directories browseable = no writable = no create mask = 0700 directory mask = 0700 To make your samba server reread your configuration file, do: /etc/init.d/samba reload Hope this helps. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Newbie Samba help (solved)
Many Thanks for all the replies ... Turned out that all I needed to do was an smbpasswd -a jan and re-enter my password. At first I tried the settings you suggested ... I printed out your email and my smb.conf and compared them line by line. The differences were very small. Below is the smb.conf that gets setup via the NetInst routines. The encrypt passwords does not show up in the smb.conf and yet when you go to http://localhost:901 and click on the Globals button it does show encrypt passwords = YES. You suggested that under [homes] both browseable and writeable should be YES. I changed the browseable to YES, but couldn't find a writable as a choice under either the Basic or Advanced views. That change didn't make any difference, so I ploughed on and filled in the hosts allow field as you suggested. This change also didn't work, however it made the machine think longer when I tried to login. Before the response was instantaneous, this time it took a good 30 or 40 seconds to refuse access. socket options isn't a choice under the Basic view, but is under Advanced and mine was set the same as yours, but it doesn't show in my smb.conf. It appears that if it is a Samba default value it doesn't show in the smb.conf file? Only after doing the smbpasswd -a jan in Applications - Accessories - Root Terminal did I get to access the \home\jan folder. I changed everything back the original smb.conf settings and login from my Win Xp machines. Interestingly from the Win Xp machine I can see a whole bunch of files and folders with names that start with a . that I can't see from the Gnome desktop. # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2007/04/25 07:17:31 [global] workgroup = SFCMC server string = %h server obey pam restrictions = Yes passdb backend = tdbsam passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* . syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 dns proxy = No wins support = Yes panic action = /usr/share/samba/panic-action %d invalid users = root include = /etc/samba/dhcp.conf [homes] comment = Home Directories valid users = %S create mask = 0700 directory mask = 0700 browseable = No [printers] comment = All Printers path = /var/spool/samba create mask = 0700 printable = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers -Original Message- From: P Kapat [mailto:[EMAIL PROTECTED] Sent: April 25, 2007 5:53 PM To: debian-user@lists.debian.org Subject: Re: Newbie Samba help You probably need to create the user for Samba too, via smbpasswd. As I said, please send your /etc/samba/smb.conf if you want more help. As Dave was suggesting, you need to modify smb.conf. There are a few GUIs that do that for you (http://us4.samba.org/samba/GUI/). Its easier to edit the file for small purposes like this, if you know what you want. Edit you /etc/samba/smb.conf to look like this: (this is mine; remember to undo the linebreaks that are caused by this mail text.) [global] # change the WORKGROUP to whatever you see from XP Network Neighborhood. workgroup = WORKGROUP server string = %h server # the following line was added/changed encrypt passwords = true obey pam restrictions = Yes passdb backend = tdbsam passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* . syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 dns proxy = No panic action = /usr/share/samba/panic-action %d invalid users = root # 192.168.a.b is the IP of my XP machine, replace a, b accordingly hosts allow = localhost, 192.168.a.b socket options = TCP_NODELAY load printers = No [homes] comment = Home Directories create mask = 0700 directory mask = 0700 browseable = Yes writable = Yes This should work with the defualt Jan passwd, otherwise, use smbpasswd Jan at the comand line and provide a password (need not be the one you are using for usual login, but helps to keep it same). I generally map a network drive to the HOME directory of the samba server (Debian box). HTH -- Regards PK -- http://counter.li.org #402424 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.463 / Virus Database: 269.6.0/775 - Release Date: 2007.04.24 5:43 PM No virus found
Re: Newbie Samba help (solved)
On Wed, 25 Apr 2007 22:03:47 -0400 Jan Sneep [EMAIL PROTECTED] wrote: snip Interestingly from the Win Xp machine I can see a whole bunch of files and folders with names that start with a . that I can't see from the Gnome desktop. These are hidden files. Not shown by default in Gnome. You can see them by using the -a switch with ls or Ctl-H if using the Gnome GUI. Regards John -- War is God's way of teaching Americans geography Ambrose Bierce (1842 - 1914) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CUPS/Samba help please
On Wed, 13 Jul 2005 18:00:15 +0200, Clive Menzies [EMAIL PROTECTED] wrote: snip Anyone have some insight into this? Maybe you experienced something similar and can give me a few tips on how to resolve it? In /etc/samba/smb.conf there is a setting: # Most people will find that this option gives better performance. # See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/speed.html # for details # You may want to add the following on a Linux system: # SO_RCVBUF=8192 SO_SNDBUF=8192 socket options = TCP_NODELAY You could try uncommenting the penultimate line. Regards Clive snip P.S. AH SWEET BUDDAH. 'TIS FIXED Well, I had typed a whole giant message about why, even after trying the above, it still didn't work, when I happened to stumble across the fix via google and the Gentoo forums (hey, I was desperate) I did appreciate the suggestion above (and in fact tried it) but I didn't notice any difference. However, deleting two registry keys in XP proved to be the ultimate solution. Apparently this bug was introduced in Service Pack 2 (SP2) Anyhow, I'm gonna try to be as verbose about everything as possible in the hopes that the next poor bastard who suffers from this problem will be able to find this post in the archives. First the important info: Nuclear : My Windows XP SP2 machine Sikozu: Debian GNU/Linux Sarge box. HP LaserJet 3550N: The Printer and of course CUPS Samba. Two registry keys are at fault here. (Yay MS!) HKEY_CURRENT_USER\Printers\DevModePerUser and HKEY_CURRENT_USER\Printers\DevModes2 in DevModePerUser I have an entry of: \\Sikozu\Color_LaserJet_3550 -- DELETED IT in DevModes2 I have two entries: \\NUCLEAR\\\Sikozu\Color_LaserJet_3550,LocalsplOnly --- KEEP \\Sikozu\Color_LaserJet_3550 --- DELETED IT Now, from what I can surmise is the fix: By deleting those two DELETED keys. I've told XP to spool to itself only. and then hand off the data to Samba _after_. This results in 100% CPU usage for about 10 seconds, and then *presto* I have my machine back. No more 5 minute freezes, etc. I'm sure someone else can probably shed more light the exact technical details, but long story short: It didn't work before, and now it does. --- PREVIOUS TEXT THAT I'M LEAVING FOR KEYWORDS --- Clive, Thanks for the tip. I gave that a whirl, but it didn't improve it any that I could notice. However, it did give me some things to think about. As near as I can tell (after running a couple of experiments) is that whatever is going on involves the XP box talking to the CUPS machine. For example, when printing a document from within Acrobat 7, the print dialog brings up a little print preview display so that one can see what the document will look like before it is actually printed and paper/ink are expended. Now, based upon my experiments, whenever the display is redrawn, the print driver itself communicates with the CUPS machine to redraw this little window. Or perhaps communicates is not the right word, maybe Query is more correct. Perhaps the driver is querying the print server to find out if a particular paper size or layout is supported, I don't know. But some sort of data transfer is taking place. (and a god awful amount of it too) As long that little display doesn't need to be redrawn (overlapping window) and no settings (orientation, page count, etc) are changed, the CPU Bandwidth usage will eventually drop to zero and remain there. I can then proceed to press the OK button to initiate the print, and all goes as planned (and I get beautiful prints). But God forbid I change a setting (maybe I want 2 copies or I only want the first page printed, etc) and the whole cycle repeats. Network bandwidth jumps to 25mbps for 3-5 mins, CPU usage maxes out (which is due to the network traffic being generated I think). However, just as before, eventually the Print Preview window is redrawn and everything drops back to zero. I can click OK and get my printout. The really odd thing is that printing _directly_ to the printer doesn't result in the same kind of massive traffic. I might get 25mbps but only for a few seconds. So something is obviously jinky with Samba. Anyhow, if you or anyone else maybe has some more suggestions, I'd love to hear them, 'cause I'm at my wit's end. Thanks! -- Johann --
Re: CUPS/Samba help please
On Wed, 13 Jul 2005 17:40:08 +0200, in linux.debian.user you wrote: Beretta wrote: The easy solution is just to ditch CUPS for my printing, but I really like being able to go back and restart jobs regardless of which machine I'm currently using. Did you try CUPS with IPP instead of the SMB protocol? That won't address the samba problem, but may enable you to print with CUPS. Marty, Thank you for taking the time to offer that suggestion. I was eventually able to fix the problem (see my other post in this thread)
Re: CUPS/Samba help please
On (14/07/05 01:05), Johann Beretta wrote: To: debian-user@lists.debian.org From: Johann Beretta [EMAIL PROTECTED] Date: Thu, 14 Jul 2005 01:05:19 -0700 Subject: Re: CUPS/Samba help please On Wed, 13 Jul 2005 18:00:15 +0200, Clive Menzies [EMAIL PROTECTED] wrote: snip Anyone have some insight into this? Maybe you experienced something similar and can give me a few tips on how to resolve it? In /etc/samba/smb.conf there is a setting: # Most people will find that this option gives better performance. # See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/speed.html # for details # You may want to add the following on a Linux system: # SO_RCVBUF=8192 SO_SNDBUF=8192 socket options = TCP_NODELAY You could try uncommenting the penultimate line. Regards Clive snip P.S. AH SWEET BUDDAH. 'TIS FIXED Well, I had typed a whole giant message about why, even after trying the above, it still didn't work, when I happened to stumble across the fix via google and the Gentoo forums (hey, I was desperate) I did appreciate the suggestion above (and in fact tried it) but I didn't notice any difference. However, deleting two registry keys in XP proved to be the ultimate solution. Apparently this bug was introduced in Service Pack 2 (SP2) Anyhow, I'm gonna try to be as verbose about everything as possible in the hopes that the next poor bastard who suffers from this problem will be able to find this post in the archives. First the important info: Nuclear : My Windows XP SP2 machine Sikozu: Debian GNU/Linux Sarge box. HP LaserJet 3550N: The Printer and of course CUPS Samba. Two registry keys are at fault here. (Yay MS!) HKEY_CURRENT_USER\Printers\DevModePerUser and HKEY_CURRENT_USER\Printers\DevModes2 in DevModePerUser I have an entry of: \\Sikozu\Color_LaserJet_3550 -- DELETED IT in DevModes2 I have two entries: \\NUCLEAR\\\Sikozu\Color_LaserJet_3550,LocalsplOnly --- KEEP \\Sikozu\Color_LaserJet_3550 --- DELETED IT Now, from what I can surmise is the fix: By deleting those two DELETED keys. I've told XP to spool to itself only. and then hand off the data to Samba _after_. This results in 100% CPU usage for about 10 seconds, and then *presto* I have my machine back. No more 5 minute freezes, etc. I'm sure someone else can probably shed more light the exact technical details, but long story short: It didn't work before, and now it does. Great news ;) SP2 has a lot to answer for thanks for the info. It's not something I've seen (the problem) although we have a couple of networks where XP is printing to a Debian CUPS printer via samba. Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
CUPS/Samba help please
All, I have a strange situation that I cannot figure out. When printing to an HP LaserJet 3550N printer via CUPS/Samba on a Sarge box _from_ a Windows XP box the bandwidth and CPU usage on the client (XP) machine is insane. The network usage applet (on the XP machine) will typically show 25% usage (100mbit LAN) and 100% CPU usage for 5-6 minutes and the XP box will basically freeze during that time. In contrast, when I print directly to the printer from Windows (it's a network printer) via a standard TCP/IP port, this doesn't happen. CPU usage might spike to 10% for 10-15 seconds or so, and network usage might register 25% for a few moments. In both operations I use the print drivers supplied by HP for this model printer. The easy solution is just to ditch CUPS for my printing, but I really like being able to go back and restart jobs regardless of which machine I'm currently using. I have quite a few documents that are printed regularly, and being able to sit down at any machine and restart the job via a web browser is very handy. I also have an HP LaserJet 4000N (black/white) printer on the network, and printing to it via CUPS also results in the same scenario, but not quite as pronounced. Also, it doesn't matter what program I am printing from, be it Photoshop, Acrobat, Word, Excel (although Excel is the worst) attempting to print from any of these applications gives the same insane CPU/Network usage. The print jobs always end up being printed but, needless to say, having to wait 5 mins between clicking print and my XP box unfreezing is not something I can live with. Anyone have some insight into this? Maybe you experienced something similar and can give me a few tips on how to resolve it? Thanks in advance!
Re: CUPS/Samba help please
Beretta wrote: The easy solution is just to ditch CUPS for my printing, but I really like being able to go back and restart jobs regardless of which machine I'm currently using. Did you try CUPS with IPP instead of the SMB protocol? That won't address the samba problem, but may enable you to print with CUPS. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CUPS/Samba help please
On (13/07/05 07:24), Beretta wrote: I have a strange situation that I cannot figure out. When printing to an HP LaserJet 3550N printer via CUPS/Samba on a Sarge box _from_ a Windows XP box the bandwidth and CPU usage on the client (XP) machine is insane. The network usage applet (on the XP machine) will typically show 25% usage (100mbit LAN) and 100% CPU usage for 5-6 minutes and the XP box will basically freeze during that time. In contrast, when I print directly to the printer from Windows (it's a network printer) via a standard TCP/IP port, this doesn't happen. CPU usage might spike to 10% for 10-15 seconds or so, and network usage might register 25% for a few moments. In both operations I use the print drivers supplied by HP for this model printer. The easy solution is just to ditch CUPS for my printing, but I really like being able to go back and restart jobs regardless of which machine I'm currently using. I have quite a few documents that are printed regularly, and being able to sit down at any machine and restart the job via a web browser is very handy. I also have an HP LaserJet 4000N (black/white) printer on the network, and printing to it via CUPS also results in the same scenario, but not quite as pronounced. Also, it doesn't matter what program I am printing from, be it Photoshop, Acrobat, Word, Excel (although Excel is the worst) attempting to print from any of these applications gives the same insane CPU/Network usage. The print jobs always end up being printed but, needless to say, having to wait 5 mins between clicking print and my XP box unfreezing is not something I can live with. Anyone have some insight into this? Maybe you experienced something similar and can give me a few tips on how to resolve it? In /etc/samba/smb.conf there is a setting: # Most people will find that this option gives better performance. # See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/speed.html # for details # You may want to add the following on a Linux system: # SO_RCVBUF=8192 SO_SNDBUF=8192 socket options = TCP_NODELAY You could try uncommenting the penultimate line. Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compartir Con Samba (help)
[homes] comment = Home Directories bronseable = no path = /home/%u/Public algo ya empeza a funcionar... en el sentido que con una maquina (gnome 2.8 de sarge) he podido entrar en Public de un usuario. Pero desde Ubuntu con gnome 2.10 nada de nada. Tengo que probar con windows a ver que no sea un problema de gnome. OK, funciona perfectamente conectandose desde XP... genial! ciao, MaX __ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compartir Con Samba (help)
[homes] comment = Home Directories|-bronseable = no |path = /home/%u/Public| |---¿ no es browseable?-- Luis Vega M.Linux Registered User #356394http://fodsite.podzone.net
Re: Compartir Con Samba (help)
El Martes, 28 de Junio de 2005 00:15, max escribió: Hola a todos, necesito compartir una carpeta en concreto de cada usuario de mi servidor debian, utilizando samba Cada usuario tiene en su Home la carpeta Public y quiero compartir solo esa y no toda la Home. Como puedo hacerlo de forma automática? Estaba pensando de poner una variable en el path como %U o $HOME pero parece no funcionar. Aquí el trozito de smb.conf. [Public] path = /home/%U/Public available = yes browseable = yes public = yes writable = yes create mask = 777 directory mask = 777 ..algunas ideas? Alguna. ¿Usan los clientes linux?. Si es así edita /etc/fstab y añade la linea para montar el recurso?. -- Saludos. Pablo Fingerprint 5607 40CF 45EF D490 B794 5056 D7B2 C3DC ABF1 CE49 Jabber: [EMAIL PROTECTED] http://aldiagestion.com pgpdHfCrZbkQK.pgp Description: PGP signature
Re: Compartir Con Samba (help)
Hola.. Con fecha 00:15 28/06/2005, max escribió: -- Inicio del mensaje -- Hola a todos, necesito compartir una carpeta en concreto de cada usuario de mi servidor debian, utilizando samba Cada usuario tiene en su Home la carpeta Public y quiero compartir solo esa y no toda la Home. Como puedo hacerlo de forma automática? Estaba pensando de poner una variable en el path como %U o $HOME pero parece no funcionar. Aquí el trozito de smb.conf. [Public] path = /home/%U/Public available = yes browseable = yes public = yes writable = yes create mask = 777 directory mask = 777 Esta configuración tiene que confundir al servidor samba, porque estás nombrando un servicio en concreto (el servicio Public) con unos parámetros que son variables. La verdad es que no sé cómo respondería. ¿Qué tal modificando la entrada [homes]? Lo he probado, la verdad, pero en teoría el parámetro path podria aplicarse también a este caso, aunque en mis pruebas ha resultado ser desastroso. [homes] comment = Home Directories path = /home/%U/Public browseable = yes writeable = yes create mode = 0777 directory mode = 0777 Otro detalle para tener en cuenta: el servicio [homes] entrega una carpeta en concreto a cada usuario, no comparte todas las carpetas de forma genérica. O sea, aunque tengas muchos usuarios estos no tienen por qué ver las carpetas del resto de los usuario... al menos yo no he dado en cómo hacerlo (aunque me gusta mucho más esto que lo que hace windows, que temuestra todas las carpetas de todos los logins del sistema... ideal para ataques de fuerza bruta). Saludos.
Re: Compartir Con Samba (help)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 max wrote: Hola a todos, necesito compartir una carpeta en concreto de cada usuario de mi servidor debian, utilizando samba Cada usuario tiene en su Home la carpeta Public y quiero compartir solo esa y no toda la Home. Como puedo hacerlo de forma automática? Porque no creas una carpeta Public general fuera de Home? Estaba pensando de poner una variable en el path como %U o $HOME pero parece no funcionar. Aquí el trozito de smb.conf. Define parece no funcionar [Public] path = /home/%U/Public porque %U? (Para que no te sea tan simple la solucion, fijate en man smb.conf que alli te indica de manera muy clara cual es la letra que debes poner alli) available = yes browseable = yes public = yes writable = yes create mask = 777 directory mask = 777 ..algunas ideas? RTFM? ciao MaX __ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es - -- Ricardo A.Frydman Consultor en Tecnología Open Source - Administrador de Sistemas jabber: [EMAIL PROTECTED] - http://www.eureka-linux.com.ar SIP # 1-747-667-9534 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCwT4pkw12RhFuGy4RAszQAJ49Juzl8tysLko/zNwkD1PvShYu2QCfcmHZ rKMHOiYrkSIQDVbyD4YV3RI= =pzcp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compartir Con Samba (help)
- Original Message - From: max [EMAIL PROTECTED] To: debian-user-spanish@lists.debian.org Sent: Monday, June 27, 2005 7:15 PM Subject: Compartir Con Samba (help) Hola a todos, necesito compartir una carpeta en concreto de cada usuario de mi servidor debian, utilizando samba Cada usuario tiene en su Home la carpeta Public y quiero compartir solo esa y no toda la Home. Como puedo hacerlo de forma automática? ¿Compartirla con quién? ¿Todos con todos los usuarios, con el usuario propietario desde otra consola, o todas las public con un usuario en particular? Por defecto, samba habilita al usuario propietario a acceder a toda la home. Estaba pensando de poner una variable en el path como %U o $HOME pero parece no funcionar. Aquí el trozito de smb.conf. [Public] path = /home/%U/Public available = yes browseable = yes public = yes writable = yes create mask = 777 directory mask = 777 ..algunas ideas? ciao MaX __ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compartir Con Samba (help)
Ricardo Frydman wrote: porque %U? (Para que no te sea tan simple la solucion, fijate en man smb.conf que alli te indica de manera muy clara cual es la letra que debes poner alli) casi resuelto ponendo un %u en lugar de %U me esplico mejor: tengo en /home muchos usuarios y en cadauno de ellos tiene una carpeta Public así: /home/pepe/Public /home/jordi/Public /home/juan/Public . Quiero compartir solo la carpeta Public (con nombre y contraseña) sin tener que declarar cada vez el path completo. Por esto quiero usar el servicio [homes] entonces he puesto: [homes] comment = Home Directories bronseable = no path = /home/%u/Public algo ya empeza a funcionar... en el sentido que con una maquina (gnome 2.8 de sarge) he podido entrar en Public de un usuario. Pero desde Ubuntu con gnome 2.10 nada de nada. Tengo que probar con windows a ver que no sea un problema de gnome. ciao MaX __ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Compartir Con Samba (help)
Hola a todos, necesito compartir una carpeta en concreto de cada usuario de mi servidor debian, utilizando samba Cada usuario tiene en su Home la carpeta Public y quiero compartir solo esa y no toda la Home. Como puedo hacerlo de forma automática? Estaba pensando de poner una variable en el path como %U o $HOME pero parece no funcionar. Aquí el trozito de smb.conf. [Public] path = /home/%U/Public available = yes browseable = yes public = yes writable = yes create mask = 777 directory mask = 777 ..algunas ideas? ciao MaX __ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Samba HELP
Non c'est bon j'ai trouve -Message d'origine- De : Miki [mailto:[EMAIL PROTECTED] Envoyé : dimanche 16 février 2003 16:42 À : [EMAIL PROTECTED] Debian. Org Objet : Samba HELP J'ai fait une connerie à savoir j'ai fait un rm -r sur le répertoire /etc/samba après l'avoir désinstaller pk c'est une très bonne question mais mon problème c'est que si je réinstalle samba bein ce répertoire est complètement vide aucun fichier dedans et je sais pas comment résoudre ce problème -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SAMBA Help Needed
On (05 Sep 02 15:06), Bodnyk, Bruce W wrote: I'm trying to mount a directory on a Windows NT box onto a Debian system and am having some problems. I can use smbclient and get to the directory on the NT machine but when I try and mount the directory using mount -t smbfs -o username=bbodnyk/fciam //etbodnyk/proengineer /var/www/proengineer I get the following error message: SMBFS: need mount version 6 mount: wrong fs type, bad option, bad superblock on //etbodnyk/proengineer, or too many mounted file systems. Any idea what could be going wrong? This is not how you mount smbfs partitions. Instead try: mount -t smbfs //etbodnyk/proengineer /var/www/proengineer It will prompt you for a password. Ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SAMBA Help Needed
On (05 Sep 02 20:30), Ben Goodstein wrote: On (05 Sep 02 15:06), Bodnyk, Bruce W wrote: I'm trying to mount a directory on a Windows NT box onto a Debian system and am having some problems. I can use smbclient and get to the directory on the NT machine but when I try and mount the directory using mount -t smbfs -o username=bbodnyk/fciam //etbodnyk/proengineer /var/www/proengineer I get the following error message: SMBFS: need mount version 6 mount: wrong fs type, bad option, bad superblock on //etbodnyk/proengineer, or too many mounted file systems. Any idea what could be going wrong? This is not how you mount smbfs partitions. Instead try: mount -t smbfs //etbodnyk/proengineer /var/www/proengineer It will prompt you for a password. Ben My apologies, this IS how you mount smbfs so I am stumped. Ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SAMBA Help Needed
Only thing I can think of is that you are trying to mount ntfs partition and you don't have it in your kernel or you dont have the smbfs filesystem loaded in your kernel. But that mount 6 error is odd. If you have X installed try apt-get LinNeighborhood its a nice gui to mount network shares and see if you have any luck with that, sorry I couldn't be of more use. Ben Goodstein wrote: On (05 Sep 02 20:30), Ben Goodstein wrote: On (05 Sep 02 15:06), Bodnyk, Bruce W wrote: I'm trying to mount a directory on a Windows NT box onto a Debian system and am having some problems. I can use smbclient and get to the directory on the NT machine but when I try and mount the directory using mount -t smbfs -o username=bbodnyk/fciam //etbodnyk/proengineer /var/www/proengineer I get the following error message: SMBFS: need mount version 6 mount: wrong fs type, bad option, bad superblock on //etbodnyk/proengineer, or too many mounted file systems. Any idea what could be going wrong? This is not how you mount smbfs partitions. Instead try: mount -t smbfs //etbodnyk/proengineer /var/www/proengineer It will prompt you for a password. Ben My apologies, this IS how you mount smbfs so I am stumped. Ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SAMBA Help Needed
Bodnyk, Bruce W wrote: I'm trying to mount a directory on a Windows NT box onto a Debian system and am having some problems. I can use smbclient and get to the directory on the NT machine but when I try and mount the directory using mount -t smbfs -o username=bbodnyk/fciam //etbodnyk/proengineer /var/www/proengineer I get the following error message: SMBFS: need mount version 6 mount: wrong fs type, bad option, bad superblock on //etbodnyk/proengineer, or too many mounted file systems. Any idea what could be going wrong? Thanks! Bruce Can't answer your specific question, but I always use smbmount: smbmount //etbodynk/proengineer /var/www/proengineer -o username=bbodnyk/fciam Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SAMBA help.
It sounds as though you have some confusion about the differences between the smb networking protocol, which SAMBA and windows file and print sharing use, and the tcp/ip network protocol with BIND, which Linux and Windows TCP/IP use. This confusion no doubt is due to the fact that Microsoft decided to call an smb scope a domain, when domain had been used for more than ten years prior to the release of Windows NT to describe a TCP/IP/BIND scope. These two things are different. your internet (BIND) domain will look somethnig like name.foo, whereas your NT domain will look something like NAME (case insensitive). To understand this difference, take a closer look at your win9x network control panel. In the TCP/IP properties, on the DNS tab, you will find boxes for your hostname and domain name. These correspond to the hostname and network name that any Linux distribution will prompt you for when you install. In the Client for Microsoft Networking properties, there is a box for a Windows NT domain. This corresponds to the domain in the various SAMBA config files. There is also a workgroup box on the identity tab in the Windows network control panel. This should match the Windows NT domain mentioned above. This is all explained in much more detail in the SAMBA documentation.
SAMBA help.
I need to know if I need to rename my network 'WORKGROUP' to be able to share drives and printers with windows. I've currently named my network 'natepuri.com.' It's not a registered name, yet. I'll register it when I get the money. Does samba require WORKGROUP? Or is that just a variable for whatever I want to call my network. Presently all tcp/ip connections over my LAN are very function. IP MASQ is functional as well. However, I have the client section in the network window in the control panel set to 'Log on the Windows NT domain.' Previously I had the 'Windows NT domain:' set to 'natepuri.com,' that didn't work so I set it to 'WORKGROUP' and that didn't work. I had 'Access Control' set to 'User-level access control' and first had the list of users set to 'natepuri.com' then to 'WORKGROUP.' Neither worked. I'm using 'client for microsoft networks.' Samba is running in daemon mode. When I boot windows, it says 'cannot log on to Windows NT domain, some network services will be unavailable.' (or something like that). What am I doing wrong? I've read the SMB HOWTO among others. The issues above still confuse me... Thanks... NatePuri Certified Law Student Debian GNU/Linux Monk McGeorge School of Law [EMAIL PROTECTED] http://ompages.com
Re: SAMBA help.
On Fri, 19 Mar 1999, Paul Nathan Puri wrote: I need to know if I need to rename my network 'WORKGROUP' to be able to share drives and printers with windows. I've currently named my network 'natepuri.com.' It's not a registered name, yet. I'll register it when I get the money. I don't believe this is valid. This is not an internet domain it wants, but rather, a lanman domain, I don't think it can contain '.'s Does samba require WORKGROUP? Or is that just a variable for whatever I want to call my network. Whatever you want, mine is called ASGARD. Presently all tcp/ip connections over my LAN are very function. IP MASQ is functional as well. However, I have the client section in the network window in the control panel set to 'Log on the Windows NT domain.' Previously I had the 'Windows NT domain:' set to 'natepuri.com,' that didn't work so I set it to 'WORKGROUP' and that didn't work. You must change this in both SAMBA and in Win95, you also need to have in your smb.conf the lines: domain master = yes domain logons = yes I had 'Access Control' set to 'User-level access control' and first had the list of users set to 'natepuri.com' then to 'WORKGROUP.' Neither worked. I can't yet get this part to work either. Maybe eventually, does anyone on the list have this working? I'm using 'client for microsoft networks.' Samba is running in daemon mode. When I boot windows, it says 'cannot log on to Windows NT domain, some network services will be unavailable.' (or something like that). This is probably due to it not thinking your SAMBA server is a domain master for the domain you have told it to log in to. Adding the two lines above should fix that. You will also need to give yourself a SAMBA password: man smbpasswd What am I doing wrong? I've read the SMB HOWTO among others. The issues above still confuse me... Thanks... try: http://www.undergrad.math.uwaterloo.ca/~djbrosem/sambahowto/Samba-Beginners-HOWTO.html It's a work in progress, so not ready for prime-time yet, but I've got some pretty positive feedback on it. The package information for debian needs to be updated, so don't treat it as gospel, just a word of caution. The smb.conf file should do what you need, though, and AFAIK, it's the only info on SAMBA that explains win95 configuration. HTH -Dano
Re: SAMBA help.
Thanks for the info, I'll check it all out... NatePuri Certified Law Student Debian GNU/Linux Monk McGeorge School of Law [EMAIL PROTECTED] http://ompages.com On Fri, 19 Mar 1999, Daniel Brosemer wrote: On Fri, 19 Mar 1999, Paul Nathan Puri wrote: I need to know if I need to rename my network 'WORKGROUP' to be able to share drives and printers with windows. I've currently named my network 'natepuri.com.' It's not a registered name, yet. I'll register it when I get the money. I don't believe this is valid. This is not an internet domain it wants, but rather, a lanman domain, I don't think it can contain '.'s Does samba require WORKGROUP? Or is that just a variable for whatever I want to call my network. Whatever you want, mine is called ASGARD. Presently all tcp/ip connections over my LAN are very function. IP MASQ is functional as well. However, I have the client section in the network window in the control panel set to 'Log on the Windows NT domain.' Previously I had the 'Windows NT domain:' set to 'natepuri.com,' that didn't work so I set it to 'WORKGROUP' and that didn't work. You must change this in both SAMBA and in Win95, you also need to have in your smb.conf the lines: domain master = yes domain logons = yes I had 'Access Control' set to 'User-level access control' and first had the list of users set to 'natepuri.com' then to 'WORKGROUP.' Neither worked. I can't yet get this part to work either. Maybe eventually, does anyone on the list have this working? I'm using 'client for microsoft networks.' Samba is running in daemon mode. When I boot windows, it says 'cannot log on to Windows NT domain, some network services will be unavailable.' (or something like that). This is probably due to it not thinking your SAMBA server is a domain master for the domain you have told it to log in to. Adding the two lines above should fix that. You will also need to give yourself a SAMBA password: man smbpasswd What am I doing wrong? I've read the SMB HOWTO among others. The issues above still confuse me... Thanks... try: http://www.undergrad.math.uwaterloo.ca/~djbrosem/sambahowto/Samba-Beginners-HOWTO.html It's a work in progress, so not ready for prime-time yet, but I've got some pretty positive feedback on it. The package information for debian needs to be updated, so don't treat it as gospel, just a word of caution. The smb.conf file should do what you need, though, and AFAIK, it's the only info on SAMBA that explains win95 configuration. HTH -Dano -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: SAMBA help.
When you say yours is called ASGARD, does that mean you named your linux box ASGARD too? So I have to edit /etc/hosts and the rest to rename my machine? Hmmm... I like the intranet setup a lot. But I definitely need to learn SAMBA; so do I have to rename my linux box, edit host files etc? Thanks... NatePuri Certified Law Student Debian GNU/Linux Monk McGeorge School of Law [EMAIL PROTECTED] http://ompages.com On Fri, 19 Mar 1999, Daniel Brosemer wrote: On Fri, 19 Mar 1999, Paul Nathan Puri wrote: I need to know if I need to rename my network 'WORKGROUP' to be able to share drives and printers with windows. I've currently named my network 'natepuri.com.' It's not a registered name, yet. I'll register it when I get the money. I don't believe this is valid. This is not an internet domain it wants, but rather, a lanman domain, I don't think it can contain '.'s Does samba require WORKGROUP? Or is that just a variable for whatever I want to call my network. Whatever you want, mine is called ASGARD. Presently all tcp/ip connections over my LAN are very function. IP MASQ is functional as well. However, I have the client section in the network window in the control panel set to 'Log on the Windows NT domain.' Previously I had the 'Windows NT domain:' set to 'natepuri.com,' that didn't work so I set it to 'WORKGROUP' and that didn't work. You must change this in both SAMBA and in Win95, you also need to have in your smb.conf the lines: domain master = yes domain logons = yes I had 'Access Control' set to 'User-level access control' and first had the list of users set to 'natepuri.com' then to 'WORKGROUP.' Neither worked. I can't yet get this part to work either. Maybe eventually, does anyone on the list have this working? I'm using 'client for microsoft networks.' Samba is running in daemon mode. When I boot windows, it says 'cannot log on to Windows NT domain, some network services will be unavailable.' (or something like that). This is probably due to it not thinking your SAMBA server is a domain master for the domain you have told it to log in to. Adding the two lines above should fix that. You will also need to give yourself a SAMBA password: man smbpasswd What am I doing wrong? I've read the SMB HOWTO among others. The issues above still confuse me... Thanks... try: http://www.undergrad.math.uwaterloo.ca/~djbrosem/sambahowto/Samba-Beginners-HOWTO.html It's a work in progress, so not ready for prime-time yet, but I've got some pretty positive feedback on it. The package information for debian needs to be updated, so don't treat it as gospel, just a word of caution. The smb.conf file should do what you need, though, and AFAIK, it's the only info on SAMBA that explains win95 configuration. HTH -Dano -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: SAMBA help.
On Fri, 19 Mar 1999, Paul Nathan Puri wrote: When you say yours is called ASGARD, does that mean you named your linux box ASGARD too? No, my linux box is bolverk, and the windows machine is FRIGG. My workgroup is ASGARD ie. I have 'workgroup = ASGARD' in my smb.conf file. So I have to edit /etc/hosts and the rest to rename my machine? Hmmm... Don't rename your machine unless you can't do a 'hostname' without getting '.'s in the name. At work, I do: [EMAIL PROTECTED]:[~/tinfly]$ hostname penguin1 So it doesn't return penguin1.glfc.forestry.ca which is good, that's what you want. I like the intranet setup a lot. But I definitely need to learn SAMBA; so do I have to rename my linux box, edit host files etc? Thanks... Yes, edit the host files. You should have an entry in your /etc/hosts and/or /etc/lmhosts for your windows box(en) (as explained in my HowTo) unless you are running a nameserver, then, you add entries for your clients to your nameserver. You may also find it of benefit to run a WINS setup, this will be covered in detail in a later version of my HowTo, but it's fairly straightforward from reading the SAMBA docs. HTH -Dano
Re: SAMBA help.
*- On 19 Mar, Paul Nathan Puri wrote about Re: SAMBA help. When you say yours is called ASGARD, does that mean you named your linux box ASGARD too? So I have to edit /etc/hosts and the rest to rename my machine? Hmmm... I like the intranet setup a lot. But I definitely need to learn SAMBA; so do I have to rename my linux box, edit host files etc? Thanks... No. The you need to give your group of PC's a workgroup name, I use the generic HOME so all PC's in the local net will be in the workgroup called HOME. Then each PC has it's own netbios name, by default it uses the first part of the DNS name. From the smb.conf man page netbios name (G) This sets the NetBIOS name by which a Samba server is known. By default it is the same as the first component of the host´s DNS name. If a machine is a browse server or logon server this name (or the first component of the hosts DNS name) will be the name that these services are advertised under. See also netbios aliases. Default: Machine DNS name. Example: netbios name = MYNAME workgroup (G) This controls what workgroup your server will appear to be in when queried by clients. Note that this parameter also controls the Domain name used with the security=domain setting. Default: set at compile time to WORKGROUP Example: workgroup = MYGROUP I have a 2 pc home network like this. Linux box Win95 box IP192.168.1.1 192.168.1.2 fake DNSbrian.servis.snet angela.servis.snet workgroupHOME HOME netbios name BRIAN ANGELA in /etc/samba/smb.conf # Global parameters workgroup = HOME netbios name = BRIAN Althought the above 'netbios name' is not really needed. These do not have to be the same as the info in /etc/hosts in /etc/hosts 127.0.0.1 localhost loopback 192.168.1.1 brian.servis.snet brian 192.168.1.2 angela.servis.snet angela -- Brian - Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes. - unknown Mechanical Engineering[EMAIL PROTECTED] Purdue University http://www.ecn.purdue.edu/~servis -
Re: SAMBA: Help!!
On Tue, 8 Sep 1998, bmorgan wrote: This is a reposting of a previous message. I'm starting to get desperate. Any help would be greatly appreciated! I'm having trouble connecting to my debian machine from my windows machine using samba. I've successfully done this before, but now I've got several users connecting to the samba server for IP printing to jet-direct boxes. Right now, I've got my SMB.CONF file set so that it uses the workgroup linux and security = user. All my users should be able to connect with the same login name (student), and no password. Is it possible for multiple users to connect to the samba server all using the same login name? Or do I need to have a separate account for everyone who connects (the latter would NOT be a good scenario, if I can avoid it). Is there something else I need to set in the smb.conf file to allow multiple users with the same login name? Perhaps the security = parameter? If you use security = share no user/password information at all is needed to access the public shares on the machine. But if you like to restrict the access you will have to do it for each and every share in /etc/smb.conf shares example: [publicro] comment = Public read only browseable = yes read only = yes public = yes path = /public_readable_path [publicrw] comment = Read/write for all browseable = yes writable = yes public = yes path = /public_writable_path [studentfolder] comment = Read/write for user student browseable = yes writable = yes public = no path = /student_path valid users = student Good luck /Fredrik
Re: SAMBA: Help!!
Hi, so you are saying that the first user can login succesfully but after that no one else can log in? Are you sure Windows users are logged in their Windows 95 boxes as user student? If not do Start Menu:Shutdown:Close all programs and log in as a different user. I have never tried using null passwords but I guess it is doable... peloy.- bmorgan [EMAIL PROTECTED] wrote: This is a reposting of a previous message. I'm starting to get desperate. Any help would be greatly appreciated! I'm having trouble connecting to my debian machine from my windows machine using samba. I've successfully done this before, but now I've got several users connecting to the samba server for IP printing to jet-direct boxes. Right now, I've got my SMB.CONF file set so that it uses the workgroup linux and security = user. All my users should be able to connect with the same login name (student), and no password. Is it possible for multiple users to connect to the samba server all using the same login name? Or do I need to have a separate account for everyone who connects (the latter would NOT be a good scenario, if I can avoid it). Is there something else I need to set in the smb.conf file to allow multiple users with the same login name? Perhaps the security = parameter? Believe me, I've got everything else setup correctly. Null passwords, smbpassword file is set for no passwords as well. Thanks in advance. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- -- Eloy A. Paris Information Technology Department Rockwell Automation Venezuela Telephone: +58-2-9432311 Fax: +58-2-9431645
SAMBA: Help!!
This is a reposting of a previous message. I'm starting to get desperate. Any help would be greatly appreciated! I'm having trouble connecting to my debian machine from my windows machine using samba. I've successfully done this before, but now I've got several users connecting to the samba server for IP printing to jet-direct boxes. Right now, I've got my SMB.CONF file set so that it uses the workgroup linux and security = user. All my users should be able to connect with the same login name (student), and no password. Is it possible for multiple users to connect to the samba server all using the same login name? Or do I need to have a separate account for everyone who connects (the latter would NOT be a good scenario, if I can avoid it). Is there something else I need to set in the smb.conf file to allow multiple users with the same login name? Perhaps the security = parameter? Believe me, I've got everything else setup correctly. Null passwords, smbpassword file is set for no passwords as well. Thanks in advance.
Re: SAMBA: Help!!
On Tue, 8 Sep 1998, bmorgan wrote: : This is a reposting of a previous message. I'm starting to get : desperate. Any help would be greatly appreciated! [ snip ] You could give the Samba list a try. Send mail to [EMAIL PROTECTED] with a body of subscribe samba Your Name You could try the website at http://samba.anu.edu.au/samba You could try the newsgroup: comp.protocols.smb -- Nathan Norman MidcoNet 410 South Phillips Avenue Sioux Falls, SD mailto:[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
Samba help
I can mount my Linux server through a modem connection using mgetty. I am using NFS to mount a Novell file server. I am running Samba on all of my UNIX machines and can see all of them from remote access. I need to be able to mount and access a Win95 box from remote locations through remote access. I have tried smb_mount, with no luck. I also cannot see the mounted Novell partitions from remote. Has anyone done this before? If so, Please Help!! Thank you in advance, Andy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Samba help
Andy Scott wrote: I can mount my Linux server through a modem connection using mgetty. I am using NFS to mount a Novell file server. I am running Samba on all of my UNIX machines and can see all of them from remote access. I need to be able to mount and access a Win95 box from remote locations through remote access. I have tried smb_mount, with no luck. I also cannot see the mounted Novell partitions from remote. Has anyone done this before? If so, Please Help!! smb_mount will work (if anything will). Post the error messages that smb_mount is printing when you try to run it. -- Jens B. Jorgensen [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
