|
Will do. Thanks, Mark Mark Walter Sr. Programmer/Analyst Hanover Wire Cloth a div of CCX, Inc. mwalter@hanoverwire.com http://www.hanoverwire.com 717.637.3795 Ext.3040 /"\ \ / X / \ "Fritz Hayes" <fhayes@spiritone.com To: "'Midrange Systems Technical Discussion'" <midrange-l@midrange.com> > cc: Sent by: Subject: RE: Remote Printer midrange-l-bounces@mi drange.com 01/14/2003 01:16 PM Please respond to Midrange Systems Technical Discussion Well, try the remote outq, LPD path. That would confirm OK communications. There is also a IP Time to Live tweak that I am checking on. Fritz Hayes > -----Original Message----- > From: midrange-l-bounces@midrange.com [mailto:midrange-l- > bounces@midrange.com] On Behalf Of MWalter@hanoverwire.com > Sent: Tuesday, January 14, 2003 9:45 AM > To: Midrange Systems Technical Discussion > Subject: RE: Remote Printer > > > Fritz, > > It is set up as a LAN printer and a regular outq (not remote outq, > LPD,LPR) > . And I can get to it from the web client. > > > Thanks, > > Mark > > > Mark Walter > Sr. Programmer/Analyst > Hanover Wire Cloth a div of CCX, Inc. > mwalter@hanoverwire.com > http://www.hanoverwire.com > 717.637.3795 Ext.3040 > /"\ > \ / > X > / \ > > > > > "Fritz Hayes" > <fhayes@spiritone.com To: "'Midrange > Systems Technical Discussion'" <midrange-l@midrange.com> > > cc: > Sent by: Subject: RE: Remote > Printer > midrange-l-bounces@mi > drange.com > > > 01/14/2003 12:01 PM > Please respond to > Midrange Systems > Technical Discussion > > > > > > > Mark, > > It sounds like you might be mixing *LAN printer type with a Remote Outq > (LDP) printer type. Try creating a *LAN printer directly, and check that > it > creates a normal Outq. > > Something else to check: can you talk to the printer using the Web client > from the existing network to the remote network? If it doesn't work, you > may have a routing problem. > > > Fritz Hayes > <snip> > > > > No firewall between here and remote site. It is a secure WAN over a > > private frame. > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.