Re: [Samba] Possible Bug?? (was: Win95 Win98 - NOT WORKING - NT,2000, XP are ok)
Thanks for the suggestion Andrew, I was hopeful, but removing the writeable made no difference. Still prints from NT, 2000, XP but not from Win95, 98. Any other ideas? -peter. Andrew Bartlett [EMAIL PROTECTED] on 19/03/2003 07:05:29 PM On Wed, 2003-03-19 at 18:02, [EMAIL PROTECTED] wrote: Please lend me some expertise... Sure! See below: RE: [Samba] Win95 Win98 - NOT WORKING - NT,2000, XP are ok (re Printing is working fine for our Windows NT, 2000 and XP clients. However, with windows 95 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. I think Samba is treating this like a file-share for non-NT (non-spoolss) printing. [global] printing = sysv lprm command = /usr/bin/cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume load printers = no [hp8100DN1] printer = hp8100dn_1 comment = HP LaserJet hp8100 DN path = /var/spool/lp/tmp/samba guest account = nobody guest ok = yes browseable = yes printable = yes writable = yes Well, I'll start by saying that this last statement will probably just confuse things - it might turn it back into a disk share. Andrew Bartlett Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Possible Bug?? (was: Win95 Win98 - NOT WORKING - NT,2000, XP are ok)
Thanks for the suggestion Raj. I might try using an old backup copy of the conf file. Don't know why this would work, but worth a shot anyway hey? :-) -peter. Raj Saxena [EMAIL PROTECTED] on 19/03/2003 07:20:09 PM Hi, I am not running it that way but one thing you can do is probably print directly to your printer server? Do you have a jetdirect card in your printer? It is a work around but this way you can have the 95/98 print jobs get by till this is resolved. I have noticed on two occasions where i have some really weird things happening all to find out i had a corrupted smb.conf file. Go figure that one but i used a back copy just to see if that would cure my problem and it worked. Hope this helps a bit. Raj -Original Message- From: [EMAIL PROTECTED] Please lend me some expertise... Ok, I know suggesting a bug is a bit impolite, but I cannot find a solution for this and none of the helpful people who have responded have been able to help either... If I come off sounding a bit short it's just because I've tried many things to get these older clients printing. :-) Don't mean to annoy anyone. Appreciate any help! Have several pressing reasons to upgrade to newest Samba (including latest security fix) but cannot do this if it means the Win9x clients can't print. The important point here is that everyone is printing fine on old Samba server. Have replicated permissions and conf file is pretty much the same for the new Samba server. It isn't a permissions thing because the Win9x clients are successfully sending the print job to the spool directory. Then the print job is getting stuck there. The job being stuck in the spool directory doesn't stop others from printing though. (Other NT, 2000, XP clients that is) Obviously most people are able to print from Win9x . Just wondering if maybe this is a Solaris + HP printers thing?? Thought maybe it was a printer driver issue, But it is printing okay from the old Samba so surely this is not the problem? Any ideas? Can anyone replicate my problem? Is anyone else using Solaris + HP + Samba 2.2.7a ? thanks sorry -peter. RE: [Samba] Win95 Win98 - NOT WORKING - NT,2000, XP are ok (re Printing is working fine for our Windows NT, 2000 and XP clients. However, with windows 95 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. Samba version is 2.2.7a, on Solaris 8 Printers are HP printers - e.g. HP 8100dn All clients including 95/98 were happily printing on a very much older version of Samba (2.0.6) network setup is a peer to peer network. printing directly from Unix to the printer is working ok (p.s. Just for a wild stab in the dark I tried setting the disable spoolss = yes but this stopped all printing from making it to the computer - even from the clients that were originally working.) relevant bits of conf. file included below... note that I don't have print command explicitly stated, but testparm indicates that it is configured properly... [global] printing = sysv lprm command = /usr/bin/cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume load printers = no [hp8100DN1] printer = hp8100dn_1 comment = HP LaserJet hp8100 DN path = /var/spool/lp/tmp/samba guest account = nobody guest ok = yes browseable = yes printable = yes writable = yes Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.462 / Virus Database: 261 - Release Date: 3/13/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.462 / Virus Database: 261 - Release Date: 3/13/2003 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Possible Bug?? (was: Win95 Win98 - NOT WORKING - NT,2000, XP are ok)
Please lend me some expertise... Ok, I know suggesting a bug is a bit impolite, but I cannot find a solution for this and none of the helpful people who have responded have been able to help either... If I come off sounding a bit short it's just because I've tried many things to get these older clients printing. :-) Don't mean to annoy anyone. Appreciate any help! Have several pressing reasons to upgrade to newest Samba (including latest security fix) but cannot do this if it means the Win9x clients can't print. The important point here is that everyone is printing fine on old Samba server. Have replicated permissions and conf file is pretty much the same for the new Samba server. It isn't a permissions thing because the Win9x clients are successfully sending the print job to the spool directory. Then the print job is getting stuck there. The job being stuck in the spool directory doesn't stop others from printing though. (Other NT, 2000, XP clients that is) Obviously most people are able to print from Win9x . Just wondering if maybe this is a Solaris + HP printers thing?? Thought maybe it was a printer driver issue, But it is printing okay from the old Samba so surely this is not the problem? Any ideas? Can anyone replicate my problem? Is anyone else using Solaris + HP + Samba 2.2.7a ? thanks sorry -peter. RE: [Samba] Win95 Win98 - NOT WORKING - NT,2000, XP are ok (re Printing is working fine for our Windows NT, 2000 and XP clients. However, with windows 95 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. Samba version is 2.2.7a, on Solaris 8 Printers are HP printers - e.g. HP 8100dn All clients including 95/98 were happily printing on a very much older version of Samba (2.0.6) network setup is a peer to peer network. printing directly from Unix to the printer is working ok (p.s. Just for a wild stab in the dark I tried setting the disable spoolss = yes but this stopped all printing from making it to the computer - even from the clients that were originally working.) relevant bits of conf. file included below... note that I don't have print command explicitly stated, but testparm indicates that it is configured properly... [global] printing = sysv lprm command = /usr/bin/cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume load printers = no [hp8100DN1] printer = hp8100dn_1 comment = HP LaserJet hp8100 DN path = /var/spool/lp/tmp/samba guest account = nobody guest ok = yes browseable = yes printable = yes writable = yes Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Win95 Win98 - NOT WORKING - NT,2000, XP are ok (re posted)
Our setup is peer to peer, rather than a domain setup. So security is set to server Generally though, we are using the same conf. file for this new Samba as the one we had (have) in production (on Samba 2.0.6). So I guess what I need to know is what has changed in regards to printing with Win95, 98 from 2.0.6 to 2.2.7a ? thanks -peter. Peter Carpenter [EMAIL PROTECTED] on 14/03/2003 09:45:28 PM Did you change your security setting in your new Samba e.g. from share to domain? -Original Message- From: [EMAIL PROTECTED] I tried adding the [printers] section to my conf file as John suggested, but this didn't solve the problem. Still able to print from NT, 2000, XP and not from Win95, 98 just recapping - am able to print from all clients with the old version (2.0.6) which we are still using in production With the new Samba (2.2.7a) the file sharing is fine, but printing only works for NT,2000,XP With Win95 Win98 only, the file gets put in the spool directory but doesn't seem to get sent from the spool directory to the printer. (or picked up by the printer - however it works...) Any idea if Win95, 98 printing is treated differently to the newer OS's ? thanks for any thoughts. see below for other details... -peter. Sorry to have to repost this (didn't get any response on the first post), we really need some of the fixes of the new Samba but cannot go ahead without the support for the older machines. Need to prove that Samba is the great product that I believe it is. Hi folks - I am having printing problems with our older machines. Printing is working fine for our Windows NT, 2000 and XP clients. However, with windows 95 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. Samba version is 2.2.7a, on Solaris 8 Printers are HP printers - e.g. HP 8100dn All clients including 95/98 were happily printing on a very much older version of Samba (2.0.6) printing directly from Unix to the printer is working ok Has anyone experienced this problem or have any advice on how to get my older boxes printing with the latest Samba? any thoughts welcome - no really - anything - please :-) -peter. (p.s. Just for a wild stab in the dark I tried setting the disable spoolss = yes but this stopped all printing from making it to the computer - even from the clients that were originally working.) relevant bits of conf. file included below... note that I don't have print command explicitly stated, but testparm indicates that it is configured properly... [global] printing = sysv lprm command = /usr/bin/cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume load printers = no [hp8100DN1] printer = hp8100dn_1 comment = HP LaserJet hp8100 DN path = /var/spool/lp/tmp/samba guest account = nobody guest ok = yes browseable = yes printable = yes writable = yes Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Win95 Win98 - NOT WORKING - NT,2000, XP are ok (reposted)
I tried adding the [printers] section to my conf file as John suggested, but this didn't solve the problem. Still able to print from NT, 2000, XP and not from Win95, 98 just recapping - am able to print from all clients with the old version (2.0.6) which we are still using in production With the new Samba (2.2.7a) the file sharing is fine, but printing only works for NT,2000,XP With Win95 Win98 only, the file gets put in the spool directory but doesn't seem to get sent from the spool directory to the printer. (or picked up by the printer - however it works...) Any idea if Win95, 98 printing is treated differently to the newer OS's ? thanks for any thoughts. see below for other details... -peter. John H Terpstra [EMAIL PROTECTED] on 13/03/2003 03:02:55 PM On Thu, 13 Mar 2003 [EMAIL PROTECTED] wrote: Suggest you add a [printers] entry in your smb.conf file. You should NOT need an entry for the printer itself. My samba-2.2.x prints fine from Win95/98/Me as well as NT4/2K/XP. - John T. Hey, thanks for your efforts anyway. I don't know what to make of this. Obviously a lot of things have changed between Samba 2.0.6 and 2.2.7a, but I can't figure out why Win95 98 suddenly can't print. I think you may be right - something to do with the new Samba using the MS-RPCs... which I imagine would mean a completely different printing method. Do you think this would require a different printer driver on the 95/98 boxes?? From what I read, I had the impression that it should all still work. I'd like to hear from anyone if they are successfully printing from Win95, Win98 clients on a Solaris server and using HP printers. I'm sure many people must be successfully printing from 95/98, but maybe this problem is specific to my particular environment ? I am contemplating your suggestion about the bug message. Maybe another day or so of frustration and I will try it. again - thanks muchly for your help. -peter. Date: Mon, 10 Mar 2003 18:33:35 +0100 From: maraqas [EMAIL PROTECTED] Hi Peter, i had a long, frunstrating web surfing yesterday night, searching for something that could apply to your case. I didn't find much at all, sorry. The only thing perhaps interesting to you could be this: http://us2.samba.org/samba/ftp/docs/htmldocs/printer_driver2.html This doc contains a section about migrating from 2.0.x to 2.2.x I think the problem lyes in the new way samba manages printing, that is by listening the MS-RPCs (Remote Procedure Call) coming from the winNT and win2000 clients. This is done thanks to spoolss, as i figured out reading here and there across the net. Well they say spoolss supports even win9x driver calls, even if those OSes do not actually make an RPC. They also say that backward compat. is reached through use client driver and spoolss disable. With these options enabled, the samba server should act just like it was a 2.0.x I think you'd need help from the samba guys themselves, so i advice reposting this problem with a more shocking subject line (suggest to use the keyword BUG :)) so you'll be able to capture their attention. Really sorry not to have been useful to you... cheers Maq Sorry to have to repost this (didn't get any response on the first post), we really need some of the fixes of the new Samba but cannot go ahead without the support for the older machines. Need to prove that Samba is the great product that I believe it is. Hi folks - I am having printing problems with our older machines. Printing is working fine for our Windows NT, 2000 and XP clients. However, with windows 95 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. Samba version is 2.2.7a, on Solaris 8 Printers are HP printers - e.g. HP 8100dn All clients including 95/98 were happily printing on a very much older version of Samba (2.0.6) printing directly from Unix to the printer is working ok Has anyone experienced this problem or have any advice on how to get my older boxes printing with the latest Samba? any thoughts welcome - no really - anything - please :-) -peter. (p.s. Just for a wild stab in the dark I tried setting the disable spoolss = yes but this stopped all printing from making it to the computer - even from the clients that were originally working.) relevant bits of conf. file included below... note that I don't have print command explicitly stated, but testparm indicates that it is configured properly... [global] printing = sysv lprm command = /usr/bin/cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume load printers = no [hp8100DN1] printer = hp8100dn_1 comment = HP LaserJet hp8100 DN path = /var/spool/lp/tmp/samba guest account = nobody guest ok = yes browseable = yes printable = yes writable =
[Samba] Win95 Win98 - NOT WORKING - NT,2000, XP are ok (reposted)
Hey, thanks for your efforts anyway. I don't know what to make of this. Obviously a lot of things have changed between Samba 2.0.6 and 2.2.7a, but I can't figure out why Win95 98 suddenly can't print. I think you may be right - something to do with the new Samba using the MS-RPCs... which I imagine would mean a completely different printing method. Do you think this would require a different printer driver on the 95/98 boxes?? From what I read, I had the impression that it should all still work. I'd like to hear from anyone if they are successfully printing from Win95, Win98 clients on a Solaris server and using HP printers. I'm sure many people must be successfully printing from 95/98, but maybe this problem is specific to my particular environment ? I am contemplating your suggestion about the bug message. Maybe another day or so of frustration and I will try it. again - thanks muchly for your help. -peter. Date: Mon, 10 Mar 2003 18:33:35 +0100 From: maraqas [EMAIL PROTECTED] Hi Peter, i had a long, frunstrating web surfing yesterday night, searching for something that could apply to your case. I didn't find much at all, sorry. The only thing perhaps interesting to you could be this: http://us2.samba.org/samba/ftp/docs/htmldocs/printer_driver2.html This doc contains a section about migrating from 2.0.x to 2.2.x I think the problem lyes in the new way samba manages printing, that is by listening the MS-RPCs (Remote Procedure Call) coming from the winNT and win2000 clients. This is done thanks to spoolss, as i figured out reading here and there across the net. Well they say spoolss supports even win9x driver calls, even if those OSes do not actually make an RPC. They also say that backward compat. is reached through use client driver and spoolss disable. With these options enabled, the samba server should act just like it was a 2.0.x I think you'd need help from the samba guys themselves, so i advice reposting this problem with a more shocking subject line (suggest to use the keyword BUG :)) so you'll be able to capture their attention. Really sorry not to have been useful to you... cheers Maq Sorry to have to repost this (didn't get any response on the first post), we really need some of the fixes of the new Samba but cannot go ahead without the support for the older machines. Need to prove that Samba is the great product that I believe it is. Hi folks - I am having printing problems with our older machines. Printing is working fine for our Windows NT, 2000 and XP clients. However, with windows 95 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. Samba version is 2.2.7a, on Solaris 8 Printers are HP printers - e.g. HP 8100dn All clients including 95/98 were happily printing on a very much older version of Samba (2.0.6) printing directly from Unix to the printer is working ok Has anyone experienced this problem or have any advice on how to get my older boxes printing with the latest Samba? any thoughts welcome - no really - anything - please :-) -peter. (p.s. Just for a wild stab in the dark I tried setting the disable spoolss = yes but this stopped all printing from making it to the computer - even from the clients that were originally working.) relevant bits of conf. file included below... note that I don't have print command explicitly stated, but testparm indicates that it is configured properly... [global] printing = sysv lprm command = /usr/bin/cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume load printers = no [hp8100DN1] printer = hp8100dn_1 comment = HP LaserJet hp8100 DN path = /var/spool/lp/tmp/samba guest account = nobody guest ok = yes browseable = yes printable = yes writable = yes Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Win95 Win98 - NOT WORKING - NT,2000, XP are ok (reposted)
Date: 07 Mar 2003 00:50:28 +0100 From: maq [EMAIL PROTECTED] To: SambaList [EMAIL PROTECTED] Subject: [Re: [Samba] printing - Win95 Win98 not working - NT,2000, XP are ok.] 1) Do you have a backup copy of your old smb.conf? 2) Try adding public=yes to the printer share definition Thanks for the suggestions but... 1 - yep I am basically using the same old conf file on which printing was working for Win95, 98 with a few necessary modifications. 2 -The printer share has guest ok which is the same as public=yes any other ideas? Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Win95 Win98 - NOT WORKING - NT,2000, XP are ok(reposted)
File Sharing is working fine. The problem seems to be getting the spooled file from the Samba spool directory to the printers, and only on Win95 and 98. The print command works ok when I run it from Unix... see the bottom of my post for relevant conf file bits. thanks -peter. Kurt Weiss [EMAIL PROTECTED] on 07/03/2003 06:54:35 PM did u test if it's a printing problem, or if there's the same problemwith file shares too??? can u post smb.conf Peter A Bryant 07/03/2003 08:31 AM To: [EMAIL PROTECTED] cc: Subject: Win95 Win98 - NOT WORKING - NT,2000, XP are ok (reposted) Sorry to have to repost this (didn't get any response on the first post), we really need some of the fixes of the new Samba but cannot go ahead without the support for the older machines. Need to prove that Samba is the great product that I believe it is. Hi folks - I am having printing problems with our older machines. Printing is working fine for our Windows NT, 2000 and XP clients. However, with windows 95 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. Samba version is 2.2.7a, on Solaris 8 Printers are HP printers - e.g. HP 8100dn All clients including 95/98 were happily printing on a very much older version of Samba (2.0.6) printing directly from Unix to the printer is working ok Has anyone experienced this problem or have any advice on how to get my older boxes printing with the latest Samba? any thoughts welcome - no really - anything - please :-) -peter. (p.s. Just for a wild stab in the dark I tried setting the disable spoolss = yes but this stopped all printing from making it to the computer - even from the clients that were originally working.) relevant bits of conf. file included below... note that I don't have print command explicitly stated, but testparm indicates that it is configured properly... [global] printing = sysv lprm command = /usr/bin/cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume load printers = no [hp8100DN1] printer = hp8100dn_1 comment = HP LaserJet hp8100 DN path = /var/spool/lp/tmp/samba guest account = nobody guest ok = yes browseable = yes printable = yes writable = yes Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Win95 Win98 - NOT WORKING - NT,2000, XP are ok (reposted)
Sorry to have to repost this (didn't get any response on the first post), we really need some of the fixes of the new Samba but cannot go ahead without the support for the older machines. Need to prove that Samba is the great product that I believe it is. Hi folks - I am having printing problems with our older machines. Printing is working fine for our Windows NT, 2000 and XP clients. However, with windows 95 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. Samba version is 2.2.7a, on Solaris 8 Printers are HP printers - e.g. HP 8100dn All clients including 95/98 were happily printing on a very much older version of Samba (2.0.6) printing directly from Unix to the printer is working ok Has anyone experienced this problem or have any advice on how to get my older boxes printing with the latest Samba? any thoughts welcome - no really - anything - please :-) -peter. (p.s. Just for a wild stab in the dark I tried setting the disable spoolss = yes but this stopped all printing from making it to the computer - even from the clients that were originally working.) relevant bits of conf. file included below... note that I don't have print command explicitly stated, but testparm indicates that it is configured properly... [global] printing = sysv lprm command = /usr/bin/cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume load printers = no [hp8100DN1] printer = hp8100dn_1 comment = HP LaserJet hp8100 DN path = /var/spool/lp/tmp/samba guest account = nobody guest ok = yes browseable = yes printable = yes writable = yes Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printing - Win95 Win98 not working - NT,2000, XP are ok.
Hi folks - I am having printing problems with our older machines. Printing is working okay for our Windows NT, 2000 and XP clients. However, with windows 95 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. Samba version is 2.2.7a, on Solaris 8 Printers are HP printers - e.g. HP 8100dn All clients including 95/98 were happily printing on a very much older version of Samba (2.0.6) printing directly from Unix to the printer is working ok Has anyone experienced this problem or have any advice on how to get my older boxes printing with the latest Samba? any thoughts welcome... -peter. (p.s. Just for a wild stab in the dark I tried setting the disable spoolss = yes but this stopped all printing from making it to the computer - even from the clients that were originally working.) relevant bits of conf. file included below... note that I don't have print command explicitly stated, but testparm indicates that it is configured properly... [global] printing = sysv lprm command = /usr/bin/cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume load printers = no [hp8100DN1] printer = hp8100dn_1 comment = HP LaserJet hp8100 DN path = /var/spool/lp/tmp/samba guest account = nobody guest ok = yes browseable = yes printable = yes writable = yes Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Infrasoft MX very slow loading from Samba share
The clients are XP and 2000 boxes. I have looked at the logs and noticed that MX opens a HECK of a LOT of files when it opens a single drawing. In one section of the log I estimate it opens about 3300 files in 105 seconds. Probably small files - I think macros etc. I will try and explore a bit further before posting any more. I was just hoping some other Samba person out there was using MX and could give their experience. Thanks for your interest Jerry. -peter. Gerald (Jerry) Carter [EMAIL PROTECTED] on 25/02/2003 01:33:58 PM On Tue, 18 Feb 2003 [EMAIL PROTECTED] wrote: Just wondering if anyone is aware of any conflicts between MX and Samba. Or if anyone is successfully storing MX files on their Samba server. Sounds like oplock break timeouts. What is the client os? I've never heard any feedback from Infrasoft MX users, so I can't comment on it. cheers, jerry Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Infrasoft MX very slow loading from Samba share
We are experiencing long delays when loading MX files stored on our samba fileserver. We are running version 2.2.7a of Samba on Solaris 8 servers. Using MX version 2.5 and higher on windows 2000 and XP workstations When the files are stored locally they load in a few seconds, whilst taking more than a minute to run from the Samba server. Our current workaround is to store the files locally, but this is not ideal. Other application files(e.g. Word, etc) of similar size load from the server in seconds. Problem seems to be confined to MX files. Just wondering if anyone is aware of any conflicts between MX and Samba. Or if anyone is successfully storing MX files on their Samba server. thanks for any information -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] re: samba configuration
hello, i colombian help me to samba manual in spanish configuration network windows nt my version the linux is red hat 8.0 thanks aquí está un sitio portugués. Esto estará quizá de una cierta ayuda. buena suerte http://groups.yahoo.com/group/samba-br/ Here is a Portuguese language site. Maybe this will be of some help. good luck -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] re: samba configuration
Aquí está otro sitio. Lo pienso soy un pedacito viejo. No puedo leer realmente a españoles. http://lucas.hispalinux.es/COMO-INSFLUG/COMOs/Samba-Como/Samba-Como.html Here's another site. I think it's a bit old. I can't actually read spanish. :-) peter. Peter A Bryant 13/12/2002 09:08 AM To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: re: samba configuration hello, i colombian help me to samba manual in spanish configuration network windows nt my version the linux is red hat 8.0 thanks aquí está un sitio portugués. Esto estará quizá de una cierta ayuda. buena suerte http://groups.yahoo.com/group/samba-br/ Here is a Portuguese language site. Maybe this will be of some help. good luck -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Searchable archieves
A searchable archive of the Samba mailing list is available at http://marc.theaimsgroup.com/ I sometimes find the search a bit dodgy though. From: Isamp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, 11 Dec 2002 10:36:49 -0200 Message-Id: [EMAIL PROTECTED] Subject: [Samba] Searchable archieves Please, where can I found the searchable archieves of this list ? Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] RE: Samba newbie question... (SWAT)
Thanks for the performance information John, I wasn't aware that optimising the conf could make such a difference. I guess my way of thinking - where I want to look at the original smb.conf file and have it nicely readable is a bit impractical, and maybe I will soon change that way of thinking, but I think it will help your work if you are aware of other peoples thought processes, (even if they seem incorrect). Just to clarify for a newbie, The main functionality of SWAT is to optimise the smb.conf file ? Should a separate tool be used if I want to simplify management (viewing, organising, understanding) of the smb.conf, or does SWAT perform that task as well as any of the other Samba gui's as well as performing optimisation? On a more basic level, could I ask you two questions about SWAT? I could discover the answer by setting up SWAT, but I would like to know the answer before trying. :-) 1. Does SWAT show what all the parameters are set to ? ( I don't find testparm output the nicest to read) 2. Does SWAT allow for included files in smb.conf ? finally, sorry I sure don't have the expertise to create code for swat. If I sound critical of your work or anything here, I really don't mean to, just looking for information. Once again, thanks for your good work. -peter. On Tue, 26 Nov 2002 [EMAIL PROTECTED] wrote: Hi John, I don't actually use swat, so am not highly qualified to offer suggestions. Anyway, here's my two cents. :-) I would like to use a nice gui such as SWAT to manage my conf file, but don't because I have heard that it changes the structure - ordering of parameters etc. within the conf file, as well as removing comments. From some of your comments, I get the impression that you feel this is a minor matter, but it is the reason that I don't use swat, and I have read comments from several other people suggesting the same thing - don't use swat if you have a carefully organised conf file. In your opinion, is swat mainly a tool for optimising the conf file? What I would like it to be is a tool for organising/managing conf parameters, for easily viewing what value each parameter is set to (even if it's default value), viewing which ones are specifically set in the conf file and which are just default, and for viewing individual shares and what parameters are set for each share. My first exposure to real problems with excessively sized smb.conf files was in a site that had 800 MS Windows clients. They had a full smb.conf config history in the file. It was 156Kb in size. At that time, samba read smb.conf (as it does now) every 20 seconds, except now we only read the actual file if the last change is more recent than when smbd started. Anyway, at this site the system load with all clients idle was 30! Work it out: 800 x 156Kb x 3/60 = 6.2MB/sec of file system I/O without doing a thing. By optimizing the smb.conf file this dropped the load to nothing. The resulting file was just under 10Kb in size. So you see, this radically taught me that config files are no place for documentation. That should be done in a separate file. SWAT optimizes the smb.conf file for minimum size, only writing out parameters that are not at default. I would like to be able to set and change parameters, and when I'm done, for SWAT to write changes back into the existing file without changing the way that I've got my conf nicely set out. (including comments and several include files). So, have you checked 'testparm'? It will tell you all config parameter settings. Is this possible? Is it likely to happen? Do I ask too much? :-) I think perhaps other people would like it not to mess with their pretty organised smb.conf also. Well, if someone will send me patches that do this as an option, I'll gladly review and commit if the code is clean and not in conflict with samba coding standards. Well, I told you I haven't used SWAT, so feel free to ignore my input. I am looking for a convincing argument why SWAT is bad! I am also looking for informed input on how we can improve the utility of SWAT. - John T. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] RE: Samba newbie question... (SWAT)
So John, are you the SWAT guru for Samba? I like the idea of having an expert for each area of Samba. Just a thought - if you are looking for further feedback regarding SWAT, you may want to post a message to the Samba forum on tek-tips website. (goto www.tek-tips.comand search for forum called Andrew Tridgell : Samba) There are currently over 800 members of the forum, so there should be at least a few SWAT users, and obviously these people like a gui interface if they are using the web forum. -pete. On Wed, 27 Nov 2002 [EMAIL PROTECTED] wrote: Thanks for the performance information John, I wasn't aware that optimising the conf could make such a difference. I guess my way of thinking - where I want to look at the original smb.conf file and have it nicely readable is a bit impractical, and maybe I will soon change that way of thinking, but I think it will help your work if you are aware of other peoples thought processes, (even if they seem incorrect). Spot on! I also object to things that I have tidied my way being changed without my consent. You are no rebel, never intended to convey that impression either. But performance can make or break a Windows NT/2K/XP take-out deal. Just to clarify for a newbie, The main functionality of SWAT is to optimise the smb.conf file? No, SWAT allows you to configure and tune Samba, every option has context sensitive help too. Then it has a tool to manage network wide passwords, and to check on what files are open, etc. It is just that when you use SWAT to write the smb.conf file it will write only those parameters that are at non-default values, and it will write them in it's internal order. Should a separate tool be used if I want to simplify management (viewing, organising, understanding) of the smb.conf, or does SWAT perform that task as well as any of the other Samba gui's as well as performing optimisation? My opinion or yours? Best thing is to try it. Form your own judgement and give me your feedback. On a more basic level, could I ask you two questions about SWAT? You did anyhow. ;) I could discover the answer by setting up SWAT, but I would like to know the answer before trying. :-) Lazy? 1. Does SWAT show what all the parameters are set to ? ( I don't find testparm output the nicest to read) Yep. It has a Basic mode and an Advanced mode. In Samba-3.0.0 it will have a Basic mode, an Advanced mode and a Developer mode. 2. Does SWAT allow for included files in smb.conf ? finally, sorry I sure don't have the expertise to create code for swat. If I sound critical of your work or anything here, I really don't mean to, just looking for information. Criticism is fair game. Go for it. That's how we improve things. Once again, thanks for your good work. No problems. Enjoy. - John T. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] RE: Samba newbie question...
The Samba-Team wrote SWAT to opimise the smb.conf file for a reason. I believe that a configuration file is a poor place for system documentation, particularly if it can affect performance. This does not affect small sites but those with hundreds of MS Windows PC clients will notice a significant problem with unnecessarily large smb.conf files. So having said that, I am looking for input from people who have an opinion they wish to share. What is your wish list for SWAT? What new or improved functionality should SWAT offer to make Samba more usable? Lastly, I am looking for volunteers to help extend/change/improve SWAT. This week is SWAT week for me. Between Wednesday and Friday I hope to overhaul SWAT in the Samba-3.0.0 branch, I would ask for early responses. Please email comments back to this list, and offers to help with specifying and coding to me privately at [EMAIL PROTECTED] I will summarize comments back to this list later this week. Hi John, I don't actually use swat, so am not highly qualified to offer suggestions. Anyway, here's my two cents. :-) I would like to use a nice gui such as SWAT to manage my conf file, but don't because I have heard that it changes the structure - ordering of parameters etc. within the conf file, as well as removing comments. From some of your comments, I get the impression that you feel this is a minor matter, but it is the reason that I don't use swat, and I have read comments from several other people suggesting the same thing - don't use swat if you have a carefully organised conf file. In your opinion, is swat mainly a tool for optimising the conf file? What I would like it to be is a tool for organising/managing conf parameters, for easily viewing what value each parameter is set to (even if it's default value), viewing which ones are specifically set in the conf file and which are just default, and for viewing individual shares and what parameters are set for each share. I would like to be able to set and change parameters, and when I'm done, for SWAT to write changes back into the existing file without changing the way that I've got my conf nicely set out. (including comments and several include files). Is this possible? Is it likely to happen? Do I ask too much? :-) I think perhaps other people would like it not to mess with their pretty organised smb.conf also. Well, I told you I haven't used SWAT, so feel free to ignore my input. Thanks for all your work. -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] re: Am I using the wrong list???
A day or two ago I posted information about error messages I was getting in my logs after installing 2.2.6. No one has replied! Am I using the wrong list? If you don't mind looking back, please take a look at my message and provide some input! Thanks, Tait Shrum Bryant Public Schools Hi Tait. You are using the right list, you were just unlucky. Not everyone gets an answer to their questions. I suggest you repost your question, as people aren't that likely to go to the trouble of looking up your old posting. I'd also suggest that you make the subject a little bit more specific concerning your problem. People tend to skim the subjects of the mailing list and see if there is anything that they know about or are interested in. If you mention the area you are having trouble with and the problem you're having, you may catch the eye of someone who knows about that stuff. Also you may want to try posting to the Samba forum on Tek-tips web site. Go to www.tek-tips.com and search for a forum called Andrew Tridgell:Samba good luck with future posts. sorry I can't help you with your specific problem -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Solaris version 8
Hello, Can Samba be run on Solaris version 8? Michael L. Hall PTC Building Coordinator Yep, we have had samba running on solaris for years including solaris 8 more recently. -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Kudos to Samba team - again
I am sure 99% of Samba users feel as I do - very grateful to the Samba team for their efforts and their product. Touch wood - I've seen very few problems with 2.2.6 on the mailing list thus far. I just downloaded the source, configure, make, make install and to quote Microsoft - It just worked.No slander intended ! :-) It looks good. Thanks team. -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: something wrong with the list (or its members)
That sounds about right. There are only a few people with the time to play 'wack a mole' with the contuing stream of questions. I think one of the problems is that we don't have a decent FAQ system - so there are a *lot* of duplicate questions on the list. (That said, I'm not sure how many people would read an FAQ in any case...) Andrew Bartlett Just my small opinion, but I think that something already exists that would go some way towards fixing the problem of unanswered queries, (and perhaps even repeated questions) I am talking about the Samba forum on TekTips. Goto www.tek-tips.com and search for a forum called Andrew Tridgell: Samba This is a very nice forum. Best things are 1. It makes it simple to follow a thread (which is kinda difficult thru mailing list) You can even mark threads you are interested in and they display first and you can be notified by email when there is a reply to the thread 2. Makes it easy to see if someone has replied to a question or not (number of replies is displayed on list of threads) I look out for messages that have zero replies and try to help if I can. Also may stop repeat questions because it has a nice search feature as well as a good FAQ page that people can add to and which is easy to access. I think the more people use this forum, the less basic questions will appear on the mailing list. Check it out. There are already 660 members of the list and it's only been around since about the start of the year. I'm not doing an ad here - it's a free forum. Think if everyone used this it would be good for Samba Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Windows 95/98 will not connect to Samba 2.2.5 please help
Hi, we have several Solaris 8 file print servers running Samba 2.0.6 I know this is quite an old version, so we upgraded one of them to 2.2.5 recently. Now, all the Win 98 95 clients cannot connect to the upgraded server (incorrect password for Server/IPC$) However Win NT, 2000 seem to connect to the new server just fine. The 95/98 clients can still connect ok to the other samba servers that we have not upgraded. The conf file on the new Samba is basically identical to the old conf file. Has anyone got a solution to this problem? Any advice welcome. Thanks -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] SOLVED: (maybe) Re:Windows 95/98 will not connect to Samba 2.2.5
Ok, I think I fixed the problem, but I'm still a bit puzzled. You see, a lot of our users are mapped to the user 'nobody' When I checked the log file, I noticed that it was having a problem because 'nobody' has a null password. So, putting the parameter 'null passwords = yes' into the conf file fixed the problem. What I don't understand is that it connected fine with Samba 2.0.6 servers and the parameter was not set in their conf files either. Can anyone explain this? Did this parameter not work at one time? As far as I know, the default has always been 'null passwords = no'. It's not that important to know, I'm just curious. Also just if anyone would like to comment, is it a problem to be mapping people to a No Password account? thanks everyone for your help. -peter. Yes, unless someone has changed the registry to use unencrypted passwords, I THINK. You can check this out. run tcpcump and watch the interaction during the login phase. Maybe the samba logs will show it too, but I would hope the log wouldn't show a password. Joel On Thu, Sep 26, 2002 at 08:04:51AM +1000, [EMAIL PROTECTED] wrote: Joel, from what I read, the encrypt problem does not affect Windows 98. Is that your understanding also? thanks -peter. Is the an encrypt password problem? Joel On Wed, Sep 25, 2002 at 05:02:36PM +1000, [EMAIL PROTECTED] wrote: Hi, we have several Solaris 8 file print servers running Samba 2.0.6 I know this is quite an old version, so we upgraded one of them to 2.2.5 recently. Now, all the Win 98 95 clients cannot connect to the upgraded server (incorrect password for Server/IPC$) However Win NT, 2000 seem to connect to the new server just fine. The 95/98 clients can still connect ok to the other samba servers that we have not upgraded. The conf file on the new Samba is basically identical to the old conf file. Has anyone got a solution to this problem? Any advice welcome. Thanks -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Is Samba 2.2.4 stable error free
Hi, I am planning on upgrading our Samba servers to a more current version (presently we have 2.0.6) Just wondering if 2.2.4 is the best version to implement, or if an earlier version would be more stable, e.g. 2.2.3a I ask this question because I've seen a few messages on the mailing lists suggesting errors in 2.2.4, but don't know if these are real errors or just people with a bad setup or something. Does anyone have information / opinions on this. Which version should I go for? Thanks for your advice -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] AutoCAD file names UPPER CASE on samba
Roberto - thanks for your help - I think I've found a solution. Our servers are currently running Samba 2.0.6 (I think I said 2.0.8 before mistakenly) We have a test server running Samba 2.2.2 with pretty much the same conf file as the others. So I tried saving an AutoCAD file to this machine, and it seems to preserve the case just fine. So in summary, the solution to this problem seems to be to upgrade to at least Samba 2.2.2 . I couldn't find this fix mentioned in any release notes, so I'm not sure at what version this was fixed. -pete. (Martyn thanks also for your assistance) Pete Just more 2 things to try, 1 - upgrade your samba, I´m using 2.2.3a in Linux, and also in Solaris 2.4.1 2 - try to add the follow in your smb.conf client code page = 850 character set = iso8859-1 or what is correct to you. Roberto At 22:50 27/05/2002, [EMAIL PROTECTED] wrote: Roberto, thanks for the suggestion, however, no success. I explicitly set all the parameters, but still the filenames are being automatically set to upper case (on the Samba server only). thanks anyway -pete. Hi I sugest to explicit setup all parameters you need. In my case: mangle case = no case sensitive = no default case = lower preserve case = yes short preserve case = no I have no problems with AutoCAD file names with those settings. Hope this help ROberto At 00:36 24/05/2002, you wrote: p.s. forgot to mention parameter settings for the share we are having problems with preserve case = yes default case - not set - default = lower mangle case- not set - default = no -- Forwarded by Peter A Bryant/EngServ/QMR/Au on 24/05/2002 01:32 PM --- Peter A Bryant 24/05/2002 01:31 PM To: [EMAIL PROTECTED] cc: Subject: AutoCAD file names UPPER CASE on samba Hi folks, we are experiencing a problem when AutoCAD 2000+ drawing files are saved on a Samba (2.0.8) file share. Regardless of what the file is 'saved as', the name is always converted to all capitals. e.g. Drawing1 becomes DRAWING1 Just wondering if anyone else has experienced this problem. Seems strange that it is only AutoCAD files, but I think it is Samba related, not AutoCAD, since the files save ok on local drives. We are using a mixture of NT and 2000 clients. Samba 2.0.8 is running on Solaris 8 servers. Any help appreciated. thanks -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] AutoCAD file names UPPER CASE on samba
Roberto, thanks for the suggestion, however, no success. I explicitly set all the parameters, but still the filenames are being automatically set to upper case (on the Samba server only). thanks anyway -pete. Hi I sugest to explicit setup all parameters you need. In my case: mangle case = no case sensitive = no default case = lower preserve case = yes short preserve case = no I have no problems with AutoCAD file names with those settings. Hope this help ROberto At 00:36 24/05/2002, you wrote: p.s. forgot to mention parameter settings for the share we are having problems with preserve case = yes default case - not set - default = lower mangle case- not set - default = no -- Forwarded by Peter A Bryant/EngServ/QMR/Au on 24/05/2002 01:32 PM --- Peter A Bryant 24/05/2002 01:31 PM To: [EMAIL PROTECTED] cc: Subject: AutoCAD file names UPPER CASE on samba Hi folks, we are experiencing a problem when AutoCAD 2000+ drawing files are saved on a Samba (2.0.8) file share. Regardless of what the file is 'saved as', the name is always converted to all capitals. e.g. Drawing1 becomes DRAWING1 Just wondering if anyone else has experienced this problem. Seems strange that it is only AutoCAD files, but I think it is Samba related, not AutoCAD, since the files save ok on local drives. We are using a mixture of NT and 2000 clients. Samba 2.0.8 is running on Solaris 8 servers. Any help appreciated. thanks -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] AutoCAD file names UPPER CASE on samba
Hi folks, we are experiencing a problem when AutoCAD 2000+ drawing files are saved on a Samba (2.0.8) file share. Regardless of what the file is 'saved as', the name is always converted to all capitals. e.g. Drawing1 becomes DRAWING1 Just wondering if anyone else has experienced this problem. Seems strange that it is only AutoCAD files, but I think it is Samba related, not AutoCAD, since the files save ok on local drives. We are using a mixture of NT and 2000 clients. Samba 2.0.8 is running on Solaris 8 servers. Any help appreciated. thanks -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] p.s. AutoCAD file names UPPER CASE on samba
p.s. forgot to mention parameter settings for the share we are having problems with preserve case = yes default case - not set - default = lower mangle case- not set - default = no -- Forwarded by Peter A Bryant/EngServ/QMR/Au on 24/05/2002 01:32 PM --- Peter A Bryant 24/05/2002 01:31 PM To: [EMAIL PROTECTED] cc: Subject: AutoCAD file names UPPER CASE on samba Hi folks, we are experiencing a problem when AutoCAD 2000+ drawing files are saved on a Samba (2.0.8) file share. Regardless of what the file is 'saved as', the name is always converted to all capitals. e.g. Drawing1 becomes DRAWING1 Just wondering if anyone else has experienced this problem. Seems strange that it is only AutoCAD files, but I think it is Samba related, not AutoCAD, since the files save ok on local drives. We are using a mixture of NT and 2000 clients. Samba 2.0.8 is running on Solaris 8 servers. Any help appreciated. thanks -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or National Transport Secretariat, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
