| Stephen Gran on Mon, 06 Jan 2003 12:01:08 -0500 |
|
On Mon, Jan 06, 2003 at 10:42:31AM -0500, Gregson Helledy said: > Last week I posted about my ability to print from Win98 to a > linux machine after adding "use client driver = yes" to the > smb.conf file. > > Now I've set up my linux desktop machine (running Libranet)to > print to this same printer. All goes well, except that > sending a print job from the Libranet machine activates > the server's dial-on-demand link (diald). This sounds like a problem with name resolution - do you have the server listed in the clients' /etc/hosts ? Check using tcpdump and see what requests are being sent that cause the dial up. > The print server/dial-on-demand machine is running Mandrake 7.2 > Single Network Firewall (2.2-series kernel). Packages are: > cups-1.1.7-2.2mdk > samba-2.0.7-18mdk > > The attached (parallel port) printer is set to "raw" using the client's > driver. > > The desktop linux machine is running Libranet 2.0 I've updated cups to > the latest version in stable. > Packages are: > cupsys 1.1.14-3 > samba-common 2.2.2-10 > The cupsd.conf file has "Browsing Off", > which should (?) avoid triggering the link. > I have not changed the default ports for SAMBA (631, I think). > > Questions: > * Why is Libranet, but not windows, triggering the Mandrake box to > dial the internet? What would cups send that windows doesn't? > > * Should I not be using SAMBA to communicate between linux boxes? I wouldn't bother using SAMBA for linux clients - CUPS can communicate between boxes, and using SAMBA just adds another layer to debug. -- -------------------------------------------------------------------------- | Stephen Gran | Hanging on in quiet desperation is the | | steve@lobefin.net | English way. -- Pink Floyd | | http://www.lobefin.net/~steve | | -------------------------------------------------------------------------- Attachment:
pgpqqbK3TlIhT.pgp
|
|