[Samba] Re: Printing only works sometimes
Tks Guys, I shall do some digging. I already have the chaps at SCO scratching themselves bald. So hopefully I shall get things going some day Meanwhile I shall try out all your suggestions and see what happens. Rgds Joe Carri -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Printing only works sometimes
Jeremy Allison samba.org> writes: > The problem seems to be with the lp subsystem on the SCO > OpenServer box. Probably the reason you're not getting much > help is due to the fact you're running on an *extremely* > (to say the least unpopular platform. > > I have a feeling people may be much more willing to help > if you were running on any other system than SCO. > > SCO have not gone out of their way to make themselves > popular with the Free Software/Open Source communities > due to their legal activities. > > Would it be possible to migrate your applications onto > a Linux varient instead ? They are known to be much > better integrated with Samba into a Windows printing > network (it works out of the box on my Red Hat Fedora > test machines). > > Cheers, > > Jeremy. Hi, Thanks for the suggestion Jeremy, I do understand that SCO is no longer popular, specially now that there's a very satisfactory alternative in the various forms of Linux. However, I'm afraid that that's impossible. You see the two UNIX machines are what the entire firms MIS system runs on. The MIS system has been implemented and has grown and accreted over the years (since 1994) and is now a real behemoth. To port it to another OS will be a major job. In fact the reason I need to get the printing operational is for printing MIS reports and other documents at the outlying locations. Could you give me an idea of what lp could do wrong to cause samba to time out. I'm pretty sure I could fool around with lp and get it to behave. the SCO lp is a very stable and reliable animal, and I've never had problems with it over the years, but there's always a first time ... Rgds, Joe Carri -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing only works sometimes
I posted the message below, on the gmane.network.samba.general newsgroup some days ago, and haven't got any replies yet. If anyone has any suggestions as to what can be done, please let me know. I have been trying to use Samba 2.2.6 to print from two SCO Openserver 5.0.7 servers (VDOHOM & VDOHOM2, IP addresses 192.168.1.121 & 192.168.1.122) on a WAN consisting of networks 192.168.1.0, 192.168.11.0 & 192.168.21.0, interconnected by ISDN leased lines using CISCO 805 routers. The WAN has been up and running for months and there are no communications problems. Users have been runing various Oracle applications on Win2K servers, connecting to the internet through another Win2k server and a firewall, and connecting to the Unix servers with Telnet. I installed and configured Samba to print to printers attached to the WIN 2003 Servers JUMBOSRV1 & MSTSVR on 192.168.11.200 & 192.168.21.200 respectively, using smbprint.sysv. All Samba parameters are at default value. The WIN 2000 Server (W2k-SVR, 192.168.1.1) is the PDC & WINS Server for the entire domain, consisting of all three LANS. Printing from any Windows workstation to any of teh printers functions correctly. I have created a user called samba on the two Openserver machines as well as on the Windows Domain. The user was added with with useradd & smbpasswd. I do not have any problem accessing or browsing test shares on the UNIX machines. I am currently trying to set up the printing from the UNIX servers to the WIN 2003 Server jumbosvr1. I intend to set up a similar print facility on mstsvr after this. My problem is this. Some of the time, I can print from either Unix server without any problems at all. However, about half the time, lpstat claims the document has been printed, but nothing in fact is printed. The Win 2003 servers do not show any queued documents. When a document prints correctly the arguments (passed by lp -d jumbo -ob filename) to smbrpint.sysv (redirected to a log file) are: Arguments = jumbo-3 root 1 b /SPARE/APPLICATION/LOCATIONS/invt/mkt/x And the smbclient message (I have redirected output to a log file) is: added interface ip=192.168.1.122 bcast=192.168.1.255 nmask=255.255.255.0 Domain=[DOMAIN] OS=[Windows Server 2003 3790] Server=[Windows Server 2003 5.2] smb: \> CR/LF<->LF and print text translation now on smb: \> putting file - as stdin-27268 (14.1 kb/s) (average 14.1 kb/s) When a document fails to print, smbclient produces the arguments passed to smbprint.sysv are: Arguments = jumbo-38110 root 1 b /SPARE/APPLICATION/LOCATIONS/invt/mkt/1S20050213455463 Output from smbclient: added interface ip=192.168.1.122 bcast=192.168.1.255 nmask=255.255.255.0 session setup failed: Call timed out: server did not respond after 2 milliseconds My reasoning so far is this: 1. Since I can print half the time, there is nothing wrong with the networking or name resolution. 2. Since I can print some of the time SMB printing is set up correctly. 3. Would it help if I increase the timeout period for setting up NETBIOS Sessions, how can I do this? What could cause the session setup to fail sometimes? Can you suggest possible causes and remedies please? Will my increasing the time out period help? Please post any replies to the above newsgroup, or send them to me at this address. Tks & Rgds, Joseph Carri __ Do you Yahoo!? Yahoo! Sports - Sign up for Fantasy Baseball. http://baseball.fantasysports.yahoo.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] How Can I Increase Session Setup Timeout Period - Help!!
I posted the message below, some time ago, and haven't got any suggestions yet. I would be most grateful if anyone could tell me how I can increase the timeout period for setting up NETBIOS Sessions for smbclient, as this would perhaps solve the problem. By the way, there is no problem when printing from any Windows machine. PREVIOUS MESSAGE FOLLOWS I have been trying to use Samba 2.2.6 to permit printing from two SCO Openserver 5.0.7 servers (VDOHOM & VDOHOM2) on the WAN consisting of networks 192.168.1.0, 192.168.11.0 & 192.168.21.0, interconnected by ISDN leased lines using CISCO 805 routers. The network has been up and running for months and there are no communications problems. Users have been runing various Oracle applications on Win2K servers, connecting to the internet through another Win2k server and a firewall, and connecting to the Unix servers with Telnet. I installed and configured Samba to print to printers attached to the WIN 2003 Servers JUMBOSRV1 & MSTSVR on 192.168.11.200 & 192.168.21.200 respectively, using smbprint.sysv. All Samba parameters are at default value. The WIN 2000 Server (W2k-SVR, 192.168.1.1) is the PDC & WINS Server for the entire domain, consisting of all three LANS. Printing from any Windows workstation to any of teh printers functions correctly. I have created a user called samba on the two Openserver machines as well as on the Windows Domain. The user was added with with useradd & smbpasswd. I do not have any problem accessing or browsing test shares on the UNIX machines. I am currently trying to set up the printing from the UNIX servers to the WIN 2003 Server jumbosvr1. I intend to set up a similar print facility on mstsvr after this. My problem is this. Some of the time, I can print from either Unix server without any problems at all. However, about half the time, lpstat claims the document has been printed, but nothing in fact is printed. The Win 2003 servers do not show any queued documents. When a document prints correctly the arguments (passed by lp -d jumbo -ob filename) to smbrpint.sysv (redirected to a log file) are: Arguments = jumbo-3 root 1 b /SPARE/APPLICATION/LOCATIONS/invt/mkt/x And the smbclient message (I have redirected output to a log file) is: added interface ip=192.168.1.122 bcast=192.168.1.255 nmask=255.255.255.0 Domain=[DOMAIN] OS=[Windows Server 2003 3790] Server=[Windows Server 2003 5.2] smb: \> CR/LF<->LF and print text translation now on smb: \> putting file - as stdin-27268 (14.1 kb/s) (average 14.1 kb/s) When a document fails to print, smbclient produces the arguments passed to smbprint.sysv are: Arguments = jumbo-38110 root 1 b /SPARE/APPLICATION/LOCATIONS/invt/mkt/1S20050213455463 Output from smbclient: added interface ip=192.168.1.122 bcast=192.168.1.255 nmask=255.255.255.0 session setup failed: Call timed out: server did not respond after 2 milliseconds My reasoning so far is this: 1. Since I can print half the time, there is nothing wrong with the networking or name resolution. 2. Since I can print some of the time SMB printing is set up correctly. What could cause the session setup to fail sometimes? Can you suggest possible causes and remedies please? Will my increasing the time out period help? How can I do this? Tks & Rgds, Joseph Carri -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Unreliable Printing -- Samba To Win 2003 Printer
Hi, I have installed Samba 2.2.6 on a SCO Openserver 5.0.7 System connected in a WAN. The WAN has includes three networks (192.168.1.0, 192.68.11.0, & 192.168.21.0) connected by ISDN leased lines and CISCO 805 routers. I have no problem with the network, and all Windows users as well as (telnet) UNIX users have been using the setup for several months. I need to print from the UNIX machine on 192.168.1.0 to a printer connected to a W2003 server on 192.168.11.0 I have set up Samba with smbprint.sysv and have none of the usual problems. The hassle I have run into is this. When I give a print from the UNIX machine, some of the time it prints fine on the target printer. Sometimes, however, nothing gets printed, and the target machines spooler does not even get the print file. *** When a document prints correctly the arguments (passed by lp -d jumbo -ob filename) to smbrpint.sysv are: Arguments = jumbo-3 root 1 b /SPARE/APPLICATION/LOCATIONS/invt/mkt/x And the smbclient message (I have redirected output to a log file) is: added interface ip=192.168.1.122 bcast=192.168.1.255 nmask=255.255.255.0 Domain=[DOMAIN] OS=[Windows Server 2003 3790] Server=[Windows Server 2003 5.2] smb: \> CR/LF<->LF and print text translation now on smb: \> putting file - as stdin-27268 (14.1 kb/s) (average 14.1 kb/s) When a document fails to print, smbclient produces the arguments passed to smbprint.sysv are: Arguments = jumbo-38110 root 1 b /SPARE/APPLICATION/LOCATIONS/invt/mkt/1S20050213455463 Output from smbclient: added interface ip=192.168.1.122 bcast=192.168.1.255 nmask=255.255.255.0 session setup failed: Call timed out: server did not respond after 2 milliseconds * My reasoning so far is this: 1. Since I can print half the time, there is nothing wrong with the networking or name resolution. 2. Since I can print some of the time SMB printing is set up correctly. What could cause the session setup to fail intermittently? Can anyone suggest possible causes and remedies please? Rgds, Joseph Carri -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
