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-37777 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 20000 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/
On Wed, Feb 23, 2005 at 09:27:45PM -0800, Joseph Carri wrote:> > 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 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. > > 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.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.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joseph Carri wrote: | I have been trying to use Samba 2.2.6 to print from | two SCO Openserver 5.0.7 servers (VDOHOM & VDOHOM2, IP .... | 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. Try smbclient from 3.0.11. 2.2.x is EOL (kind of like SCO :) ) | 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-37777 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 20000 milliseconds Look at network traces. The windows server is not responding apparently. Also try saving some of the failed spooled jobs and print them manually. You might also look at the cups smbspool utility in 3.0 or IPP printing in windows 2000. | 3. Would it help if I increase the timeout period for | setting up NETBIOS Sessions, how can I do this? You can try. However, I'd be more interested in why the windows server hangs the session. Bottom line is that there is really nothing to point at finger at smbclient here. No without more information at least. But 2 things should probably happen before anyone digs in deeper. (a) try smbclient from Samba 3.0 and try to reproduce the error on a non-SCO box. cheers, jerry ====================================================================Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCHfAKIR7qMdg1EfYRAp31AJsFh0zqZL0Z8q929cb2tWdwcD82wgCfb+NI Ad23uscEVn6SRBrdYt9dzlU=a538 -----END PGP SIGNATURE-----
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