Some additional info I have found so far.  The first is from Microsoft and
is for Windows ME, but I suspect the info still applies.

http://support.microsoft.com/default.aspx?kbid=294439

This one is more related to XP.  It mentions that the printer has to be on
an IIS system.  Hmmmm... Is IIS part of XP Pro?  I know that this solves our
problem here at work though since we DO have a print server running on an
IIS system.

http://support.microsoft.com/default.aspx?scid=kb;en-us;307847&Product=winxp

JP




----- Original Message ----- 
From: "John E. Peterson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 18, 2004 8:39 AM
Subject: Re: Remote printing


> Well, this post at least explains the process (yes, this original post and
> my post were both about printing across the internet, not a LAN).  I at
> least know I can research IPP.
>
> So -- if a lot of people WANT IPP as part of VNC (or FTP as part of VNC)
how
> does it get suggested.  I know it's open source and I can make it do
> whatever **I** want, but it is more helpful if eventually it is a complete
> package.  Or are we now getting out of the realm of what VNC was intended
to
> be?  A simple "screen viewer" type application?
>
> Thanks
>
> John
>
>
> ----- Original Message ----- 
> From: "hungerburg" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, February 18, 2004 5:54 AM
> Subject: Re: Remote printing
>
>
> > > Subject: Remote printing
> > > Date: Tue, 17 Feb 2004 12:04:31 -0700
> > >
> > > No, the remote client is many miles away.
> > >
> > > The local client's printer is attached to the client's computer at the
> same
> > > remote location, many miles away.
> >
> > Terms: the _servers_ screen's content is displayed at the _client_.
> > there is mostly always a person sitting at the clients side. server may
> > be a headless station. so lets call the server the remote, and the
> > client the local side of the connection (just like with the web).
> >
> > printing on the server/remote is the default. printing to client/local
> > is more involved: on the client computer you have to install some kind
> > of print server. on the server computer you have to tell a printer
> > driver to use that print server for output.
> >
> > there are several options, depending on the kind of connection between
> > the peers. on a LAN, in the same building, your printers may already be
> > shared between your workstations.
> >
> > if your vnc connection is routed across the internet, you may consider
> > using IPP, the "Internet Printing Protocoll". there is client and server
> > support in w2k, mac os X and most recent gnu/linux distributions; hp
> > jetdirect print server appliances and maybe others support it too.
> >
> > setup is very similar to vnc setup, just the other way around: the print
> > server is at the vnc client side and vice versa;  so is firewall
> > configuration, you need to forward port 631 on the print server side.
> > in the printer driver setup, on the vnc server side, you have to enter
> > the hostname or ip-address of the print server, as you do, when
> > initiating a vnc connection.
> >
> > regards,
> >
> > hungerburg.
> >
> > PS: shouldnt this be a FAQ? please use this text as fit.
> > _______________________________________________
> > VNC-List mailing list
> > [EMAIL PROTECTED]
> > To remove yourself from the list visit:
> > http://www.realvnc.com/mailman/listinfo/vnc-list
> _______________________________________________
> VNC-List mailing list
> [EMAIL PROTECTED]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to