X-Spam-Check-By: sourceware.org Date: Wed, 23 Nov 2005 13:39:59 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: lpr error (Was :Re: Enscript error with passwd uid field (enscript-1.6.3-3)) Message-ID: <20051123123959.GT2999@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Nov 23 12:49, Jurgen Defurne wrote: > I do have a real problem, but not with enscript, but with accessing > the printers. > > In the past, I could set PRINTER to //server/printershare, and use > enscript and lpr to print out my jobs. > > If I try to print now, I get the following message from lpr : > lpr: printer error: can't open '\\beqbrgbrg1ms0p1\psbe31.lnk' for > writing: The printer name is invalid. > > Upon further investigation, it seems that I cannot contact any > printers anymore from cygwin upon our print server, but I > can see those printers from my explorer. > > Ie. If I do 'ls //server' I should probably see the printer shares, > like any other share on the same server. No, the shares under //server are only of type disk, not type printer. Contacting the printer using the above $PRINTER variable should work in the snapshots. Please try the latest one from http://cygwin.com/snapshots/ Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/