Re: Fw: Printing via RPC Calls in 2.2.5-pre -- drum roll -- it works:)

2002-06-06 Thread Gerald Carter 

On Thu, 6 Jun 2002, Steven J Mackenzie wrote:

 All this has made me brave enough to put my shiny new rpms on to a test
 server sharing an HP laser to NT4 clients. I'll report back tomorrow.

Steven,

Thanks for the feedback.  Always good to hear when things work :-)






cheers, jerry
 -
 Hewlett-Packard http://www.hp.com
 SAMBA Team   http://www.samba.org
 --http://www.plainjoe.org
 Sam's Teach Yourself Samba in 24 Hours 2ed.  ISBN 0-672-32269-2
 --I never saved anything for the swim back. Ethan Hawk in Gattaca--

Re: Fw: Printing via RPC Calls in 2.2.5-pre -- drum roll -- it works :)

2002-06-06 Thread Steven J Mackenzie 

More 2.2.5-pre printing RPC testing:

I've upgraded a 2.2.4-pre server to 2.2.5-pre (Last Sundays CVS).

This print server is a member of a Samba controlled domain, and uses domain
level security.

Printer drivers for an HP2200dn are shared for NT and for 2000 by the
server.

I've tested printing from Windows 2000 client (as a member of the same
domain as the print server), and from a Windows NT 4.0 client (which used
guest privs to download the drivers and access the printer). AOK.

I also tested setting printing defaults, which were set and respected.

I'll be able to upgrade my 2.2.2 servers now :)

 Thanks for the feedback.  Always good to hear when things work :-)

Thanks for the software -- when it works, it's great ;)

Fw: Printing via RPC Calls in 2.2.5-pre -- drum roll -- it works :)

2002-06-05 Thread Steven J Mackenzie 

[whoops -- reposted in plain text]

I hope working printing RPCs won't be too shocking for people! (Although I
have seen one wierd behaviour on XP ...)

I've briefly tested the 2.2.5-pre code on a Mandrake 8.2 server (100 MHz, 64
Mb ram), sharing an Epson Photo 790 inkjet printer.

This server was configured with 2.2.3a code, then ran 2.2.4, then 2.2.3a,
and now 2.2.5-pre (cvs update from Sunday June 2.

Since the upgrade to 2.2.5-pre I have tried:

File sharing with encrypted passwords and user level security, which worked
as expected.

I've uploaded a 9X driver to the server from a Windows XP client.

I've tested the printer with Windows XP client -- printer properties can now
be viewed without crashing XP spools service.

On XP pages print.

*** odd thing ***
Even though I've taken Epson Status Monitor 3 out of my Start Up folder, I
have had a couple of communication error dialogues from it after or before
(depending on the document complexity) my print outs.

The box says Check all connections and make sure all devices are on. If the
power was turned off during printing, cancel the print job. If the error
does not clear, see your manual.

It has a greyed out section for ink levels (which don't seem to be
monitorable over the network). It has a button labeled Stop that changes
to OK after the print has completed.

(I have EPSON Printer Status Agent2 running as a service.)
*** end odd thing ***

Printer default page size changed from the XP client, and remembered after
a reboot.

Printer properties and printing from Windows 98 SE tested with no problems.

Speed of communication with the printer is a *lot* better since I turned the
logging level down from 10 to 1.

All this has made me brave enough to put my shiny new rpms on to a test
server sharing an HP laser to NT4 clients. I'll report back tomorrow.

I hope this is useful information,
Steven