Printer issue - new

Thu Feb 20 13:17:22 PST 2020

Mark,

I agree this is not an FP Tech issue.  The print problem came up after a
Windows 10 upgrade in early December.  Before that everything worked fine.

I did see an issue with print jobs reaching the print Que and taking over 5
minutes to begin printing.  I could see the print job in the Que.  This even
happened when trying to print a test page.

FilePro was accessing the printer but the print job weas not printing as it
had in November or early December prior to the upgrade.

Richard

> -----Original Message-----
> From: Filepro-list
<filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com>
> On Behalf Of Fairlight via Filepro-list
> Sent: Thursday, February 20, 2020 11:58 AM
> To: filepro-list at lists.celestial.com
> Subject: Re: Printer issue - new
> 
> Besides a few extra services and a lot extra in licensing fees, there are
very few
> things Server will get you that Win10 won't.  If one can, one probably
should
> save the money.  It's the fiscally responsible thing to do.
> 
> As filePro isn't really doing anything kernel-specific, or
Windows-version-specific
> (beyond the fact that at some point MS changed the console window API),
> there's really nothing for fP Tech to do other than make sure it works on
> Windows.
> 
> m->
> 
> 
> On Thu, Feb 20, 2020 at 10:38:16AM -0500, Jose Lerebours via Filepro-list
thus
> spoke:
> > Wouldn't `netcat` be a generic solution to reaching printers across
> > intra/extranet?
> >
> > Why use USB only printers and then struggle with this!?!  Get a
> > printer that can be given an IP, regardless of the PC it is attached
> > to and use `netcat` in lieu of "print" or "lp".
> >
> > What am I missing here?
> >
> > On a side note, when did WIN 10 become a "Server OS"?  We are trying
> > to run away from "complexity" and render our topology worthless.
> > There was a time where one had a "real server" or "servers" and I just
> > do not remember this kind of things being as much of an issue.
> >
> > It is so nice for us to turn to fpTech for solutions for the problems
> > we create by making bad decisions - We save $$$ and then expect
> > filePro to do things that are only a problem because of the decision
> > we've made.  It is as if to say, well, I am allowed to do a bad
> > infrastructure design and filePro is responsible thus fpTech has to fix
it ...
> >
> > Am I the only one that see something wrong with this?
> >
> >
> > On 2/20/20 9:55 AM, Richard D. Williams via Filepro-list wrote:
> > > That's what I thought.
> > >
> > > If I have a printer on a Linux server I just need to add that to my
> > > config file.
> > > Then, anyone can reach it.
> > >
> > > When a printer is added to the FP Windows config, does not that
> > > printer need to be on each PC?
> > >
> > > Richard
> > >
> > > There is no universal way
> > >
> > > On 2/19/2020 6:31 PM, Fairlight via Filepro-list wrote:
> > > > Find, as in actual discovery?  Highly, highly doubtful.  I'd go so
> > > > far as saying 99.9999%+ unlikely.
> > > >
> > > > That would require wayyyyy more work than I can ever see fP Tech
> > > > putting in.  Hell, HP and Brother can't even get that 100% right,
> > > > and they write the damned drivers for their own printers.
> > > > (Literally, HP printers get lost, and Brother's driver is only
> > > > fine once you coax it into knowing where the printer is.  It was
> > > > -not- PnP.  At least the Brother stays connected, which is more
> > > > than I could say for the HP.)
> > > >
> > > > More succinctly: "Hah!  No way in hell do I believe it can do it!"
> > > >
> > > > m->
> > > >
> > > >
> > > >
> > > > On Wed, Feb 19, 2020 at 03:37:44PM -0600, Richard D. Williams via
> > > > Filepro-list thus spoke:
> > > > > Does windows filepro have the ability to find a printer not on
> > > > > the users PC?
> > > > >
> > > > > Richard D. Williams
> > > > >
> > > > > On 2/19/2020 1:27 PM, Richard Kreiss via Filepro-list wrote:
> > > > > > Filepro 5.0
> > > > > >
> > > > > >
> > > > > > Client installed a new "server" named data1 running Windows
> > > > > > 10 Pro with an
> > > > > > HP Printer attached using a USB port labeled virtual porter
> > > > > > port for USB.
> > > > > > Printer name is: HP Officejet Pro 8100
> > > > > >
> > > > > >
> > > > > > This printer is connected to "server" data1.  In filePro's
> > > > > > printer maintenance this printer is named HP-8100 and the
> > > > > > destination is win: HP Officejet Pro 8100. This printer is set
> > > > > > to the default printer. I can print from data1 but not any of
> > > > > > the other computer.  Any suggestions as to why this issue
> > > > > > occurs.  If someone tries to print an output they get a
> > > > > > filePro error and then an 1801 error message which means that
> > > > > > the print job is having issues with the windows defender
> > > > > > firewall.
> > > > > >
> > > > > >
> > > > > > I created an new incoming rule called printers opening the
> > > > > > ports that the printers are using.  Should I also create an
> > > > > > outgoing rule.
> > > > > > No I have not
> > > > > > had my client's test the new firewall rule yet.  I have not
> > > > > > run into this issue previously.
> > > > > >
> > > > > >
> > > > > > I am accessing the new "server" data1 using GoToMyPC and have
> > > > > > not had a difficulty creating outputs.
> > > > > >
> > > > > >
> > > > > > I did not set up this server or configure the other computers
> > > > > > for access.
> > > > > >
> > > > > >
> > > > > > filePro is installed in the folder appl which is mapped as
> > > > > > drive L.  The startup file is:
> > > > > >
> > > > > >
> > > > > > echo off
> > > > > >
> > > > > > rem Run levy Goldbery & stettner program
> > > > > >
> > > > > > rem Richard Kreiss 03/03/2010
> > > > > >
> > > > > > set PFDSK=L
> > > > > >
> > > > > > set PFDATA=L:
> > > > > >
> > > > > > set PFPROG=L:\appl
> > > > > >
> > > > > > set PFDIR=\appl
> > > > > >
> > > > > > set PFGLOB=
> > > > > >
> > > > > > set PFCONFIG=
> > > > > >
> > > > > > set PFKeyTab=DOS
> > > > > >
> > > > > > set PFTMP=C:\temp
> > > > > >
> > > > > > set PATH=%PFPROG%\fp;%path%
> > > > > >
> > > > > > %pfprog%\fp\p lg_menu
> > > > > >
> > > > > >
> > > > > > Any suggestions as to why filePro is not finding the printer?
> > > > > >
> > > > > >
> > > > > > I may have to have this client upgrade to version 6 and create
> > > > > > PDF's for printing if all else fails.
> > > > > >
> > > > > >
> > > > > > Richard Kreiss
> > > > > >
> > > > > > GCC Consulting
> > > > > >
> > > > > >
> > > > > > -------------- next part -------------- An HTML attachment was
> > > > > > scrubbed...
> > > > > > URL:
> > > > > > <http://mailman.celestial.com/pipermail/filepro-list/attachmen
> > > > > > ts/20200219/7ae83338/attachment.html>
> > > > > > _______________________________________________
> > > > > > Filepro-list mailing list
> > > > > > Filepro-list at lists.celestial.com
> > > > > > Subscribe/Unsubscribe/Subscription Changes
> > > > > > http://mailman.celestial.com/mailman/listinfo/filepro-list
> > > > > >
> > > > > _______________________________________________
> > > > > Filepro-list mailing list
> > > > > Filepro-list at lists.celestial.com
> > > > > Subscribe/Unsubscribe/Subscription Changes
> > > > > http://mailman.celestial.com/mailman/listinfo/filepro-list
> > > > >
> > >
> > > _______________________________________________
> > > Filepro-list mailing list
> > > Filepro-list at lists.celestial.com
> > > Subscribe/Unsubscribe/Subscription Changes
> > > http://mailman.celestial.com/mailman/listinfo/filepro-list
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > Subscribe/Unsubscribe/Subscription Changes
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> 
> --
> Audio panton, cogito singularis.
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list