Re: Printing from TRU64 Unix to Windows 2000 Printer Queue

From: Michael D. Ober (obermd._at_.alum.mit.edu.nospam)
Date: 10/26/05

  • Next message: rainer lörwald: "Re: Printing from TRU64 Unix to Windows 2000 Printer Queue" 
    Date: Wed, 26 Oct 2005 15:16:37 -0600

    Thought of that today. Since I have full access to my Cisco Router, I did a
    packet sniff there. They aren't arriving. I also discovered that
    traceroutes from the Unix server also doesn't tunnel properly. As for the
    printer type and name, the name is "Printer4" on each end and the printer is
    a HP LaserJet 5Si without Postscript. We have removed all the filters while
    working on the connectivity issues.

    Mike Ober.

    "rainer lörwald" <rainer.loerwald@gmx.de> wrote in message
    news:435FE2B3.24969B3E@gmx.de...
    > Micael,
    >
    > install ethereal on the 2000 server to check if the packets
    > arrive and what the response of the 2000 system is. This
    > should help. Is the printer name exactly Printer4? Be sure
    > due to case sensitive behavior of Unix. Does the printer
    > support Postscript?
    >
    > Rainer
    >
    >
    > "Michael D. Ober" schrieb:
    > >
    > > Here's the /etc/printcap entry on the unix side.
    > >
    > > lp18|18|WAKE:\
    > > :af=/usr/adm/lp18acct:\
    > > :if=/usr/lbin/lpf:\
    > > :lf=/usr/adm/lp18err:\
    > > :lp=:\
    > > :mx#0:\
    > > :of=/usr/lbin/lpf:\
    > > :pl#66:\
    > > :pw#80:\
    > > :rm=WAKE:\
    > > :rp=Printer4:\
    > > :sd=/usr/spool/lpd18:\
    > > :xf=/usr/lbin/xf:
    > >
    > > /sbin/ping WAKE returns
    > >
    > > PING WAKE (10.96.253.1): 56 data bytes
    > > 64 bytes from 10.96.253.1: icmp_seq=0 ttl=45 time=98 ms
    > > 64 bytes from 10.96.253.1: icmp_seq=1 ttl=45 time=310 ms
    > > 64 bytes from 10.96.253.1: icmp_seq=2 ttl=45 time=94 ms
    > > 64 bytes from 10.96.253.1: icmp_seq=3 ttl=45 time=94 ms
    > > 64 bytes from 10.96.253.1: icmp_seq=4 ttl=45 time=95 ms
    > > 64 bytes from 10.96.253.1: icmp_seq=5 ttl=45 time=96 ms
    > > 64 bytes from 10.96.253.1: icmp_seq=6 ttl=45 time=94 ms
    > > 64 bytes from 10.96.253.1: icmp_seq=7 ttl=45 time=93 ms
    > > 64 bytes from 10.96.253.1: icmp_seq=8 ttl=45 time=94 ms
    > >
    > > ----WAKE PING Statistics----
    > > 9 packets transmitted, 9 packets received, 0% packet loss
    > > round-trip (ms) min/avg/max = 93/118/310 ms
    > >
    > > I can LPR from a Windows workstation to this printer, so I believe that
    I
    > > have configured the printer correctly on the windows server. I have
    also
    > > previously successfully used LPR from a VMS system to this same windows
    > > server. The only thing I can think of is that the LPR is timing out as
    the
    > > link is through a site to site VPN and is rather slow. I have verified
    the
    > > IPSec Security Attributes are not blocking the packets.
    > >
    > > Mike Ober.
    > >
    > > "rlmobil" <rlmobil@gmx.de> wrote in message
    > > news:opsy5ycfc09cwxr8@dedre-ddzyyy0j.emea.thermo.com...
    > > > Mike,
    > > >
    > > > Do you have an appropriate entry in your /etc/printcap file defining
    the
    > > > printer?
    > > > I never tried this way round (always had the printer on the *x*-box),
    but
    > > > it should work.
    > > >
    > > > Rainer
    > > >
    > > > On Wed, 19 Oct 2005 09:01:42 -0600, Michael D. Ober
    > > > <obermd.@.alum.mit.edu.nospam> wrote:
    > > >
    > > > > I need to configure my Windows 2000 AD Server to accept print jobs
    from
    > > a
    > > > > Tru64 Unix system. I have installed Services for Unix and set the
    port
    > > > > to
    > > > > be an LPR port in the printer properties. Based on the
    documentation I
    > > > > found, this should be sufficient to respond to
    > > > > lpr -P<myserver> -S<printershare>. However, nothing ever appears in
    the
    > > > > printer queue for this printer. The printer itself is configured as
    a
    > > > > "local" TCPIP port and printing from Windows to this printer queue
    to
    > > the
    > > > > printer works fine.
    > > > >
    > > > > Thanks,
    > > > > Mike Ober.
    > > > >
    > > > >
    > > > >
    > > >
    > > >
    >

  • Next message: rainer lörwald: "Re: Printing from TRU64 Unix to Windows 2000 Printer Queue"

    Relevant Pages

    • Re: LPR printing problems with Windows Server 2003
      ... servers to track printing costs. ... Pcounter I was running (version 2.50 windows) had an issue. ... Novell printer object that prints using LPR to the aforementioned printer ... LPR printing through the Windows 2003 server, ...
      (microsoft.public.windows.server.general)
    • Re: LPR printing problems with Windows Server 2003
      ... We originally used Novell NDPS printing, ... printer object that prints using LPR to the aforementioned printer and IP ... through the Windows 2003 server, or 3) via LPR printing through the Novell ...
      (microsoft.public.windows.server.general)
    • Re: LPR Problems
      ... are these additional lines actually being sent from the Windows 2003 Web ... What options are you using on the lpr command in the batch file? ... What OS is running on the "controlling pc" that is receiving the print ... > I'm using LPR on a windows 2003 web server, to send a file to a network ...
      (microsoft.public.win2000.printing)
    • Re: Cant Access Network Resources. Clock Sync errors
      ... Its talking to a Win2K3 Server, ... I can see KerberosV5 packets. ... Repadmin is included Windows support tools, ... If the replication works fine, I recommend you reset computer account ...
      (microsoft.public.windows.server.active_directory)
    • Re: Network Monitor
      ... Got me - and in any case this utility only captures packets, ... need a Server copy of Windows to load and analyze the packets captured. ... >> * PLEASE post all messages and replies in the newsgroups ...
      (microsoft.public.windowsxp.network_web)