[Samba] Win2K Printer Driver Problems - Landscape margins off, no collating.
Our environment: Samba 2.2.5 on RedHat 7.2 (Tried on two different servers) Printing handled by Cups 1.1.14-15 Printers shares available and print jobs being handled properly by cups. THE PROBLEM: New HP drivers uploaded to the PRINT$ share seem to be downloaded by clients correctly, however the following problems occur: 1. In Word, changing page setup to landscape results in a "Margins outside of printable range" error. Choosing "Fix" sets the left margin to 2.5" and cuts off half of the page. Any other application, even non MS apps, refuse to print landscape no matter what orientation in Page Setup. This happens for any model of printer as long as an HP driver is used. 2. Trying Use Client Driver = Yes in smb.conf results in no one (printer admins included) being able to save driver settings on the server or any installed printers. 3. The only workaround we have is to use the Win2K stock HP LaserJet 4 driver for all printers (including 4000's and 5000's) but this driver has a problem whereby it does not collate multiple copies. We have wiped ntprinters.tdb and ntdrivers.tdb (with samba stopped of course) and cleared the local driver cache on client machines. Still, the second the printer is re-installed the problem re-occurs. What is not clear is at what point Windows starts using the local copy of the driver that has been downloaded. If I change the driver on the server, everyone who uses that printer instantly gets the changes. All drivers work fine on a native Windows 2000 server or if the printer is defined as a local printer connected to port that points at the Samba server. Somehow, sonewhere the printer driver information is getting corrupted on the Samba servers. Any ideas would be appreciated. I have a way of rolling out all printers as local on a global basis but would rather avoid having to look after the local drivers on 180+ machines. Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] FW: The trouble with XP client...
I am a technical user new to Samba and Linux... I have successfully joined an XP client to the latest downloads of RH8.0 and SMB 2.2.5. The problem is when I login, I get the error message that xp cannot find the profiles folder and cannot save the local copy of the session at the end of the session. It cannot find the network folder. Any ideas?? Thanx a bunch!! [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Off-topic tcpdump/samba
Hello all I've been doing some TCP dumps of Samba among other things, to try to fish out a slight communications glitch that I suspect has to do with a bad IP stack on an older machine, and I'm wondering if any of you could help make my life a bit easier: When doing the dump, I used the '-C' flag which causes capture files to be rotated when they reach a certain size. I made the mistake of making this size too small, and now need to recombine all those files so I can avoid having to analyze file upon file of dump data separately. Using cat did NOT work, as analysis would never go beyond the equivalent of the first dump file. Any advice would be greatly appreciated. Another question: I have set up SSL to work for Samba clients, have 2 clients plus Samba PDC all using the same CA, all have their cert's signed by this CA, and a local copy of the CA cert (NOT the private key) and all have the required parameters set, BUT: the clients can only talk to the PDC, not each other!! Do I need to publish the CA's private key to the client machines to make this happen (hope NOT!!), or what am I missing? Best Diego -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Using the XP backup utility with SAmba
I set up a backup folder on my samba server today but I am not able to configure it to accept scheduled backups from the Win XP backup utility. I have coated a backup profile on my XP machine and set the backup path to the Samba directory. When I try to run the backup I get the error: "The Backup file name could not be used: \\Sorage\Backups\Davinci\Davinci.bkf Please ensure it is a valid path and that you have sufficient access" I am able to browse the directory just fine so I think it might be a permissions issue between the Backup utility and Samba or that it is logging in using a different username. Any Advice? _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] smbclient: protocol negotiation failed
When trying to connect to a samba server using smbclient on the local machine (or any other unix machine with smbclient), I get a "protocol negotiation failed" error. When I try to connect to the same server using a windows client it works just fine... Regardless of whether the client is on the same server or some other machine I get the following error message: [2002/10/07 15:10:34, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer I understand that this error may point to a network fault (perhaps) but I don't understand think that I have a network fault when running smbclient on the local machine. The machine is a Solaris 8 Sun box and authentication is being performed by Win2k Domain Controllers. The global section of my config is as follows: workgroup = MYDOMAIN server string = %h - Samba %v password level = 8 security = server password server = MYSERVER null passwords = no encrypt passwords = yes wins support = no wins server = 192.168.2.2 hosts allow = 192.168.1., 192.168.2. 192.168.3. fstype = Samba preserve case = yes domain master = no local master = no preferred master = no os level = 0 dead time= 0 locking = yes lock directory = /var/spool/samba hide dot files = yes public = no guest account = nobody browseable = yes log file = /log/samba/log.%m thoughts on this would be useful.. cheers, Carey Nairn ___ Carey Nairn Network and Systems Administrator Information Systems Branch Phone: (03) 6233 3077 Dept of Premier & CabinetFax:(03) 6224 3174 GPO Box 123b Hobart, Tasmania 7001 AUSTRALIA Mailto:[EMAIL PROTECTED] ___ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] FireWall Effects on Samba (Newbie)
I am fairly certain RH 7.1 out of the box blocks port 139. You will have to learn how to open up your ports to let samba work. I don't use RH anymore, but you may have either iptables or ipchains on your system. Joel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] mounting a win98 share
I am trying to perform a backup of a win98 share to the tape drive on my server. Until I upgraded to 2.2.5-1 everything was peachy. Now I am getting this: [root@chamber-gw samba]# mount -t smbfs -o password=** //10.0.10.150/paula /home/backup/paula/ INFO: Debug class all level = 3 (pid 25292 from pid 25292) opts: rw opts: password=*** mount.smbfs started (version 2.2.5) added interface ip=10.0.10.1 bcast=10.0.10.255 nmask=255.255.255.0 Connecting to 10.0.10.150 at port 139 25292: session request to 10.0.10.150 failed (Called name not present) Connecting to 10.0.10.150 at port 139 25292: session request to 10 failed (Called name not present) Connecting to 10.0.10.150 at port 139 25292: session request to *SMBSERVER failed (Called name not present) SMB connection failed Does anyone have a clue or idea why this is occuring now? I verified that the share is indeed there and the password is set correctly. The win98 box is not asking for a username and the share is tagged as read only. thanks, -- Guy Story, KC5GOI Itel-Tigerbyte LLC [EMAIL PROTECTED] 940.891.4575 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
Hmmm... I thought you can print well from the server itself? Are you sure you were ever using BSD printing. Maybe you were really using lprng. I think samba defaults to bsd. Have you got a printing parameter in your smb.conf? Joel On Sun, Oct 06, 2002 at 07:13:17PM -0700, Dan Sawyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Second update: > > On the advice of someone else on this mailing list, I converted from BSD > printing to CUPS (still using samba). Doing so has given me what is perhaps > a more identifiable error message. When I send a job to the server, I check > the que and get the following response: > > thedude@floyd:~> lpstat -t > scheduler is running > system default destination: lp > device for lp: samba://192.168.1.101/lp > lp accepting requests > printer lp disabled - > reason unknown > lp-1thedude 164864 Sun Oct 6 19:07:36 2002 > > So it seems that the printer is disabled for some reason. The job just stays > there in the que and never prints. > > - -Dan > > On Thursday 03 October 2002 15:23, Joel Hammer wrote: > > Do you understand how printing works with samba? > > Essentially, you just transfer the file to the samba spool directory, and > > invoke lpr to print the file. You will need to look at your smb.conf file > > to see what is supposed to happen. I would set up a share just for your > > printer and not rely on the generic printer share that smb.conf comes with. > > > > Here is the sort of printer share I have: > > This take a postscript file as input, invokes lpr to print to queue ps on > > the server, which translates postscript files for my lexmark printer. > > > > Joel > > > > > > > > [ps] > > path = /tmp > > read only = No > > create mask = 0700 > > guest ok = yes > > hosts allow = 192.168. > > printable = Yes > > printing = lprng > > print command = echo %J %p %s >> /tmp/junkJ;\ > >a="`echo '%J' | sed "s/^.*- //"`" ;\ > >echo This is truncated $a >> /tmp/junkJ;\ > >/usr/bin/lpr -Pps -J"$a" %s;\ > >rm %s > > lpq command = /usr/bin/lpq -Pps > > lprm command = /usr/bin/lprm -Pps %j > > lppause command = /usr/sbin/lpc hold z53 %j > > lpresume command = /usr/sbin/lpc release z53 %j > > share modes = No > > use client driver = yes > > > > On Thu, Oct 03, 2002 at 12:47:27PM -0700, Dan Sawyer wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > > > Hello, everyone - > > > > > > I've been trying for two weeks now to get my print server operational > > > under Samba. After walking through the howtos and tweaking the configs > > > per spec, it just ain't working. Printing from a client machine sends, > > > and then nothing happens. No error messages or anything similar. > > > > > > Printing from the server works fine, but not from the clients. > > > > > > Setup: > > > > > > 4 machine network, 3 clients, 1 samba file/print server > > > SuSE 7.3 running on all machines. > > > HP 2P parallel printer on lp0 of server > > > > > > What else can I tell you to help figure this out? > > > - -Dan Sawyer > > > -BEGIN PGP SIGNATURE- > > > Version: GnuPG v1.0.6 (GNU/Linux) > > > Comment: For info see http://www.gnupg.org > > > > > > iD8DBQE9nJ7TaB8ur/y6V8gRArm9AJ9rRc8yhDm5Catchqv4SXedOqs5qwCfSWS/ > > > 2IayciR10uTYysD/3F24UdE= > > > =TMQV > > > -END PGP SIGNATURE- > > > -- > > > To unsubscribe from this list go to the following URL and read the > > > instructions: http://lists.samba.org/mailman/listinfo/samba > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE9oO3BaB8ur/y6V8gRAiAJAJwNmGtKOhWamaEBO2oX2bTlI0T7DACfXWEj > WPZ2VS/XixCF6xBqgXbDQyc= > =nwXl > -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] FireWall Effects on Samba (Newbie)
Dear List, I have been wrestling with getting Samba 2.2.5 on Redhat 7.1 working on a Windows NT network containing W2K, W98 and Mac machines. I can see the Samba server (gargoyle) from the Win machines fine, but cannot browse any shares (Network unreachable error message). This seems a relatively common problem, but seems harder to resovle in my case :-) I have walked through the toubleshooting chapter and fail at a certain point. If I use "net view" from the Win machines I see the server, but "net view \\gargoyle" fails, but should have listed the available shares. Interestingly from the linux side I can browse outwards and see shares on the Win machines and the NT server fine. I can see the samba shares fine from the linux side but "nmblookup -B 192.168.1.253 gargoyle" command returns a "name query failed" result (.253 is the NT server). Presumably then gargoyle is not announcing itself correctly? BTW I have added the linux server to the NT's LMHOSTS file and to the Win machines LMHOSTS file and this helps with name resolution but not the share problem. I have added the users to the linux system and to the samba password file and just aboiut every other thing suggested in the troubleshooting chapter. OR, is it to do with firewall configuration rejecting the packets at the lowest level? Given I am a Linux newbie, can someone provide a walkthrough of where I go to broaden my firewall (if this really is the problem)? I am at a loss as to where to go (smb.conf is shown below). Unless I crack this and a netatalk installation I will be stuck with configuring a Mac server! Yuk! BTW the netatalk stuff doesn't work either, hence the firewall suspicion. cheers, Alex [global] smb passwd file = /etc/samba/smbpasswd remote announce = 192.168.1.253 dns proxy = no security = user encrypt passwords = yes workgroup = ICON server string = Samba Server %v socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 netbios name = GARGOYLE log file = /var/log/samba/log.%m load printers = yes wins support = no printcap name = /etc/printcap max log size = 50 guest account = pcguest [homes] comment = Home Directories browseable = no writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes [tmp] comment = Temporary file space path = /tmp read only = no public = yes [public] path = /iconshare public = yes only guest = yes writable = yes printable = no -- Alexander C. Le Dain, PhD Manager of Programming ICON Technologies Pty Ltd www.icon-tech.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Windows 2000 sp2 -> sp3
I have seen this recently myself. I have win98 and win2kpro boxes at a customer site so the scripts have 2 different entries. For win 98 net use h: /HOME this works fine but fails to fly on my 2k boxes. NT4 is happy with this too. for my 2k boxes net use h: \\chamber-gw\%USERNAME% works great but gags a big one on the 9X and NT4 boxes. Since I have several sites were the user might go to a 9x one time and a 2k another, I have both listed. One of them always fails depending on the OS but one always works. I am running 2.2.1a on some systems and am in the process of upgrading to 2.2.5 on the others. The 2k boxes are on SP3. -- Guy Story, KC5GOI Itel-Tigerbyte LLC [EMAIL PROTECTED] 940.891.4575 On Sunday 06 October 2002 07:42 pm, Dmitry N. Salmin wrote: > Really if I do "net use H: \\sambaserver\homes" after login, w2k > requests for a password and successfully connects the the homes share. > > -> What is necessary to make Windows 2000 not request a password if > -> username and password are the same on w2k and Samba? > > -> What has changed in sp3 so that it does not provide Samba with the > -> password I type in at login? > > > -Original Message- > From: Javid Abdul-AJAVID1 [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 07, 2002 12:30 AM > To: 'Dmitry N. Salmin '; '[EMAIL PROTECTED] ' > Subject: RE: [Samba] Windows 2000 sp2 -> sp3 > > > what error are you getting > -Original Message- > From: Dmitry N. Salmin > To: [EMAIL PROTECTED] > Sent: 10/6/02 1:40 AM > Subject: [Samba] Windows 2000 sp2 -> sp3 > > Hello All. > > I was using Windows 2000 sp2 and Samba 2.2.3a. Windows 2000 users were > also registered on my Samba server with the same passwords. Encryption > was set to Off. > > In the Windows 2000 user profiles it was set to automatically map H: to > \\sambaserver\homes. > > After installing sp3 it does not work anymore. > > Dmitry -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Second update: On the advice of someone else on this mailing list, I converted from BSD printing to CUPS (still using samba). Doing so has given me what is perhaps a more identifiable error message. When I send a job to the server, I check the que and get the following response: thedude@floyd:~> lpstat -t scheduler is running system default destination: lp device for lp: samba://192.168.1.101/lp lp accepting requests printer lp disabled - reason unknown lp-1thedude 164864 Sun Oct 6 19:07:36 2002 So it seems that the printer is disabled for some reason. The job just stays there in the que and never prints. - -Dan On Thursday 03 October 2002 15:23, Joel Hammer wrote: > Do you understand how printing works with samba? > Essentially, you just transfer the file to the samba spool directory, and > invoke lpr to print the file. You will need to look at your smb.conf file > to see what is supposed to happen. I would set up a share just for your > printer and not rely on the generic printer share that smb.conf comes with. > > Here is the sort of printer share I have: > This take a postscript file as input, invokes lpr to print to queue ps on > the server, which translates postscript files for my lexmark printer. > > Joel > > > > [ps] > path = /tmp > read only = No > create mask = 0700 > guest ok = yes > hosts allow = 192.168. > printable = Yes > printing = lprng > print command = echo %J %p %s >> /tmp/junkJ;\ >a="`echo '%J' | sed "s/^.*- //"`" ;\ > echo This is truncated $a >> /tmp/junkJ;\ >/usr/bin/lpr -Pps -J"$a" %s;\ >rm %s > lpq command = /usr/bin/lpq -Pps > lprm command = /usr/bin/lprm -Pps %j > lppause command = /usr/sbin/lpc hold z53 %j > lpresume command = /usr/sbin/lpc release z53 %j > share modes = No > use client driver = yes > > On Thu, Oct 03, 2002 at 12:47:27PM -0700, Dan Sawyer wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Hello, everyone - > > > > I've been trying for two weeks now to get my print server operational > > under Samba. After walking through the howtos and tweaking the configs > > per spec, it just ain't working. Printing from a client machine sends, > > and then nothing happens. No error messages or anything similar. > > > > Printing from the server works fine, but not from the clients. > > > > Setup: > > > > 4 machine network, 3 clients, 1 samba file/print server > > SuSE 7.3 running on all machines. > > HP 2P parallel printer on lp0 of server > > > > What else can I tell you to help figure this out? > > - -Dan Sawyer > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.0.6 (GNU/Linux) > > Comment: For info see http://www.gnupg.org > > > > iD8DBQE9nJ7TaB8ur/y6V8gRArm9AJ9rRc8yhDm5Catchqv4SXedOqs5qwCfSWS/ > > 2IayciR10uTYysD/3F24UdE= > > =TMQV > > -END PGP SIGNATURE- > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: http://lists.samba.org/mailman/listinfo/samba -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9oO3BaB8ur/y6V8gRAiAJAJwNmGtKOhWamaEBO2oX2bTlI0T7DACfXWEj WPZ2VS/XixCF6xBqgXbDQyc= =nwXl -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A followup to the last message: I have configured the Samba server to act as a WINS server, so YAST2 finds it now. Upon examining the log.smbd file, I find that there are no log entries generated when I try to print from the console or X on the client. However, the client generates no errors. - -Dan -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9oAURaB8ur/y6V8gRAmdmAJ9Dbum6vPIqOUoYSY02mzjEt7DWeQCfR728 fr8F5bJ/A8zrYuzCaPvwaSA= =6amJ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: force user
Jerry, Thanks for that - yes -once i removed the admin user and restarted samba it used the username in the force user field. many thanks - Original Message - From: "Gerald (Jerry) Carter" <[EMAIL PROTECTED]> To: "info" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 02, 2002 5:31 AM Subject: Re: force user > On Tue, 1 Oct 2002, info wrote: > > > Yes I had the Admin useres set as well as the valid users. I had > > entered a number of usernames in both. Should this make a difference? > > By definition, a user in the "admin users" list will operate as root. > > > I deleted the entries in admin users and then created a new file but the > > owner was still set to root.!?!? > > Did you restart Samba after the config change? Or at least get it to > reread its configuration file and reboot the client machine? > > > > > cheers, jerry > > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Windows 2000 sp2 -> sp3
Really if I do "net use H: \\sambaserver\homes" after login, w2k requests for a password and successfully connects the the homes share. -> What is necessary to make Windows 2000 not request a password if -> username and password are the same on w2k and Samba? -> What has changed in sp3 so that it does not provide Samba with the -> password I type in at login? -Original Message- From: Javid Abdul-AJAVID1 [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 12:30 AM To: 'Dmitry N. Salmin '; '[EMAIL PROTECTED] ' Subject: RE: [Samba] Windows 2000 sp2 -> sp3 what error are you getting -Original Message- From: Dmitry N. Salmin To: [EMAIL PROTECTED] Sent: 10/6/02 1:40 AM Subject: [Samba] Windows 2000 sp2 -> sp3 Hello All. I was using Windows 2000 sp2 and Samba 2.2.3a. Windows 2000 users were also registered on my Samba server with the same passwords. Encryption was set to Off. In the Windows 2000 user profiles it was set to automatically map H: to \\sambaserver\homes. After installing sp3 it does not work anymore. Dmitry -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] strange behavior maybe dependent on valid users
At 17:23 06-10-2002 +0200, you wrote: >Hi! > >My problem: > >I have a network with many workgroups and my samba server 3.0alpha21cvs is >the only member of one of that workgroups. >If I went to the network neighborhood and tried to open the workgroup of >my samba server I got an error message saying that the workgroup "mygroup" >was not available. >So I minimized the settings in the global section of my smb.conf and I was >able to open "mygroup". >I reactivated the most important options like "interfaces" and "hosts >allow", which didn't seem to be the problem. >But when I reactivated "valid users" containing 4 users, I was not able to >browse "mygroup" any more. First thing, have you checked that samba 3.0 is not the problem? Have you tried 2.2.5? Bruno Ferreira --- [This E-mail scanned for viruses by Declude Virus] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems using WinXP-Pro client and Samba PDC
At 07:00 06-10-2002 -0400, you wrote: >Hi All- > >Some time ago (24 September 2002), I wrote the list about this problem with >using a WinXP Pro client with a Samba PDC (see below for details). [snip] Well, I've read your LAN description and it mentions 4 things that are quite meaningful to me (as I had to fiddle with them too): 1 Samba server that used to be Windows 1 XP client 1 W2K client 1 Database app (a-ha! vital point!) I did read the rest of the problem and I have no idea if the "insufficient memory" message is truthful or not. The point is that I had to configure a LAN which had those 4 particularities, and a lot of trouble from the database-driven app (Access, FWIW) when it was acessed by 2 or more clients. To make a long story short, I solved a lot of trouble with the said app by configuring its' share like this: locking = yes oplocks = yes level 2 oplocks = yes share modes = no<--- dangerous, I know, but this particular piece was vital You also need to ensure all directory/file modes are group-writable. That app was crashing when closing after 2 or more clients had opened it, and threw out some other stupid errors. This may not be the cure to your particular problem, but it sure took me a few days to come up with a solution to mine, which is similar. Hope this helps in any way. Bruno Ferreira --- [This E-mail scanned for viruses by Declude Virus] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Server is getting slow
What do you see with top when the server is slow? What do you see with ps ax when the server is slow? Joel On Sun, Oct 06, 2002 at 10:56:49PM +0200, SW Kisters wrote: > Dear Sirs, > > I am working with a Suse Linux 6.3 server Samba and Windows 98 > workstations > (appx 8-10). After a few days (1 week) the server is getting real slow. > Server is 40 gb Harddisk, 256 MB Ram, everywhere 100 MB networkcards, > 100 MB intelligent Hub. > > When I reboot the network is at normal speed again. > > What can be the problem? Can you give me any suggestions please > Thank you in advance. > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Server is getting slow
Dear Sirs, I am working with a Suse Linux 6.3 server Samba and Windows 98 workstations (appx 8-10). After a few days (1 week) the server is getting real slow. Server is 40 gb Harddisk, 256 MB Ram, everywhere 100 MB networkcards, 100 MB intelligent Hub. When I reboot the network is at normal speed again. What can be the problem? Can you give me any suggestions please Thank you in advance. Kind regards SW Kisters [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: SWAT not working
Have you run smbpasswd? It allows you to add users as well as change passwords of current users. Joel On Sun, Oct 06, 2002 at 07:49:42PM +0200, Sander van Vliet wrote: > Well that's the major problem. I do have security concerns. > I've just installed webmin and meddling around with that. But I think I stick to VIM. > > Greetz and Thanks Maxor -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Autoreply to samba digest, Vol 1 #1695 - 6 msgs
Vielen Dank für Ihre e-mail. Da ich vom 30.09.-06.10 in Urlaub bin, kann ich sie leider erst danach bearbeiten bzw. beantworten. In dringenden Fällen, können Sie sich gerne an meinen Kollegen Herrn Lamotte wenden. Er hat die email-Adresse [EMAIL PROTECTED] und ist telefonisch unter 07142/596-152 zu erreichen. Mit freundlichen Grüßen Michael Müller G. Umbreit GmbH & Co.KG -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Show stopper - 2nd cry for help
Well, you seem desperate, so, I'll toss in my ideas. Just because the two versions of BSD are the same, you may have configured the kernels differently on the two machines. Computer hardware being so cheap, and linux is free (except for your time), why not set up a third machine. Configure it only as a file server, nothing else. Make sure it is a nice modern and stable distro with a well suited file system. If this works, why try using your multihomed gateway machine as a file server? Joel On Sun, Oct 06, 2002 at 10:20:55AM -0700, Sean Noonan wrote: > > > Folks, I have a really nasty problem preventing me from migrating a bunch of > NetWare 5 servers to Samba--attempts to copy large (> 2MB+) files to any > samba share results in an error. To clarify what I mean by "error": > > 1. I attempt to copy, using explorer, a 2MB+ file to any samba share. > 2. A 30 second or so pause occurs (copying this file to any other local > server, including a different samba server, completes in a couple of > seconds) > 3. A message box pops up on my screen. The title of the message box is > "Error Copying File or Folder". The contents of the message box is "Cannot > copy : The specified network name is no longer available". > 4. I click "OK" to acknowledge the message. > 5. Despite the error message, the file _appears_ to have actually copied > successfully, that is it appears in the target explorer window and has the > correct size. > 6. Error messages are generated in the samba logs, mostly regarding oplocks. > 7. Running smbstatus on the target server shows the file that was copied is > locked: > > Samba version 2.2.6pre2 > Service uid gid pid machine > -- > rootpart root wheel12099 sean (192.168.100.103) Sun Oct 6 > 09:40:51 2002 > rootpart root wheel 9981 sean (192.168.100.103) Sat Oct 5 > 21:50:27 2002 > > Locked files: > PidDenyMode Access R/WOplock Name > -- > 12099 DENY_NONE 0x20189 RDONLY EXCLUSIVE+BATCH > //tmp/Jennifer-Watkins97Data.mdb Sun Oct 6 09:40:51 2002 > > Here's some other observations/facts which may be useful in helping me: > > 1. All clients are Windows 2000 Professional + SP3 + all hot fixes. > 2. The Samba target server giving me error is running samba 2.2.6pre2 on > FreeBSD 4.6.2-RELEASE. > 3. I have another server running samba 2.2.6pre2 on FreeBSD 4.6.2-RELEASE, > too. It's acting as the PDC and WINS server. File copies to _it_ work just > great! The smb.conf files vary only slightly between the two machines. The > differences in config files are due to two reasons. The first is that the > second server is acting as a PDC and WINS server. The second is that the > first machine, the one that's giving me trouble, is a multi-homed gateway. > So, I'm specifying the "interfaces" parameter and forcing the NetBIOS name > to match it's internal, RFC1918, dns name. Those are the only differences. > 4. The server that's giving me trouble is named IMAIL. > 5. The server that works just fine, the PDC and WINS server, is named MOLD. > 6. The NT Domain on MOLD is called WATDOM. > 7. IMAIL is a member of WATDOM. > 8. The W2K workstation trying to perform the file copies is called SEAN. > 9. All machines are on one local subnet, using switched 100Mbps Ethernet. > Very fast, no network or PC hardware problems. > 10. In addition to using exploder to try and copy files, I've tried copying > using a DOS Prompt. Pretty much the same thing happens except for the GUI > popup. Instead of the GUI popup error message, xcopy or copy returns "File > creation error - The specified network name is no longer available". > 11. I played with disabling oplocks, level 2 oplocks, kernel oplocks, etc. > No love. > 12. I have "log level = 3" in my smb.conf file. This file copy procedure > seems to modify three log files: /var/log/messages, /var/log/log.smbd and > /var/log/log.sean. Below are relevant snippets of those logs: > > /var/log/messages > > Oct 5 21:50:59 mail smbd[9981]: [2002/10/05 21:50:59, 0] > smbd/oplock.c:request_oplock_break(1008) > Oct 5 21:50:59 mail smbd[9981]: request_oplock_break: no response > received to oplock break request to pid 9330 on port 3824 for dev = 27405, > inode = 36, file_id = 9 > Oct 5 21:50:59 mail smbd[9981]: [2002/10/05 21:50:59, 0] > smbd/open.c:open_mode_check(631) > Oct 5 21:50:59 mail smbd[9981]: open_mode_check: exlusive oplock left by > process 9330 after break ! For file tmp/Jennifer-Watkins97Data.mdb, dev = > 27405, inode = 36. Deleting it to continue... > Oct 5 21:50:59 mail smbd[9981]: [2002/10/05 21:50:59, 0] > smbd/open.c:open_mode_check(635) > Oct 5 21:50:59 mail smbd[9981]: open_mode_check: Existent process 9330 > left active oplock. > > /var/log/log.smbd > [2002/10/05 21:50:26, 3] smbd/oplock.c:init_oplocks(1211) > open_oplock_ipc
[Samba] Re: SWAT not working
Well that's the major problem. I do have security concerns. I've just installed webmin and meddling around with that. But I think I stick to VIM. Greetz and Thanks Maxor
RE: [Samba] Windows 2000 sp2 -> sp3
what error are you getting -Original Message- From: Dmitry N. Salmin To: [EMAIL PROTECTED] Sent: 10/6/02 1:40 AM Subject: [Samba] Windows 2000 sp2 -> sp3 Hello All. I was using Windows 2000 sp2 and Samba 2.2.3a. Windows 2000 users were also registered on my Samba server with the same passwords. Encryption was set to Off. In the Windows 2000 user profiles it was set to automatically map H: to \\sambaserver\homes. After installing sp3 it does not work anymore. Dmitry -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] (no subject)
"I don't believe in astrology. But then I'm an Aquarius, and Aquarians don't believe in astrology." -- James R. F. Quirk
[Samba] Show stopper - 2nd cry for help
Folks, I have a really nasty problem preventing me from migrating a bunch of NetWare 5 servers to Samba--attempts to copy large (> 2MB+) files to any samba share results in an error. To clarify what I mean by "error": 1. I attempt to copy, using explorer, a 2MB+ file to any samba share. 2. A 30 second or so pause occurs (copying this file to any other local server, including a different samba server, completes in a couple of seconds) 3. A message box pops up on my screen. The title of the message box is "Error Copying File or Folder". The contents of the message box is "Cannot copy : The specified network name is no longer available". 4. I click "OK" to acknowledge the message. 5. Despite the error message, the file _appears_ to have actually copied successfully, that is it appears in the target explorer window and has the correct size. 6. Error messages are generated in the samba logs, mostly regarding oplocks. 7. Running smbstatus on the target server shows the file that was copied is locked: Samba version 2.2.6pre2 Service uid gid pid machine -- rootpart root wheel12099 sean (192.168.100.103) Sun Oct 6 09:40:51 2002 rootpart root wheel 9981 sean (192.168.100.103) Sat Oct 5 21:50:27 2002 Locked files: PidDenyMode Access R/WOplock Name -- 12099 DENY_NONE 0x20189 RDONLY EXCLUSIVE+BATCH //tmp/Jennifer-Watkins97Data.mdb Sun Oct 6 09:40:51 2002 Here's some other observations/facts which may be useful in helping me: 1. All clients are Windows 2000 Professional + SP3 + all hot fixes. 2. The Samba target server giving me error is running samba 2.2.6pre2 on FreeBSD 4.6.2-RELEASE. 3. I have another server running samba 2.2.6pre2 on FreeBSD 4.6.2-RELEASE, too. It's acting as the PDC and WINS server. File copies to _it_ work just great! The smb.conf files vary only slightly between the two machines. The differences in config files are due to two reasons. The first is that the second server is acting as a PDC and WINS server. The second is that the first machine, the one that's giving me trouble, is a multi-homed gateway. So, I'm specifying the "interfaces" parameter and forcing the NetBIOS name to match it's internal, RFC1918, dns name. Those are the only differences. 4. The server that's giving me trouble is named IMAIL. 5. The server that works just fine, the PDC and WINS server, is named MOLD. 6. The NT Domain on MOLD is called WATDOM. 7. IMAIL is a member of WATDOM. 8. The W2K workstation trying to perform the file copies is called SEAN. 9. All machines are on one local subnet, using switched 100Mbps Ethernet. Very fast, no network or PC hardware problems. 10. In addition to using exploder to try and copy files, I've tried copying using a DOS Prompt. Pretty much the same thing happens except for the GUI popup. Instead of the GUI popup error message, xcopy or copy returns "File creation error - The specified network name is no longer available". 11. I played with disabling oplocks, level 2 oplocks, kernel oplocks, etc. No love. 12. I have "log level = 3" in my smb.conf file. This file copy procedure seems to modify three log files: /var/log/messages, /var/log/log.smbd and /var/log/log.sean. Below are relevant snippets of those logs: /var/log/messages Oct 5 21:50:59 mail smbd[9981]: [2002/10/05 21:50:59, 0] smbd/oplock.c:request_oplock_break(1008) Oct 5 21:50:59 mail smbd[9981]: request_oplock_break: no response received to oplock break request to pid 9330 on port 3824 for dev = 27405, inode = 36, file_id = 9 Oct 5 21:50:59 mail smbd[9981]: [2002/10/05 21:50:59, 0] smbd/open.c:open_mode_check(631) Oct 5 21:50:59 mail smbd[9981]: open_mode_check: exlusive oplock left by process 9330 after break ! For file tmp/Jennifer-Watkins97Data.mdb, dev = 27405, inode = 36. Deleting it to continue... Oct 5 21:50:59 mail smbd[9981]: [2002/10/05 21:50:59, 0] smbd/open.c:open_mode_check(635) Oct 5 21:50:59 mail smbd[9981]: open_mode_check: Existent process 9330 left active oplock. /var/log/log.smbd [2002/10/05 21:50:26, 3] smbd/oplock.c:init_oplocks(1211) open_oplock_ipc: opening loopback UDP socket. [2002/10/05 21:50:26, 3] lib/util_sock.c:open_socket_in(813) bind succeeded on port 0 [2002/10/05 21:50:26, 3] smbd/oplock.c:init_oplocks(1242) open_oplock ipc: pid = 9981, global_oplock_port = 4269 [2002/10/05 21:50:26, 3] lib/access.c:check_access(318) check_access: no hostnames in host allow/deny list. [2002/10/05 21:50:26, 2] lib/access.c:check_access(329) Allowed connection from (192.168.100.103) [2002/10/05 21:50:26, 3] smbd/process.c:process_smb(878) Transaction 0 of length 72 [2002/10/05 21:50:26, 2] smbd/reply.c:reply_special(92) netbios connect: name1=IMAILname2=SEAN [2002/10/05 21:50:26, 2] smbd/reply.c:reply_special(111) netbios connect: local=imail remot
[Samba] Autoreply to samba digest, Vol 1 #1694 - 3 msgs
Vielen Dank für Ihre e-mail. Da ich vom 30.09.-06.10 in Urlaub bin, kann ich sie leider erst danach bearbeiten bzw. beantworten. In dringenden Fällen, können Sie sich gerne an meinen Kollegen Herrn Lamotte wenden. Er hat die email-Adresse [EMAIL PROTECTED] und ist telefonisch unter 07142/596-152 zu erreichen. Mit freundlichen Grüßen Michael Müller G. Umbreit GmbH & Co.KG -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SWAT not working
I don't understand passwords in samba or swat. But, I get around the problem by starting swat with the -a option. This is what I have in my inetd.conf file: swatstream tcp nowait.400 root/usr/local/samba/bin/swat swat -a Expect cries of outrage over this suggestion, but it works fine on a home network without particular security concerns. Joel > > I've installed samba 2.2.5 a while ago and I didn't need swat at that time but now I >do. > I followed the manpage and modified my inetd.conf etc, the swat files are in place >but SWAT still gives me errors my password is wrong. I've checked my password etc and >still it doesn't work. > > Any idea's > > Greetz Maxor -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] strange behavior maybe dependent on valid users
Hi! My problem: I have a network with many workgroups and my samba server 3.0alpha21cvs is the only member of one of that workgroups. If I went to the network neighborhood and tried to open the workgroup of my samba server I got an error message saying that the workgroup "mygroup" was not available. So I minimized the settings in the global section of my smb.conf and I was able to open "mygroup". I reactivated the most important options like "interfaces" and "hosts allow", which didn't seem to be the problem. But when I reactivated "valid users" containing 4 users, I was not able to browse "mygroup" any more. So, is it possible, that the ability to open a workgroup with only one samba server depends on the value of "valid users"? Do you have any other ideas, how to solve that problem? Thanks Willi Mann -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Autoreply to samba digest, Vol 1 #1693 - 12 msgs
Vielen Dank für Ihre e-mail. Da ich vom 30.09.-06.10 in Urlaub bin, kann ich sie leider erst danach bearbeiten bzw. beantworten. In dringenden Fällen, können Sie sich gerne an meinen Kollegen Herrn Lamotte wenden. Er hat die email-Adresse [EMAIL PROTECTED] und ist telefonisch unter 07142/596-152 zu erreichen. Mit freundlichen Grüßen Michael Müller G. Umbreit GmbH & Co.KG -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] SWAT not working
Hi all I've installed samba 2.2.5 a while ago and I didn't need swat at that time but now I do. I followed the manpage and modified my inetd.conf etc, the swat files are in place but SWAT still gives me errors my password is wrong. I've checked my password etc and still it doesn't work. Any idea's Greetz Maxor
[Samba] Problems using WinXP-Pro client and Samba PDC
Hi All-
Some time ago (24 September 2002), I wrote the list about this problem with
using a WinXP Pro client with a Samba PDC (see below for details).
In response, Kenneth Illingsworth (if I understood him correctly) suggested
that the error message given by the Win XP client just might be accurate (ie.
that when the client complains of "Insufficient Memory" and then crashes
immediately, it might indeed be a problem with insufficient memory), and also
suggested that I should make sure disk write caching was enabled for the
client machine and that the amount of swap space was something like 2.5 times
the amount of physical RAM.
I tried Ken's suggestion, verified that disk write caching was indeed enabled,
increased the amount of swap space from the automatically configured amount
(384 MB of swap with 128 MB of RAM) to 512 MB of swap. Unfortunately, this
did nothing to solve the problem, and I am now exactly where I stood when I
originally posted the message below, so it seems my suspicion that the WinXP
error message had nothing to do with the real problem was probably correct.
I've tried fiddling with various settings in the smb.conf file that seem to
relate to file locking and stuff, but all to no avail.
Does anyone (please, please!) have any suggestions about what might be the
problem or what to try experimenting with to try and solve the problem?
If not, is anyone else running a network with a samba PDC, at least one Win XP
Pro client, at least one Win XP 2K client, and a database application run
simultaneously on both of these clients (and perhaps others) using common
files that are made available on the network using the disk share features of
the samba PDC? If so, perhaps someone could send me a copy of his/her
smb.conf file for simple comparison.
My smb.conf file looks like this:
[global]
workgroup = OLYMPUS
netbios name = ARES
server string = Samba %v on %h
encrypt passwords = Yes
map to guest = Bad User
smb passwd file = /etc/samba/smbpasswd
passwd program = /usr/bin/passwd %u
unix password sync = Yes
log level = 2
syslog = 0
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
character set = ISO8859-15
domain admin group = admin
add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u
logon path = \\%N\profile\%U
domain logons = Yes
os level = 64
preferred master = True
domain master = True
wins support = Yes
admin users = adam
hosts allow = 192.168.69., 127.
printing = lprng
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
[homes]
comment = Home Directories
read only = No
create mask = 0640
directory mask = 0750
browseable = No
[printers]
comment = All Printers
path = /var/tmp
create mask = 0600
printable = Yes
browseable = No
[netlogon]
comment = The domain logon service
path = /export/samba/logon
browseable = No
[profile]
comment = User profiles
path = /export/samba/profile
read only = No
create mask = 0600
directory mask = 0700
browseable = No
> [Samba] Wierdness using Samba PDC with WinXP-Pro and Win2K-Pro clients
> Tue, 24 Sep 2002 12:49:31 -0400
> Hi All-
>
> I have just finished making a change to the server machine in a 3-node
> network. Before, it was running Win2K Server, and now it's running SuSE
> Linux 8.0 and the default samba package installed with that distribution
> (samba-2.2.3a-64).
>
> The Win2K Server OS was acting as the PDC for the LAN, and the two client
> machines (one running Win2K Pro and the other running WinXP Pro) were
> connected to the domain offered by that Win2K server. Now, the same
> machine is running SuSE 8.0 and it is acting as the PDC for the LAN and the
> same two clients are now using the SuSE box as the PDC and they are now
> connected to the new domain created on the SuSE box. The server also
> serves up an SMB share to the client machines. The client machines map
> this network file share to the local F: drive for each client.
>
> This LAN is in a business office running a database application based upon
> FoxPro. The file share served up by the server contains the database
> application executables and data. The two client machines should both run
> copies of the database application simultaneously, and this worked without
> problems when the PDC and file share were being provided by Win2K server
> OS.
>
> But the wierdness is this: The arrangement still works fine with the SuSE
> box as the PDC and SMB file server, BUT... ONLY if I start the database
> application on the Win2K client machine FIRST, and then, once it is
> running, I subsequently start the database application on the WinXP client.
> If I start up the apps on the clients in that order,
Re: [Samba] Print server on all linux network
If it makes you feel any better, from day one with my linux experience I have never gotten printing to work on my own small home network using these automatic configuration tools. This explains why I know so much about printing. Have you ever posted to me your server printcap? On the server, can you print postscript files with just lpr? Is your printer really postscript? You can test this by printing from almost any linux app, like netscape, to a file. The file will be in postscript format. Then, can you print that file by cat'ing the file to the lp of your printer. Be prepared to turn the printer off if you get a lot of junk beginning with %!PS. Or, if this fails, what happens with lpr? About your printcap not showing any network connection, that may not be necessary. The printfilter (if) will incorporate the smbclient command I sent to you. Note that you do not need to use samba to print on your all linux network. You can set up printcaps on your clients to send their jobs to the server queue. For example, here is how I have one linux client set up. z53|rp1:\ :sd=/var/spool/lpd/rp1:\ :rm=hammer2.jhammer.org:\ :rp=ps:\ :sh:mx#0: The queue ps on my server accepts text files and postscript files for printing. It uses enscript to convert text into postscript prior to printing. Once you set up this printcap entry, (as the first one in the client printcap), run checkpc -f (I assume you are using lprng). Then, just lpr your file. It should work, if the queue on your server can handle text and postscript jobs. Joel On Sun, Oct 06, 2002 at 12:44:52AM -0700, Dan Sawyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Okay, Joel, after another bit of futzing around, here's what I've come up > with. > The files dumped using the command you told me to DO indeed write postscript > files to the directory in question. However every attempt to print those > files on the server fail. However, .txt files and others print properly from > the server. This leads me to believe that, somehow, the NEC Superscript > printer that's running on an HP2P ghostscript driver is somehow not a > postscript printer (though it quite apparently IS a postscript printer as far > as I can tell). Making that change (disabling postscript) has at least > gotten me to the point where I can make the printer lights blink (when > attempting to print from the client from any KDE/X program), though as yet > nothing is actually printing. Add to that one more layer of wierdness: When > printing text files from the client, the print job executes using the shell > command (cat filename.txt | smbclient //bob/nec -c 'print - '. However, when > printing a file from an X program to the server, all I get are the pretty > blinking lights. > > This leads me to the reasonable conclusion that the problems (after disabling > postscript) are client-based, involving a misconfiguration of some sort. So, > here's my client's /etc/printcap file. I notice with great dismay that > nothing in it actually directs me to anything on the network... > - -- > BEGIN CLIENT /etc/printcap: > # /etc/printcap: printer capability database. See printcap(5). > # You can use the filter entries df, tf, cf, gf etc. for > # your own filters. See the printcap(5) manual page for further > # details. > # > # Default Postscript printer on "print-serv" > #lp|ps|postscript:\ > #:client:lp=postscript@print-serv > #lp|ps|postscript:\ > #:server:oh=print-serv:\ > #:sd=/var/spool/lpd/ps:\ > #:lp=/dev/lp1:\ > #:sh:mx#0 > # > # Fax-Printer for SuSEFax > # > fax|faxprint:\ > :lp=/dev/null:\ > :sd=/var/spool/lpd/faxspool:\ > :lf=/var/spool/lpd/faxspool/err.log:\ > :if=/var/spool/lpd/faxspool/filter:\ > :mx#0:\ > :sh:\ > :sf: > ### BEGIN apsfilter: ### /etc/gs.upp/y2prn_nec.upp nec ### > # Warning: Configured for apsfilter, do not edit the labels! > #apsfilter setup Sat Oct 5 23:10:36 PDT 2002 > # > nec-ascii|lp1|y2prn_nec.upp--ascii-nec|y2prn_nec.upp ascii:\ > :lp=/dev/null:\ > :sd=/var/spool/lpd/y2prn_nec.upp--ascii-nec:\ > :lf=/var/spool/lpd/y2prn_nec.upp--ascii-nec/log:\ > :af=/var/spool/lpd/y2prn_nec.upp--ascii-nec/acct:\ > :if=/var/lib/apsfilter/bin/y2prn_nec.upp--ascii-nec:\ > :la@:mx#0:\ > :tr=:cl:sh: > # > nec|lp2|y2prn_nec.upp--auto-nec|y2prn_nec.upp auto:\ > :lp=/dev/null:\ > :sd=/var/spool/lpd/y2prn_nec.upp--auto-nec:\ > :lf=/var/spool/lpd/y2prn_nec.upp--auto-nec/log:\ > :af=/var/spool/lpd/y2prn_nec.upp--auto-nec/acct:\ > :if=/var/lib/apsfilter/bin/y2prn_nec.upp--auto-nec:\ > :la@:mx#0:\ > :tr=:cl:sh: > # > nec-raw|lp3|y2prn_nec.upp--raw-nec|y2prn_nec.upp raw:\ > :lp=/dev/null:\ > :sd=/var/spool/lpd/y2prn_nec.upp--raw-nec:\ > :lf=/var/spool/lpd/y2prn_nec.upp--raw-nec/log:\
Re: [Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay, Joel, after another bit of futzing around, here's what I've come up with. The files dumped using the command you told me to DO indeed write postscript files to the directory in question. However every attempt to print those files on the server fail. However, .txt files and others print properly from the server. This leads me to believe that, somehow, the NEC Superscript printer that's running on an HP2P ghostscript driver is somehow not a postscript printer (though it quite apparently IS a postscript printer as far as I can tell). Making that change (disabling postscript) has at least gotten me to the point where I can make the printer lights blink (when attempting to print from the client from any KDE/X program), though as yet nothing is actually printing. Add to that one more layer of wierdness: When printing text files from the client, the print job executes using the shell command (cat filename.txt | smbclient //bob/nec -c 'print - '. However, when printing a file from an X program to the server, all I get are the pretty blinking lights. This leads me to the reasonable conclusion that the problems (after disabling postscript) are client-based, involving a misconfiguration of some sort. So, here's my client's /etc/printcap file. I notice with great dismay that nothing in it actually directs me to anything on the network... - -- BEGIN CLIENT /etc/printcap: # /etc/printcap: printer capability database. See printcap(5). # You can use the filter entries df, tf, cf, gf etc. for # your own filters. See the printcap(5) manual page for further # details. # # Default Postscript printer on "print-serv" #lp|ps|postscript:\ #:client:lp=postscript@print-serv #lp|ps|postscript:\ #:server:oh=print-serv:\ #:sd=/var/spool/lpd/ps:\ #:lp=/dev/lp1:\ #:sh:mx#0 # # Fax-Printer for SuSEFax # fax|faxprint:\ :lp=/dev/null:\ :sd=/var/spool/lpd/faxspool:\ :lf=/var/spool/lpd/faxspool/err.log:\ :if=/var/spool/lpd/faxspool/filter:\ :mx#0:\ :sh:\ :sf: ### BEGIN apsfilter: ### /etc/gs.upp/y2prn_nec.upp nec ### # Warning: Configured for apsfilter, do not edit the labels! #apsfilter setup Sat Oct 5 23:10:36 PDT 2002 # nec-ascii|lp1|y2prn_nec.upp--ascii-nec|y2prn_nec.upp ascii:\ :lp=/dev/null:\ :sd=/var/spool/lpd/y2prn_nec.upp--ascii-nec:\ :lf=/var/spool/lpd/y2prn_nec.upp--ascii-nec/log:\ :af=/var/spool/lpd/y2prn_nec.upp--ascii-nec/acct:\ :if=/var/lib/apsfilter/bin/y2prn_nec.upp--ascii-nec:\ :la@:mx#0:\ :tr=:cl:sh: # nec|lp2|y2prn_nec.upp--auto-nec|y2prn_nec.upp auto:\ :lp=/dev/null:\ :sd=/var/spool/lpd/y2prn_nec.upp--auto-nec:\ :lf=/var/spool/lpd/y2prn_nec.upp--auto-nec/log:\ :af=/var/spool/lpd/y2prn_nec.upp--auto-nec/acct:\ :if=/var/lib/apsfilter/bin/y2prn_nec.upp--auto-nec:\ :la@:mx#0:\ :tr=:cl:sh: # nec-raw|lp3|y2prn_nec.upp--raw-nec|y2prn_nec.upp raw:\ :lp=/dev/null:\ :sd=/var/spool/lpd/y2prn_nec.upp--raw-nec:\ :lf=/var/spool/lpd/y2prn_nec.upp--raw-nec/log:\ :af=/var/spool/lpd/y2prn_nec.upp--raw-nec/acct:\ :if=/var/lib/apsfilter/bin/y2prn_nec.upp--raw-nec:\ :la@:mx#0:\ :tr=:cl:sh: # ### END apsfilter: ### /etc/gs.upp/y2prn_nec.upp nec ### - - Or, it could be a combination of server and client based. Allow me to explain. When plugging my laptop into a network with a windows based print server, I can set up the client's printer in YAST2 by telling YAST2 to browse the network and picking the appropriate name for the server and the que, and it prints without a hitch. However, on my all-linux network, when I try to browse with YAST2 it can't find any hosts. But (to make things even more fun), browsing with LinNeighborhood allows me to see the print que. Now, here's the smb.conf from the server: _ # Samba config file created using SWAT # from 192.168.1.100 (192.168.1.100) # Date: 2002/10/06 00:52:46 # Global parameters [global] workgroup = AWP netbios name = BOB server string = file and print server encrypt passwords = Yes update encrypted = Yes map to guest = Bad User null passwords = Yes large readwrite = Yes max smbd processes = 100 socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY character set = ISO8859-15 os level = 2 preferred master = True hosts allow = 192.168.1.100 192.168.1.101 192.168.1.102 192.168.1.103 hosts deny = ALL [homes] comment = Home Directories path = /home/burnboy read only = No create mask = 0640 directory mask = 0750 guest ok = Yes max connections = 4 write cache size = 262144
