Samba Network Printing on 8.0
Hi, I want to get Samba running so that any computer on my lan can print to the printer connected to the new SuSE 8.0 server. I've never got Samba working before, so be gentle with me. In the past on other linux distros I've at least been able to get SWAT to run, but cannot even get that far right now. I used YAST2 to install the samba package. I'd like to get SWAT running now so I can use the GUI to edit my smb.conf file, among other things. So, I've edited /etc/inetd.conf to uncomment the line that says: swat stream tcp nowait.400 root /usr/sbin/swat swat I also see the following line in /etc/services swat 901/tcp # CONFLICT, not official assigned! I've edited my /etc/hosts.deny to look like this: # /etc/hosts.deny # See `man tcpd´ and `man 5 hosts_access´ as well as /etc/hosts.allow # for a detailed description. http-rman : ALL EXCEPT LOCAL swat: 127.0.0.1 192.168.0. because I want any local computer (192.168.0.x) to be able to access SWAT. I've rebooted once to allow inetd to restart but still if I type: http://localhost:901 or even http://192.168.0.1:901 into mozilla I get a pop-up box that says "The connection was refused when attempting to connect localhost:901" Also, if I do a netstat -an I don't see that the server is listening on 901 at all. Port 901 isn't even mentioned when I type that. All I want to do is print over the network! Ahhhh! Thanks for any help. Brian W. Carver
* Brian W. Carver; <bwcarver@earthlink.net> on 01 May, 2002 wrote:
Hi,
# /etc/hosts.deny # See `man tcpd� and `man 5 hosts_access� as well as /etc/hosts.allow # for a detailed description.
http-rman : ALL EXCEPT LOCAL swat: 127.0.0.1 192.168.0.
you should have put the the last line to hosts.allow you are DENY'ing here
I've rebooted once to allow inetd to restart but still if I type:
rcinetd restart (no need to reboot) -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
That got SWAT running! (I want to say, "Duh!" now that I think about it...) I misread this Step-by-step samba guide I found online and that is what screwed me up. Now comes the part that stumped me last time I tried this. Can someone point me to a howto that will clearly explain samba users and passwords versus linux users and passwords versus windows users and passwords? Because I get them all mixed up I think and what ended up happening last time is that no windows client could ever enter a password that would be accepted and provide access to the linux server no matter what I tried. I'll give it another go and with a little bit of luck/advice post later on the solution. Brian
Hi, I'd like to use one of our new 8.0 machines to act as an X server for NCD xterminals and Exceed sessions. I've commented the following entry from /var/X11R6/lib/xdm/xdm-config: !DisplayManager.requestPort: 0 and restarted xdm: ps ax | grep xdm 930 ? S 0:01 /usr/X11R6/bin/X :0 vt07 -auth /var/lib/xdm/authdir/authfiles/A:0-oH8lFW kill -HUP 930 The file /var/X11R6/lib/xdm/Xaccess is set to the default. Still can't get any xdmcp sessions on client xterminals. What am I missing here ? Is the comment character for /var/X11R6/lib/xdm/xdm-config a pling ? Thanks, Damian -- 11:57am up 7 days, 20:16, 12 users, load average: 0.02, 0.01, 0.00
On Wednesday 01 May 2002 14:04, Damian Ohara wrote:
!DisplayManager.requestPort: 0
It the newer versions of kdm you're supposed to do this from the kdmrc section [Xdmcp] Enable=True in /etc/sysconfig/displaymanager change the value DISPLAYMANAGER_REMOTE_ACCESS to "yes" and run SuSEconfig, for the "SuSEified" process. regards Anders
Thanks Anders, Unfortunately changing /etc/sysconfig/displaymanager and running SuSEconfig doesn't help. The kdmrc related file I can find is /etc/kde3rc and adding this entry doesn't seem to help. Am now looking at xdm-config and other files ('cos I don't know where else to look). Thanks, Damian Anders Johansson wrote:
On Wednesday 01 May 2002 14:04, Damian Ohara wrote:
!DisplayManager.requestPort: 0
It the newer versions of kdm you're supposed to do this from the kdmrc
section [Xdmcp] Enable=True
in /etc/sysconfig/displaymanager change the value DISPLAYMANAGER_REMOTE_ACCESS to "yes" and run SuSEconfig, for the "SuSEified" process.
regards Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Damian O'Hara using: SuSE Linux 8.0 12:37pm up 7 days, 20:56, 12 users, load average: 0.00, 0.03, 0.06
Anders & All, I found the kdmrc file - it's at /etc/opt/kde3/share/config/kdm/kdmrc and after editing it I had to bounce the machine for it to take effect. Now all is well. Thanks again for the FAST response! Cheers, Damian Anders Johansson wrote:
On Wednesday 01 May 2002 14:04, Damian Ohara wrote:
!DisplayManager.requestPort: 0
It the newer versions of kdm you're supposed to do this from the kdmrc
section [Xdmcp] Enable=True
in /etc/sysconfig/displaymanager change the value DISPLAYMANAGER_REMOTE_ACCESS to "yes" and run SuSEconfig, for the "SuSEified" process.
regards Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Damian O'Hara using: SuSE Linux 8.0 1:41pm up 7 days, 22:00, 12 users, load average: 0.24, 0.07, 0.02
I am sure that swat is a great tool, but have you tried using webmin? It provides a useful user interface for administration of almost all the packages that a linux box could use to serve the outside world and its own users. Look in: http://www.webmin.com/ If your samba is not installed properly, webmin will tell you! Peter On Wednesday 01 May 2002 11:22 am, you wrote:
Hi,
I want to get Samba running so that any computer on my lan can print to the printer connected to the new SuSE 8.0 server. I've never got Samba working before, so be gentle with me. In the past on other linux distros I've at least been able to get SWAT to run, but cannot even get that far right now.
I used YAST2 to install the samba package. I'd like to get SWAT running now so I can use the GUI to edit my smb.conf file, among other things.
So, I've edited /etc/inetd.conf to uncomment the line that says:
swat stream tcp nowait.400 root /usr/sbin/swat swat
I also see the following line in /etc/services
swat 901/tcp # CONFLICT, not official assigned!
I've edited my /etc/hosts.deny to look like this:
# /etc/hosts.deny # See `man tcpd and `man 5 hosts_access as well as /etc/hosts.allow # for a detailed description.
http-rman : ALL EXCEPT LOCAL swat: 127.0.0.1 192.168.0.
because I want any local computer (192.168.0.x) to be able to access SWAT.
I've rebooted once to allow inetd to restart but still if I type:
http://localhost:901 or even http://192.168.0.1:901 into mozilla I get a pop-up box that says "The connection was refused when attempting to connect localhost:901"
Also, if I do a netstat -an I don't see that the server is listening on 901 at all. Port 901 isn't even mentioned when I type that.
All I want to do is print over the network! Ahhhh! Thanks for any help.
Brian W. Carver
OK, One tiny problem to describe, but then for the benefit of posterity I'll describe how I printed across the network! When printing from the client computers, printing is fine, but it prints a blank page at the end. SuSE even has a description of this problem in their database, but I don't understand their solution. Anyone able to explain it to a dummy? See: http://sdb.suse.de/en/sdb/html/ke_netprint-trouble.html ***Solution for network printing on 8.0:*** Install samba. Edit /etc/inetd.conf to uncomment the line that says: swat stream tcp nowait.400 root /usr/sbin/swat swat Edit /etc/hosts.allow to contain: swat: 127.0.0.1 192.168.0. if like me, you want any local computer (192.168.0.x) to be able to access SWAT. Type http://localhost:901 into a web browser. Use swat to set up things. I'll include my smb.conf as an attachment to show you how I set up my printer and a couple of shared directories. You can also follow the same advice I did from http://plug.phoenix.az.us/step-by-step/samba/toc.html which is and old but still useful "Samba Server Step-by-Step Guide". The one thing he doesn't tell you in that guide is to go to SWAT's passwords section and create a samba user for each client computer. You'll have to have a linux user on the server for each of these computers too. Then I made sure my windows computers were actually using the same user names and passwords for logging into windows (control panel:users) and then finally in swat click on ENABLE USER for each user you've created. After that the server computer showed up in Network Neighborhood and I could set up a network printer in Windows with the settings:printer:wizard thingy. Good luck. I feel like some of what works for me, works on accident and I don't really understand what I've done myself. I just know the clients can print, and I'm thrilled with that. Brian Brian W. Carver wrote:
Hi,
I want to get Samba running so that any computer on my lan can print to the printer connected to the new SuSE 8.0 server. I've never got Samba working before, so be gentle with me. In the past on other linux distros I've at least been able to get SWAT to run, but cannot even get that far right now.
I used YAST2 to install the samba package. I'd like to get SWAT running now so I can use the GUI to edit my smb.conf file, among other things.
So, I've edited /etc/inetd.conf to uncomment the line that says:
swat stream tcp nowait.400 root /usr/sbin/swat swat
I also see the following line in /etc/services
swat 901/tcp # CONFLICT, not official assigned!
I've edited my /etc/hosts.deny to look like this:
# /etc/hosts.deny # See `man tcpd´ and `man 5 hosts_access´ as well as /etc/hosts.allow # for a detailed description.
http-rman : ALL EXCEPT LOCAL swat: 127.0.0.1 192.168.0.
because I want any local computer (192.168.0.x) to be able to access SWAT.
I've rebooted once to allow inetd to restart but still if I type:
http://localhost:901 or even http://192.168.0.1:901 into mozilla I get a pop-up box that says "The connection was refused when attempting to connect localhost:901"
Also, if I do a netstat -an I don't see that the server is listening on 901 at all. Port 901 isn't even mentioned when I type that.
All I want to do is print over the network! Ahhhh! Thanks for any help.
Brian W. Carver
# Samba config file created using SWAT # from localhost (127.0.0.1) # Date: 2002/05/01 04:43:18 # Global parameters [global] interfaces = 192.168.0.1/24 127.0.0.1/24 bind interfaces only = Yes security = SHARE encrypt passwords = Yes map to guest = Bad User log file = /var/log/samba/log.%m time server = Yes socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY character set = ISO8859-15 os level = 2 dns proxy = No wins support = Yes guest account = smbuser hosts allow = 192.168.0.2 192.168.0.3 192.168.0.4 printing = lprng hide dot files = No veto files = /*.eml/*.nws/riched20.dll/*.{*}/ [homes] comment = Home Directories read only = No create mask = 0640 directory mask = 0750 guest ok = Yes [printers] comment = All Printers path = /var/tmp create mask = 0600 guest ok = Yes printable = Yes [printer1] path = /var/tmp read only = No create mask = 0600 guest ok = Yes printable = Yes printer name = printer1 oplocks = No [public] comment = Public path = /home/public read only = No create mask = 0664 directory mask = 0775 guest ok = Yes [data] comment = Data path = /home/samba/data read only = No create mask = 0660 directory mask = 0770 guest ok = Yes
participants (5)
-
Anders Johansson -
Brian W. Carver -
Damian Ohara -
Peter Lewis -
Togan Muftuoglu