[opensuse] Printing from Windows Computers to Suse Printers
Hello all, I remember doing this before, but I am sure things have changed in 11.3. I have 2 printers setup on my OS 11.3 and want to share one of them with a Win XP computer on my home network. I can see and setup the printer from the Win box but it shows a status of Access Denied. I did check online:http://en.opensuse.org/SDB:Printing_from_Windows_to_Linux but some things it refers to I just don't find. * 1.1 Step 1: YaST control center * 1.2 Step 2: Edit /etc/cups/mime.convs configuration file * 1.3 Step 3: Restart CUPS server I do not find the file in step #2. Thanks, Mike. back to searching.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/17/2010 2:28 PM, ka1ifq wrote:
Hello all,
I remember doing this before, but I am sure things have changed in 11.3.
I have 2 printers setup on my OS 11.3 and want to share one of them with a Win XP computer on my home network.
I can see and setup the printer from the Win box but it shows a status of Access Denied.
I did check online:http://en.opensuse.org/SDB:Printing_from_Windows_to_Linux but some things it refers to I just don't find.
* 1.1 Step 1: YaST control center * 1.2 Step 2: Edit /etc/cups/mime.convs configuration file * 1.3 Step 3: Restart CUPS server
I do not find the file in step #2.
Thanks, Mike.
back to searching.. I set it up through Yast printer setup as the user I'm logging into as. Worked great for me. Then just used Samba to connect. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
What I find is the simplest solution is to get the CUPS URL (e.g. http://xxxxx:631/printers/Lexmark) and put that into Windows. There's an option in the "Add Printer Wizard" to enter an HTTP URL. Then just choose any PostScript printer driver, even if your printer is not PostScript. I happen to have a WinXP VM up and there it is under "network printer" and then "connect to a printer on the internet oor on a home or office network" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Oct 17 14:28 ka1ifq wrote (shortened):
I remember doing this before, but I am sure things have changed in 11.3.
I have 2 printers setup on my OS 11.3 and want to share one of them with a Win XP computer on my home network.
I can see and setup the printer from the Win box but it shows a status of Access Denied.
I did check online: http://en.opensuse.org/SDB:Printing_from_Windows_to_Linux
This article is outdated and incomplete (in particular Samba is missing and/or how to access a CUPS server directly from Windows via IPP) and would need major changes and enhancements to become actually useful. I guess Win XP does not yet support to access a CUPS server directly via its native IPP protocol so that I think you need a Samba server running on the Linux server to provide to the Win XP computers its traditional printer shares. Since a longer time Samba forwards print jobs which it got from Windowns explicitely as "raw" via a line like cups options = raw in /etc/samba/smb.conf so that also no change regarding application/octet-stream in a mime.convs file should be needed. But I am not at all a Samba expert.
but some things it refers to I just don't find.
* 1.1 Step 1: YaST control center * 1.2 Step 2: Edit /etc/cups/mime.convs configuration file * 1.3 Step 3: Restart CUPS server
I do not find the file in step #2.
Since CUPS V1.4b1 the standard MIME types are installed in DataDir/mime (CUPS STR #2719 http://www.cups.org/str.php?L2719) so that it is now (i.e. since openSUSE 11.3) /usr/share/cups/mime/mime.convs and /usr/share/cups/mime/mime.types but application/octet-stream should now be enabled by default so that no longer any change therein should be needed. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello,
This article is outdated and incomplete (in particular Samba is missing and/or how to access a CUPS server directly from Windows via IPP) and would need major changes and enhancements to become actually useful.
I guess Win XP does not yet support to access a CUPS server directly via its native IPP protocol so that I think you need a Samba server running on the Linux server to provide to the Win XP computers its traditional printer shares.
Since a longer time Samba forwards print jobs which it got from Windowns explicitely as "raw" via a line like cups options = raw in /etc/samba/smb.conf so that also no change regarding application/octet-stream in a mime.convs file should be needed.
But I am not at all a Samba expert.
Since CUPS V1.4b1 the standard MIME types are installed in DataDir/mime (CUPS STR #2719 http://www.cups.org/str.php?L2719) so that it is now (i.e. since openSUSE 11.3) /usr/share/cups/mime/mime.convs and /usr/share/cups/mime/mime.types but application/octet-stream should now be enabled by default so that no longer any change therein should be needed.
Kind Regards Johannes Meixner
Thanks for the info, I'll revisit this in a couple days and have another shot at it. Thanks, Mike. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 Oct 2010 15:53:45 ka1ifq wrote:
Thanks for the info, I'll revisit this in a couple days and have another shot at it.
Thanks, Mike.
Can you tell us how you got on? I'm struggling with same problem here :( Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/22/2010 05:16 PM, Bob Williams wrote:
On Tuesday 19 Oct 2010 15:53:45 ka1ifq wrote:
Thanks for the info, I'll revisit this in a couple days and have another shot at it.
Thanks, Mike.
Can you tell us how you got on? I'm struggling with same problem here :(
Bob
It's a two part setup: (1) configure cups on the server, (2) configure the
windows client. I haven't had much luck letting yast do it, so I just edit
cupsd.conf by hand. I have added quotes on the right as further explanation.
Before you edit your cupsd.conf, 'cp /etc/cups/cupsd.conf /etc/cups/cupsd.conf.orig'
For cups on the server, something similar to the following in /etc/cupsd.conf
works fine:
ServerName nirvana.3111skyline.com # fully qualified host.domain
ServerAdmin admin@nirvana.3111skyline.com # the admin at that host.domain
ServerAlias nirvana # hostname
ServerAlias www.3111skyline.com # any cname alias
ServerAlias localhost # always include localhost
Port 631 # default port (but hard code it)
LogLevel warn
HostNameLookups Off
Timeout 180
PreserveJobFiles Yes
PreserveJobHistory Yes
DefaultPaperSize Letter
SystemGroup sys root wheel # groups with access
# hardcode all at 631
# cups will grab 443 if loaded
# before httpd
Listen localhost:631
Listen nirvana.3111skyline.com:631 # no I don't leave the port open :p
Listen nirvana:631
Listen www.3111skyline.com:631
Listen 192.168.6.17:631
Listen /var/run/cups/cups.sock
Browsing On
BrowseOrder allow,deny
BrowseAllow all
BrowseLocalProtocols CUPS
BrowseRemoteProtocols CUPS
BrowseAddress @LOCAL
DefaultAuthType Basic
<Location />
Satisfy any
Order allow,deny
Allow @LOCAL # your local subnet
Allow (xxx.xxx.xxx.xxx) # your outside IP if you want
</Location>
On 10/22/2010 05:15 PM, David C. Rankin wrote:
On 10/22/2010 05:16 PM, Bob Williams wrote:
On Tuesday 19 Oct 2010 15:53:45 ka1ifq wrote:
Thanks for the info, I'll revisit this in a couple days and have another shot at it.
Thanks, Mike.
Can you tell us how you got on? I'm struggling with same problem here :(
Bob
It's a two part setup: (1) configure cups on the server, (2) configure the windows client. I haven't had much luck letting yast do it, so I just edit cupsd.conf by hand. I have added quotes on the right as further explanation. Before you edit your cupsd.conf, 'cp /etc/cups/cupsd.conf /etc/cups/cupsd.conf.orig'
For cups on the server, something similar to the following in /etc/cupsd.conf works fine:
ServerName nirvana.3111skyline.com # fully qualified host.domain ServerAdmin admin@nirvana.3111skyline.com # the admin at that host.domain ServerAlias nirvana # hostname ServerAlias www.3111skyline.com # any cname alias ServerAlias localhost # always include localhost Port 631 # default port (but hard code it) LogLevel warn HostNameLookups Off Timeout 180 PreserveJobFiles Yes PreserveJobHistory Yes DefaultPaperSize Letter SystemGroup sys root wheel # groups with access # hardcode all at 631 # cups will grab 443 if loaded # before httpd Listen localhost:631 Listen nirvana.3111skyline.com:631 # no I don't leave the port open :p Listen nirvana:631 Listen www.3111skyline.com:631 Listen 192.168.6.17:631 Listen /var/run/cups/cups.sock Browsing On BrowseOrder allow,deny BrowseAllow all BrowseLocalProtocols CUPS BrowseRemoteProtocols CUPS BrowseAddress @LOCAL DefaultAuthType Basic <Location /> Satisfy any Order allow,deny Allow @LOCAL # your local subnet Allow (xxx.xxx.xxx.xxx) # your outside IP if you want </Location>
Satisfy any Order allow,deny Allow @LOCAL Allow (xxx.xxx.xxx.xxx) # your outside IP if you want </Location> AuthType Default Require user @SYSTEM Order allow,deny Satisfy any Allow @LOCAL Allow (xxx.xxx.xxx.xxx) # your outside IP if you want </Location> <snip>
** RESTART cupsd 'rccups restart'
(2) Then on the windows boxes, just use network neighborhood to browse to the printer, rt-click & install, choose the right driver.
Also, check your samba config. I've included the relevant print setup from /etc/samba/smb.conf below:
19:09 nirvana:~> noc /etc/samba/smb.conf [global] use sendfile = No <snip> printcap name = cups load printers = yes printing = cups show add printer wizard = no disable spoolss = yes <snip> smb ports = 139 hosts allow = 192.168.6. 127. # subnet + don't forget localhost <snip> name resolve order = wins lmhosts bcast # change as required wins support = yes <snip> [printers] comment = All Printers path = /var/spool/samba # make sure permissions are 0777 browseable = no guest ok = yes public = yes writable = no printable = yes create mode = 0700 use client driver = yes [print$] path = /var/lib/samba/drivers browseable = yes write list = @adm root guest ok = yes inherit permissions = yes
HTH!
All good info. Don't forget to adjust firewall as well. If you open 631, you can configure a printer to use IPP even without samba running. Windows has supported IPP since win98. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 23 Oct 2010 01:15:21 David C. Rankin wrote:
On 10/22/2010 05:16 PM, Bob Williams wrote:
On Tuesday 19 Oct 2010 15:53:45 ka1ifq wrote:
Thanks for the info, I'll revisit this in a couple days and have another shot at it.
Thanks, Mike.
Can you tell us how you got on? I'm struggling with same problem here :(
Bob
It's a two part setup: (1) configure cups on the server, (2) configure the windows client. I haven't had much luck letting yast do it, so I just edit cupsd.conf by hand. I have added quotes on the right as further explanation. Before you edit your cupsd.conf, 'cp /etc/cups/cupsd.conf /etc/cups/cupsd.conf.orig'
[snipped useful stuff]
HTH!
Thanks, David. I've successfully used your sample smb.conf to set up my samba server, and it works extremely well linux-to-linux. My laptop is dual boot, and when I'm logged in to openSUSE there, I can see all my /home shares on the desktop machine. Where it's falling over is in the Windows Vista incarnation, which refuses to see any other machines on the LAN. Very narcissistic! ;) I feel sure that if I could get the Windows sharing working, I would then be able to see the shared printer. Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/23/2010 4:02 AM, Bob Williams wrote:
Where it's falling over is in the Windows Vista incarnation, which refuses to see any other machines on the LAN. Very narcissistic!;) I feel sure that if I could get the Windows sharing working, I would then be able to see the shared printer. Do you have windows on the same work group? Are you allowing both smb and nmb in the suse firewall? Can you connect via the machine IP instead of hostname? Did you add the users w/ smbpasswd -a <username> ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 23 October 2010 06:36:23 Michael S. Dunsaavage wrote:
On 10/23/2010 4:02 AM, Bob Williams wrote:
Where it's falling over is in the Windows Vista incarnation,
which refuses to see any other machines on the LAN. Very narcissistic!;) I feel sure that if I could get the Windows sharing working, I would then be able to see the shared printer.
We are all like Vista, Bob. You can see house, but when you call people inside and no one answers, you can wait and call later. Vista is doing this for sure. I'm not sure for time interval, but it is quite frequent and, so far I know, it doesn't have built in stop after there is no 10 answers :) Funny is that Samba and CUPS are doing the same if set that way.
Do you have windows on the same work group? Are you allowing both smb and nmb in the suse firewall? Can you connect via the machine IP instead of hostname? Did you add the users w/ smbpasswd -a <username> ?
So, after all Michael said is fine, Linux machine is still not there for smb service if it doesn't announce it understands smb. Part of each Linux machine is firewall that doesn't let broadcast announcement trough. Everything is fine, broadcast packets fly on each side of the firewall, but nothing trough the wall. YaST Control Center >> Security and Users >> Firewall In Firewall Configuration: There is is list of functions on left side, select Broadcasting. Click on "Add" button that will start new configuration window, where you can choose service which you want to enable from drop down list. Samba browsing is the one that you want. Additionally you can limit network scope that will be used. Default is 0/0 which is any network. This is fine for basic test is it working, but you probably want to limit broadcasts to local network. In my case that would be 192.168.1.0/24 . Don't forget to tell firewall in Vista machine the same. Firewalls for windows are aware of broadcast importance, so chance that they will block that traffic is small. BTW, answer on question why is that not enabled by default is security. There was talk some time ago, but without volunteers that will learn how to change YaST Firewall there will be no change any soon. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 23 Oct 2010 17:38:58 Rajko M. wrote:
On Saturday 23 October 2010 06:36:23 Michael S. Dunsaavage wrote:
On 10/23/2010 4:02 AM, Bob Williams wrote:
Where it's falling over is in the Windows Vista incarnation,
which refuses to see any other machines on the LAN. Very narcissistic!;) I feel sure that if I could get the Windows sharing working, I would then be able to see the shared printer.
We are all like Vista, Bob. You can see house, but when you call people inside and no one answers, you can wait and call later. Vista is doing this for sure. I'm not sure for time interval, but it is quite frequent and, so far I know, it doesn't have built in stop after there is no 10 answers :)
Are you saying I should wait a bit longer?
Funny is that Samba and CUPS are doing the same if set that way.
Do you have windows on the same work group? Are you allowing both smb and nmb in the suse firewall? Can you connect via the machine IP instead of hostname? Did you add the users w/ smbpasswd -a <username> ?
See my earlier answer to Michael.
So, after all Michael said is fine, Linux machine is still not there for smb service if it doesn't announce it understands smb.
Part of each Linux machine is firewall that doesn't let broadcast announcement trough. Everything is fine, broadcast packets fly on each side of the firewall, but nothing trough the wall.
If I boot the Windows machine into openSUSE, then all the samba shares on the desktop machine are visible, both read and write. So, something's getting through the firewall.
YaST Control Center >> Security and Users >> Firewall
In Firewall Configuration: There is is list of functions on left side, select Broadcasting. Click on "Add" button that will start new configuration window, where you can choose service which you want to enable from drop down list.
Samba browsing is the one that you want. Additionally you can limit network scope that will be used. Default is 0/0 which is any network. This is fine for basic test is it working, but you probably want to limit broadcasts to local network. In my case that would be 192.168.1.0/24 .
OK. I've done that, but no change so far.
Don't forget to tell firewall in Vista machine the same. Firewalls for windows are aware of broadcast importance, so chance that they will block that traffic is small.
I'm not sure which services to allow. Windows calls them Exceptions. Anyway, I turned the Windows firewall off completely, and the desktop (samba) machine appeared briefly. However, clicking on it says it's not available and suggests I check my spelling..
BTW, answer on question why is that not enabled by default is security. There was talk some time ago, but without volunteers that will learn how to change YaST Firewall there will be no change any soon.
-- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/23/2010 3:09 PM, Bob Williams wrote:
I'm not sure which services to allow. Windows calls them Exceptions. Anyway, I turned the Windows firewall off completely, and the desktop (samba) machine appeared briefly. However, clicking on it says it's not available and suggests I check my spelling..
can you connect by manually typing in the Explorer address bar \\server or \\ip ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Michael, On Sunday 24 Oct 2010 00:10:57 Michael S. Dunsaavage wrote:
On 10/23/2010 3:09 PM, Bob Williams wrote:
I'm not sure which services to allow. Windows calls them Exceptions. Anyway, I turned the Windows firewall off completely, and the desktop (samba) machine appeared briefly. However, clicking on it says it's not available and suggests I check my spelling..
can you connect by manually typing in the Explorer address bar \\server or \\ip ?
Yes, that works. I can immediately see and browse all my /home shares. But the "Network" application in Windows Vista doesn't see my linux box. Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/24/2010 10:57 AM, Bob Williams wrote:
Hi Michael,
On Sunday 24 Oct 2010 00:10:57 Michael S. Dunsaavage wrote:
On 10/23/2010 3:09 PM, Bob Williams wrote:
I'm not sure which services to allow. Windows calls them Exceptions. Anyway, I turned the Windows firewall off completely, and the desktop (samba) machine appeared briefly. However, clicking on it says it's not available and suggests I check my spelling..
can you connect by manually typing in the Explorer address bar \\server or \\ip ?
Yes, that works. I can immediately see and browse all my /home shares. But the "Network" application in Windows Vista doesn't see my linux box.
Bob
Try the command (as root) rcnmb restart This has cleared up problems for me in the past. This may be because of which computer is demanding to be the browse master. In my experience, setting Samba to win all browser elections works best. YMMV. Also remember that windows is really slow scanning the local net. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 23 Oct 2010 12:36:23 Michael S. Dunsaavage wrote:
On 10/23/2010 4:02 AM, Bob Williams wrote:
Where it's falling over is in the Windows Vista incarnation,
which refuses to see any other machines on the LAN. Very narcissistic!;) I feel sure that if I could get the Windows sharing working, I would then be able to see the shared printer.
Do you have windows on the same work group?
Yes
Are you allowing both smb and nmb in the suse firewall?
I have "Samba Server" under Allowed Services. I thought both services would be included under that heading.
Can you connect via the machine IP instead of hostname?
No
Did you add the users w/ smbpasswd -a <username> ?
Yes. -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/23/2010 2:50 PM, Bob Williams wrote:
Are you allowing both smb
and nmb in the suse firewall? I have "Samba Server" under Allowed Services. I thought both services would be included under that heading.
Nope. Allow netbios in firewall. Alos make sure nmbd is running.
Can you connect via the machine IP instead of hostname? No can you not connect at all or just to the printer? can you do
$ smbclient -L <hostname or IP> and get a listing? Can you post your smb.conf without snipping stuff? And you may need to allow smbd in /etc/hosts.allow even for your network. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 24 Oct 2010 00:07:18 Michael S. Dunsaavage wrote:
On 10/23/2010 2:50 PM, Bob Williams wrote:
Are you allowing both smb
and nmb in the suse firewall?
I have "Samba Server" under Allowed Services. I thought both services would be included under that heading.
Nope. Allow netbios in firewall. Alos make sure nmbd is running.
Done this.
Can you connect via the machine IP instead
of hostname?
No
can you not connect at all or just to the printer? can you do
As steted in another reply, I can connect in Windows Explorer (which I hadn't thought of trying), but not through the Network connection wizardry.
$ smbclient -L <hostname or IP> and get a listing?
18:34 barrowhillfarm:~> sudo smbclient -L sputnik Enter root's password: session setup failed: NT_STATUS_LOGON_FAILURE The desktop machine running linux is called 'barrowhillfarm' The laptop running Windows is called 'sputnik' The Workgroup containing both of the above is called 'BARROWHILLFARM' Yes, I know that could be confusing ;)
Can you post your smb.conf without snipping stuff? And you may need to allow smbd in /etc/hosts.allow even for your network.
Here is my smb.conf file: # smb.conf is the main Samba configuration file. You find a full commented # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the # samba-doc package is installed. # Date: 2009-03-20 # This version of smb.conf was written on 2010.02.09 based on notes from # http://www.3111skyline.com/linux/openSUSE-server.php#samba [global] use sendfile = No workgroup = BARROWHILLFARM server string = Samba Server %v printcap name = cups load printers = yes printing = cups show add printer wizard = No log file = /var/log/samba/log.%m max log size = 500 log level = 03 time server = yes smb ports = 139 ; Limit smb ports to 139 to eliminate repetitive log messages hosts allow = 192.168.1. 127. domain logons = yes map to guest = bad user security = user encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd local master = yes os level = 80 domain master = No name resolve order = wins lmhosts bcast dns proxy = no ; Choose one or the other of the following wins support = Yes usershare allow guests = No usershare max shares = 100 add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ [homes] comment = Home Directories valid users = %S, %D%w%S browseable = No read only = No [music] comment = Music Collection path = /home/bob/music/ valid users = @music force user = bob force group = music admin users = bob browseable = Yes writeable = Yes inherit permissions = Yes [pictures] comment = Photo collection on barrowhillfarm path = /home/bob/Pictures valid users = @users force group = users admin users = bob browseable = Yes writeable = Yes inherit permissions = Yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes public = yes writeable = no printable = yes create mode = 0700 use client driver = yes [print$] path = /var/lib/samba/printers browseable = yes write list = @adm,sys,root guest ok = yes inherit permissions = yes ; Setting suitable for Winbind: ; write list = @"Domain Admins" root ; force group = +@"Domain Admins" ## Share disabled by YaST # [netlogon] -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/24/2010 01:08 PM, Bob Williams wrote:
On Sunday 24 Oct 2010 00:07:18 Michael S. Dunsaavage wrote:
On 10/23/2010 2:50 PM, Bob Williams wrote:
Are you allowing both smb
and nmb in the suse firewall?
I have "Samba Server" under Allowed Services. I thought both services would be included under that heading.
Nope. Allow netbios in firewall. Alos make sure nmbd is running.
Done this.
Can you connect via the machine IP instead
of hostname?
No
can you not connect at all or just to the printer? can you do
As steted in another reply, I can connect in Windows Explorer (which I hadn't thought of trying), but not through the Network connection wizardry.
$ smbclient -L <hostname or IP> and get a listing?
18:34 barrowhillfarm:~> sudo smbclient -L sputnik Enter root's password: session setup failed: NT_STATUS_LOGON_FAILURE
The desktop machine running linux is called 'barrowhillfarm' The laptop running Windows is called 'sputnik' The Workgroup containing both of the above is called 'BARROWHILLFARM'
what about just smbclient -U<regular user name> -Lbarrowhillfarm also IIRC, there is a limit of 11 characters to the netbios 'workgroup' name. If that still applies the workgroup name 'BARROWHILLFARM' could be your problem. Try changing it to 'BHFARM' and see if that helps. Also, set log level = 10 in smb.conf and restart smbd. That will make the logs really chatty and can help ID the problem. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 24 Oct 2010 19:57:02 David C. Rankin wrote:
On 10/24/2010 01:08 PM, Bob Williams wrote:
On Sunday 24 Oct 2010 00:07:18 Michael S. Dunsaavage wrote:
On 10/23/2010 2:50 PM, Bob Williams wrote:
Are you allowing both smb
and nmb in the suse firewall?
I have "Samba Server" under Allowed Services. I thought both services would be included under that heading.
Nope. Allow netbios in firewall. Alos make sure nmbd is running.
Done this.
Can you connect via the machine IP instead
of hostname?
No
can you not connect at all or just to the printer? can you do
As steted in another reply, I can connect in Windows Explorer (which I hadn't thought of trying), but not through the Network connection wizardry.
$ smbclient -L <hostname or IP> and get a listing?
18:34 barrowhillfarm:~> sudo smbclient -L sputnik Enter root's password: session setup failed: NT_STATUS_LOGON_FAILURE
The desktop machine running linux is called 'barrowhillfarm' The laptop running Windows is called 'sputnik' The Workgroup containing both of the above is called 'BARROWHILLFARM'
what about just
smbclient -U<regular user name> -Lbarrowhillfarm
OK. That gives: barrowhillfarm:~ # smbclient -Ubob -Lbarrowhillfarm Enter bob's password: Domain=[BARROWHILLFARM] OS=[Unix] Server=[Samba 3.4.3-3.6.1-2426-SUSE-SL11.2] Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (Samba Server 3.4.3-3.6.1-2426- SUSE-SL11.2) print$ Disk pictures Disk Photo collection on barrowhillfarm music Disk Music Collection tp0 Printer HP_PhotoSmart_8150 Stylus-CX5200 Printer EPSON Stylus CX5200 Photosmart-8100-series Printer HP Photosmart 8100 series bob Disk Home Directories Domain=[BARROWHILLFARM] OS=[Unix] Server=[Samba 3.4.3-3.6.1-2426-SUSE-SL11.2] Server Comment --------- ------- BARROWHILLFARM Samba Server 3.4.3-3.6.1-2426-SUSE-SL11.2 Workgroup Master --------- ------- BARROWHILLFARM BARROWHILLFARM
also IIRC, there is a limit of 11 characters to the netbios 'workgroup' name. If that still applies the workgroup name 'BARROWHILLFARM' could be your problem. Try changing it to 'BHFARM' and see if that helps.
Windows didn't object to that workgroup name, but I'll take your advice and try the shorter version ... tomorrow, as it's getting rather late here ;)
Also, set log level = 10 in smb.conf and restart smbd. That will make the logs really chatty and can help ID the problem.
Done. Thanks, Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/24/2010 06:10 PM, Bob Williams wrote:
Windows didn't object to that workgroup name, but I'll take your advice and try the shorter version ... tomorrow, as it's getting rather late here ;)
Also, set log level = 10 in smb.conf and restart smbd. That will make the logs really chatty and can help ID the problem.
I'm starting to think it's all on Vista's side. My Windows 7 has a
My workgroup is 12 characters, and no problems. problem finding the networks after a while. It would find it at first, and then it stopped. Also, just curious, I had to reboot my machine for a kernel update and when the Suse box came back up, Wndows 7 did find it. So did you try that? Maybe just restarting samba doesn't fix the master browser problem? Or you could at first completely try restarting network services? Or possibly on Vista, try a netconfig /release and see if it finds it after that? Just some ideas I would try if I was in front of the machine helping a client, figured I would send the suggestions along. -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 25 Oct 2010 01:22:17 Michael S. Dunsavage wrote:
On 10/24/2010 06:10 PM, Bob Williams wrote:
Windows didn't object to that workgroup name, but I'll take your advice and try the shorter version ... tomorrow, as it's getting rather late here ;)
My workgroup is 12 characters, and no problems.
Also, set log level = 10 in smb.conf and restart smbd. That will make the logs really chatty and can help ID the problem.
I'm starting to think it's all on Vista's side. My Windows 7 has a problem finding the networks after a while. It would find it at first, and then it stopped.
Also, just curious, I had to reboot my machine for a kernel update and when the Suse box came back up, Wndows 7 did find it. So did you try that? Maybe just restarting samba doesn't fix the master browser problem? Or you could at first completely try restarting network services? Or possibly on Vista, try a netconfig /release and see if it finds it after that?
Just some ideas I would try if I was in front of the machine helping a client, figured I would send the suggestions along.
Unfortunately, rebooting didn't work. Could you explain how I do the netconfig /release in Vista, please? Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/25/2010 08:08 AM, Bob Williams wrote:
Unfortunately, rebooting didn't work. Could you explain how I do the netconfig /release in Vista, please?
sorry sorry. in a cmd terminal ipconfig /renew all -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 25 Oct 2010 13:40:09 Michael S. Dunsavage wrote:
On 10/25/2010 08:08 AM, Bob Williams wrote:
Unfortunately, rebooting didn't work. Could you explain how I do the netconfig /release in Vista, please?
sorry sorry.
in a cmd terminal
ipconfig /renew all
Ah. That was interesting ... C:\Users\Bob>ipconfig /renew all Windows IP Configuration The operation failed as no adapter is in the state permissible for this operation. Registere User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/24/2010 05:10 PM, Bob Williams wrote:
smbclient -U<regular user name> -Lbarrowhillfarm
OK. That gives:
barrowhillfarm:~ # smbclient -Ubob -Lbarrowhillfarm Enter bob's password: Domain=[BARROWHILLFARM] OS=[Unix] Server=[Samba 3.4.3-3.6.1-2426-SUSE-SL11.2]
Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (Samba Server 3.4.3-3.6.1-2426- SUSE-SL11.2) print$ Disk pictures Disk Photo collection on barrowhillfarm music Disk Music Collection tp0 Printer HP_PhotoSmart_8150 Stylus-CX5200 Printer EPSON Stylus CX5200 Photosmart-8100-series Printer HP Photosmart 8100 series bob Disk Home Directories Domain=[BARROWHILLFARM] OS=[Unix] Server=[Samba 3.4.3-3.6.1-2426-SUSE-SL11.2]
Server Comment --------- ------- BARROWHILLFARM Samba Server 3.4.3-3.6.1-2426-SUSE-SL11.2
Workgroup Master --------- ------- BARROWHILLFARM BARROWHILLFARM
That all looks good: alchemy:~> smbclient -Udavid -Lnirvana Enter david's password: Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.5.5] Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (Samba 3.5.5) pdf-gen Printer PDF Generator print-pdf print$ Disk samba Disk Nirvana - Skyline, Pictures, Law LaserJet Printer Home Office Laserjet 4 david Disk Home Directories Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.5.5] Server Comment --------- ------- ARCHANGEL Samba 3.5.5 DCRGX dcrgx KILLERZ Zmans KillerZ Box NIRVANA Samba 3.5.5 SUPERSFF Samba 3.5.5 ZION Rankin's Computer Workgroup Master --------- ------- RB_LAW NIRVANA
also IIRC, there is a limit of 11 characters to the netbios 'workgroup' name. If that still applies the workgroup name 'BARROWHILLFARM' could be your problem. Try changing it to 'BHFARM' and see if that helps.
Windows didn't object to that workgroup name, but I'll take your advice and try the shorter version ... tomorrow, as it's getting rather late here ;)
Windows won't complain, it's samba I'm worried about. Looks like I'm wrong on the netbios name at 11. It is actually a 15 character limit: http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.h... WINS: The Windows Internetworking Name Server Use of WINS (either Samba WINS or MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers its name together with a name_type value for each of several types of service it has available. It registers its name directly as a unique (the type 0x03) name. It also registers its name if it is running the LanManager-compatible server service (used to make shares and printers available to other users) by registering the server (the type 0x20) name. All NetBIOS names are up to 15 characters in length. The name_type variable is added to the end of the name, thus creating a 16 character name. Any name that is shorter than 15 characters is padded with spaces to the 15th character. Thus, all NetBIOS names are 16 characters long (including the name_type information). WINS can store these 16-character names as they get registered. A client that wants to log onto the network can ask the WINS server for a list of all names that have registered the NetLogon service name_type. This saves broadcast traffic and greatly expedites logon processing. Since broadcast name resolution cannot be used across network segments, this type of information can only be provided via WINS or via a statically configured lmhosts file that must reside on all clients in the absence of WINS.
Also, set log level = 10 in smb.conf and restart smbd. That will make the logs really chatty and can help ID the problem. Done.
Thanks,
Bob
Good luck -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/24/2010 08:27 PM, David C. Rankin wrote:
On 10/24/2010 05:10 PM, Bob Williams wrote:
smbclient -U<regular user name> -Lbarrowhillfarm
OK. That gives:
barrowhillfarm:~ # smbclient -Ubob -Lbarrowhillfarm Enter bob's password: Domain=[BARROWHILLFARM] OS=[Unix] Server=[Samba 3.4.3-3.6.1-2426-SUSE-SL11.2]
Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (Samba Server 3.4.3-3.6.1-2426- SUSE-SL11.2) print$ Disk pictures Disk Photo collection on barrowhillfarm music Disk Music Collection tp0 Printer HP_PhotoSmart_8150 Stylus-CX5200 Printer EPSON Stylus CX5200 Photosmart-8100-series Printer HP Photosmart 8100 series bob Disk Home Directories Domain=[BARROWHILLFARM] OS=[Unix] Server=[Samba 3.4.3-3.6.1-2426-SUSE-SL11.2]
Server Comment --------- ------- BARROWHILLFARM Samba Server 3.4.3-3.6.1-2426-SUSE-SL11.2
Workgroup Master --------- ------- BARROWHILLFARM BARROWHILLFARM
That all looks good:
alchemy:~> smbclient -Udavid -Lnirvana Enter david's password: Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.5.5]
Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (Samba 3.5.5) pdf-gen Printer PDF Generator print-pdf print$ Disk samba Disk Nirvana - Skyline, Pictures, Law LaserJet Printer Home Office Laserjet 4 david Disk Home Directories Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.5.5]
Server Comment --------- ------- ARCHANGEL Samba 3.5.5 DCRGX dcrgx KILLERZ Zmans KillerZ Box NIRVANA Samba 3.5.5 SUPERSFF Samba 3.5.5 ZION Rankin's Computer
Workgroup Master --------- ------- RB_LAW NIRVANA
also IIRC, there is a limit of 11 characters to the netbios 'workgroup' name. If that still applies the workgroup name 'BARROWHILLFARM' could be your problem. Try changing it to 'BHFARM' and see if that helps.
Windows didn't object to that workgroup name, but I'll take your advice and try the shorter version ... tomorrow, as it's getting rather late here ;)
Windows won't complain, it's samba I'm worried about. Looks like I'm wrong on the netbios name at 11. It is actually a 15 character limit:
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.h...
WINS: The Windows Internetworking Name Server
Use of WINS (either Samba WINS or MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers its name together with a name_type value for each of several types of service it has available. It registers its name directly as a unique (the type 0x03) name. It also registers its name if it is running the LanManager-compatible server service (used to make shares and printers available to other users) by registering the server (the type 0x20) name.
All NetBIOS names are up to 15 characters in length. The name_type variable is added to the end of the name, thus creating a 16 character name. Any name that is shorter than 15 characters is padded with spaces to the 15th character. Thus, all NetBIOS names are 16 characters long (including the name_type information).
WINS can store these 16-character names as they get registered. A client that wants to log onto the network can ask the WINS server for a list of all names that have registered the NetLogon service name_type. This saves broadcast traffic and greatly expedites logon processing. Since broadcast name resolution cannot be used across network segments, this type of information can only be provided via WINS or via a statically configured lmhosts file that must reside on all clients in the absence of WINS.
Also, set log level = 10 in smb.conf and restart smbd. That will make the logs really chatty and can help ID the problem.
Done.
Thanks,
Bob
Good luck
Also, try local master = Yes preferred master = Yes os level = 65 under glboal Local master will make it a local network master browser - should be on *one* samba server. Makes it the local browser. preferred browser should be on only *one* samba server - should be master browser for workgroup os level should also be on *one* samba server - this will beat out any NT domain browser, maybe not needed, but maybe w/ Vista. Won't hurt. Also when restarting samba services after configuration changes, restart nmbd as well. -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 25 Oct 2010 01:45:09 Michael S. Dunsavage wrote:
On 10/24/2010 08:27 PM, David C. Rankin wrote:
On 10/24/2010 05:10 PM, Bob Williams wrote:
smbclient -U<regular user name> -Lbarrowhillfarm
OK. That gives:
barrowhillfarm:~ # smbclient -Ubob -Lbarrowhillfarm Enter bob's password: Domain=[BARROWHILLFARM] OS=[Unix] Server=[Samba 3.4.3-3.6.1-2426-SUSE-SL11.2]
Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (Samba Server 3.4.3-3.6.1-2426-
SUSE-SL11.2)
print$ Disk pictures Disk Photo collection on barrowhillfarm music Disk Music Collection tp0 Printer HP_PhotoSmart_8150 Stylus-CX5200 Printer EPSON Stylus CX5200 Photosmart-8100-series Printer HP Photosmart 8100 series bob Disk Home Directories
Domain=[BARROWHILLFARM] OS=[Unix] Server=[Samba 3.4.3-3.6.1-2426-SUSE-SL11.2]
Server Comment --------- ------- BARROWHILLFARM Samba Server 3.4.3-3.6.1-2426-SUSE-SL11.2
Workgroup Master --------- ------- BARROWHILLFARM BARROWHILLFARM
That all looks good:
alchemy:~> smbclient -Udavid -Lnirvana Enter david's password: Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.5.5]
Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (Samba 3.5.5) pdf-gen Printer PDF Generator print-pdf print$ Disk samba Disk Nirvana - Skyline, Pictures, Law LaserJet Printer Home Office Laserjet 4 david Disk Home Directories
Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.5.5]
Server Comment --------- ------- ARCHANGEL Samba 3.5.5 DCRGX dcrgx KILLERZ Zmans KillerZ Box NIRVANA Samba 3.5.5 SUPERSFF Samba 3.5.5 ZION Rankin's Computer
Workgroup Master --------- ------- RB_LAW NIRVANA
also IIRC, there is a limit of 11 characters to the netbios 'workgroup' name. If that still applies the workgroup name 'BARROWHILLFARM' could be your problem. Try changing it to 'BHFARM' and see if that helps.
Windows didn't object to that workgroup name, but I'll take your advice and try the shorter version ... tomorrow, as it's getting rather late here ;)
Windows won't complain, it's samba I'm worried about. Looks like I'm wrong on the netbios name at 11. It is actually a 15 character limit:
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsin g.html
WINS: The Windows Internetworking Name Server
Use of WINS (either Samba WINS or MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers its name together with a name_type value for each of several types of service it has available. It registers its name directly as a unique (the type 0x03) name. It also registers its name if it is running the LanManager-compatible server service (used to make shares and printers available to other users) by registering the server (the type 0x20) name.
All NetBIOS names are up to 15 characters in length. The name_type variable is added to the end of the name, thus creating a 16 character name. Any name that is shorter than 15 characters is padded with spaces to the 15th character. Thus, all NetBIOS names are 16 characters long (including the name_type information).
WINS can store these 16-character names as they get registered. A client that wants to log onto the network can ask the WINS server for a list of all names that have registered the NetLogon service name_type. This saves broadcast traffic and greatly expedites logon processing. Since broadcast name resolution cannot be used across network segments, this type of information can only be provided via WINS or via a statically configured lmhosts file that must reside on all clients in the absence of WINS.
Also, set log level = 10 in smb.conf and restart smbd. That will make the logs really chatty and can help ID the problem.
Done.
Thanks,
Bob
Good luck
Also, try
local master = Yes preferred master = Yes os level = 65
under glboal
Local master will make it a local network master browser - should be on *one* samba server. Makes it the local browser. preferred browser should be on only *one* samba server - should be master browser for workgroup os level should also be on *one* samba server - this will beat out any NT domain browser, maybe not needed, but maybe w/ Vista. Won't hurt.
Also when restarting samba services after configuration changes, restart nmbd as well.
Done all that, no difference, I'm afraid. As it's looking more and more like Vista problem, it could be considered a bit OT here :( I'm less bothered by the printer sharing problem now, but I would like to be able to share /home on the Vista machine. What this brings home to me is how configurable linux is - just change some settings in a conf file (if you know what to change, of course) whereas in Windows World you are at the mercy of the GUI and whatever tools are provided there. Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/25/2010 08:16 AM, Bob Williams wrote:
able to share /home on the Vista machine. What this brings home to me is how configurable linux is - just change some settings in a conf file (if you know what to change, of course) whereas in Windows World you are at the mercy of the GUI and whatever tools are provided there.
You should still be able to right click in My Computer, or whatever Vista calls it and map a drive. We have already ascertained that we can see the server if typed in manually. -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 25 Oct 2010 13:42:01 Michael S. Dunsavage wrote:
On 10/25/2010 08:16 AM, Bob Williams wrote:
able to share /home on the Vista machine. What this brings home to me is how configurable linux is - just change some settings in a conf file (if you know what to change, of course) whereas in Windows World you are at the mercy of the GUI and whatever tools are provided there.
You should still be able to right click in My Computer, or whatever Vista calls it and map a drive. We have already ascertained that we can see the server if typed in manually.
You're absolutely right. I was getting lost in the trees :) Many thanks for your help. I think I'll find another way to connect the printer so that's accessible to all my machines. Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob Williams
Many thanks for your help. I think I'll find another way to connect the printer so that's accessible to all my machines.
One way is to install the lpr component in Windows. You will also need to install a postscript printer driver. I don't have any Windows machine here so I can't guide you through. Search the web for lpr and your Windows version. Charles -- "Never make any mistaeks." (Anonymous, in a mail discussion about to a kernel bug report.)
On Monday 25 Oct 2010 14:51:35 Charles Philip Chan wrote:
Bob Williams
writes:
Many thanks for your help. I think I'll find another way to connect the printer so that's accessible to all my machines.
One way is to install the lpr component in Windows. You will also need to install a postscript printer driver. I don't have any Windows machine here so I can't guide you through. Search the web for lpr and your Windows version.
Charles
Thanks, Charles. Windows is on a dual boot laptop, so it's not very practical to have it always on, with a printer hanging off it. That's why I was looking for a solution that covered Windows > Linux > printer. I'm currently looking at getting a router with a dedicated USB printer port. Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob Williams
Thanks, Charles. Windows is on a dual boot laptop, so it's not very practical to have it always on, with a printer hanging off it. That's why I was looking for a solution that covered Windows > Linux > printer.
I am not too sure what you mean by this. With the setup I am talking about, you will be printing with lpr to the lpd server (cups-lpd, in this case): http://www.cups.org/documentation.php/doc-1.4/man-cups-lpd.html on your Linux machine through TCP/IP. Charles -- "The IETF motto is 'rough consensus and running code'" -- Scott Bradner (Open Sources, 1999 O'Reilly and Associates)
On Monday 25 Oct 2010 16:13:33 Charles Philip Chan wrote:
Bob Williams
writes:
Thanks, Charles. Windows is on a dual boot laptop, so it's not very practical to have it always on, with a printer hanging off it. That's why I was looking for a solution that covered Windows > Linux > printer.
I am not too sure what you mean by this. With the setup I am talking about, you will be printing with lpr to the lpd server (cups-lpd, in this case):
http://www.cups.org/documentation.php/doc-1.4/man-cups-lpd.html
on your Linux machine through TCP/IP.
Charles
Oops, sorry. I should read more carefully before hitting the keyboard. Yes, there are lots of hits. I'll have a play with that later. Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.1-desktop, KDE 4.5.1 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/25/2010 09:51 AM, Bob Williams wrote:
Thanks, Charles. Windows is on a dual boot laptop, so it's not very practical to have it always on, with a printer hanging off it. That's why I was looking for a solution that covered Windows > Linux > printer.
Printing Vista -> Samba/Cups should work just fine. After setting up samba/cups, all I did in vista was use windows explorer -> network neighborhood -> microsoft networks -> BARROWHILLFARM -> printers (and then double-click on the printer, and choose the driver you need, and then test with print test page) You may also want to grab a wireshark trace of the communications with the printer to see if that points to anything weird. I have had more problems with cups-client breaking Linux->Linux printing than with vista->Linux printing lately... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/25/2010 09:05 AM, Bob Williams wrote:
Many thanks for your help. I think I'll find another way to connect the printer so that's accessible to all my machines.
That too could be done by manually typing in the address when setting up a network printer, couldn't it? -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/23/2010 03:02 AM, Bob Williams wrote:
On Saturday 23 Oct 2010 01:15:21 David C. Rankin wrote:
On 10/22/2010 05:16 PM, Bob Williams wrote:
On Tuesday 19 Oct 2010 15:53:45 ka1ifq wrote:
Thanks for the info, I'll revisit this in a couple days and have another shot at it.
Thanks, Mike.
Can you tell us how you got on? I'm struggling with same problem here :(
Bob
It's a two part setup: (1) configure cups on the server, (2) configure the windows client. I haven't had much luck letting yast do it, so I just edit cupsd.conf by hand. I have added quotes on the right as further explanation. Before you edit your cupsd.conf, 'cp /etc/cups/cupsd.conf /etc/cups/cupsd.conf.orig'
[snipped useful stuff]
HTH!
Thanks, David. I've successfully used your sample smb.conf to set up my samba server, and it works extremely well linux-to-linux. My laptop is dual boot, and when I'm logged in to openSUSE there, I can see all my /home shares on the desktop machine. Where it's falling over is in the Windows Vista incarnation, which refuses to see any other machines on the LAN. Very narcissistic! ;) I feel sure that if I could get the Windows sharing working, I would then be able to see the shared printer.
Bob
Bob, Here is the complete config (minus my admin share which I don't suggest using): http://www.3111skyline.com/dl/linux/apps/samba/smb.conf.current.txt Look at Lars comments in response to my original post. He has a few clean ups that you can do on my existing config. ( doesn't impact your issue, just old settings that are now defaults, etc..) I am using it with vista clients without any problem. I'll check later threads to see if you have got it solved already. (I'm in a bit of a rush :) Good luck. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Oct 22, 2010 at 07:15:21PM -0500, David C. Rankin wrote: [ 8< ]
Also, check your samba config. I've included the relevant print setup from /etc/samba/smb.conf below:
19:09 nirvana:~> noc /etc/samba/smb.conf [global] use sendfile = No
This is the upstream default setting (uds).
<snip> printcap name = cups
This is the explicit default setting with any SUSE product since (at least) 2005-06-16 12:47:22
load printers = yes
uds too.
printing = cups
Also since 2005-06-16 12:47:22
show add printer wizard = no disable spoolss = yes
Well, this sounds like you got hit by the existing printer spooler bugs.
<snip> smb ports = 139 hosts allow = 192.168.6. 127. # subnet + don't forget localhost <snip> name resolve order = wins lmhosts bcast # change as required wins support = yes <snip> [printers] comment = All Printers path = /var/spool/samba # make sure permissions are 0777
Why not using /var/tmp?
browseable = no guest ok = yes public = yes writable = no printable = yes
KISS and therefore use only one as in the default smb.conf. Makes your config file easier to read.
create mode = 0700 use client driver = yes [print$] path = /var/lib/samba/drivers browseable = yes write list = @adm root
Why not using the dfault ntadmin group? adm might be more generic I guess.
guest ok = yes inherit permissions = yes
What's the advantage of using "inherit permissions" at this point? Well, I also can't see a potential damage. Maybe the same as with the adm group? Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 10/23/2010 01:48 PM, Lars Müller wrote: Here I always defer to you on specific advise. The truth of the config is that it has just been adapted and updated since 2.0.2 (2001?) with the new defaults as they came along and with feedback on specific issues from the samba list (You, Jeremy, Jerry, John, Andrew (Bartlett & Tridgell), et al.) It probably needs a good going through to clean it completely up, but since it has just kept working..., working..., working... for the past 5-6 years all I've done is just add a tweak or two. see inline below:
On Fri, Oct 22, 2010 at 07:15:21PM -0500, David C. Rankin wrote: [ 8< ]
Also, check your samba config. I've included the relevant print setup from /etc/samba/smb.conf below:
19:09 nirvana:~> noc /etc/samba/smb.conf [global] use sendfile = No
This is the upstream default setting (uds).
Yep, dunno when that crept into the config, but it has remained since the first version it became relevant to...
<snip> printcap name = cups
This is the explicit default setting with any SUSE product since (at least) 2005-06-16 12:47:22
same
load printers = yes
uds too.
same
printing = cups
Also since 2005-06-16 12:47:22
same
show add printer wizard = no disable spoolss = yes
Well, this sounds like you got hit by the existing printer spooler bugs.
Yep, this came in 2006-2007 time frame. I know it was suggested when (2.2.7?) broke standalone support and I was going back and forth with Jerry, I think, building from sources sending in level 10 debugs. I've just never experimented removing it since.
<snip> smb ports = 139 hosts allow = 192.168.6. 127. # subnet + don't forget localhost <snip> name resolve order = wins lmhosts bcast # change as required wins support = yes <snip> [printers] comment = All Printers path = /var/spool/samba # make sure permissions are 0777
Why not using /var/tmp?
No reason other than that's where it was originally for 2.0.2 on Mandrake 7.2 and I just never changed it. Any reason to change now? I guess I'm just stuck in my ways. When I think temp print space I think 'spool' as in /var/spool, and I've just always had a /var/spool/samba so when printing goes to hell, I know where to look :p
browseable = no guest ok = yes public = yes writable = no printable = yes
KISS and therefore use only one as in the default smb.conf. Makes your config file easier to read.
Yes, I know 'guest ok = yes' and 'public = yes' are redundant, but that was one of the 'new config file had new default, so it got added, and the clean up was put off until an opportune time (like now) when I got a chance to talk to a smart guy about it!
create mode = 0700 use client driver = yes [print$] path = /var/lib/samba/drivers browseable = yes write list = @adm root
Why not using the dfault ntadmin group?
I should now, but there was no ntadmin in 2.0.2 ;-)
adm might be more generic I guess.
guest ok = yes inherit permissions = yes
What's the advantage of using "inherit permissions" at this point?
Dunno, the entire [print$] share was a new default that showed up (long long ago) and since I never hosted any server based drivers... I didn't do an exegesis on it :p
Well, I also can't see a potential damage. Maybe the same as with the adm group?
Lars
Other than deleting the redundant defaults, removing 'inherit permissions' from print$ and possibly moving the spool from /var/spool/samba to /var/tmp, you see anything else I should tweak or remove? Thanks for helping out with the smb.conf. I know I really only give it a look when something breaks or new defaults appear when I diff the new version against my existing. So I know it is in need of a once over. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Oct 23, 2010 at 07:05:39PM -0500, David C. Rankin wrote: [ 8< ]
Other than deleting the redundant defaults, removing 'inherit permissions' from print$ and possibly moving the spool from /var/spool/samba to /var/tmp, you see anything else I should tweak or remove?
No. Only one suggestion I have: Please use bugzilla if you think there is a Samba defect. See http://en.openSUSE.org/Samba as this article also includes pointers to an openSUSE Samba bugreporting howto. It also includes a pointer to the generic samba trouble-shooting page at http://wiki.samba.org/index.php/Samba_Troubleshooting Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
participants (11)
-
Andrew Joakimsen -
Bob Williams -
Charles Philip Chan -
David C. Rankin -
Johannes Meixner -
jsa -
ka1ifq -
Lars Müller -
Michael S. Dunsaavage -
Michael S. Dunsavage
-
Rajko M.