Re: Trouble printing out to Xyplex attached embosser

On Mar 7, 3:51 pm, <laixs...@xxxxxxxxxxxx> wrote:
"Pete" <peter.charbonn...@xxxxxxxxx> wrote in message

news:1173307152.685238.321170@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I am trying to set-up a print queue on my AIX v5.3 box to print out to
multiple devices with a shared IP on aXyplexterm server. Basically,
I need to specify the port where the embosser is attached to the
Xyplex. I believe that I need to set this up as a remote printer, but
I've never done this before. Anybody have any leads on how to
accomplish this?

You have a few options. If theXyplexserver runs an lpd daemon, you can
set up a remote queue to the queue name corresponding to the physical port
on the printer. For example, some print servers have queue names like
"raw1" or "text1" ... to correspond to desired formatting options on the
physical port 1 of the server. You can tell if your term server is running
an lpd daemon by a telnet to tcp port 515 (telnet host 515) and if
something accepts the connection, its an lpd daemon. Some remote print
server LPD daemons and AIX's rembak backend don't get along particularly
well and you may find queues go down from time to time. You can extend
queue timeout settings to minimize the occurrences.

TheXyplexservers I have worked with also accept reverse telnet style
socket print connections. TCP port 2000 + (100 * port number). So, TCP
port 2100, 2200, 2300 ... correspond to the physical ports on the server.
Try:
echo "does this print" | telnet hostname 2100 (if printer on port 1)
If you want to set up queues to network print / terminal servers that don't
go down, give a try to our TCPrint utility onhttp://www.laixsoft.com

Best regards,
Paul

Thanks Paul.

Sadly, I am still mired in trying to get this to work. Attempting to
echo "Does this work" | telnet hostname 2300 (I know the correct IP/
port from a Tandem/NonStop based app which uses the Xyplex/embosser
scheme) just gives me "Escape character is '^]'." and then a flashing
cursor. At this point, I have no way to break the telnet connection -
nothing echos back to the screen - and I'm left with having to
disconnect from the the session ungracefully.

If I simply telnet to the hostname without specifying the port, I do
get a # prompt, but again, nothing echos to the screen and I have to
exit out of the session.

I've heard that this is much simpler to set-up on a Tru64 based system
using printcap to specify the port. Not having that option on AIX
seems to be the limiting factor.

Also, I tried to telnet to "hostname 515" and got this:

telnet cx107e1 515
Trying...
telnet: connect: A remote host refused an attempted connect operation.
telnet cx107e1
Trying...
Connected to cx107e1.
Escape character is '^]'.

At which point I am again stuck. So it doesn't look like this uses an
lpd daemon/queue naming, which means setting up a remote printer won't
work. Are there any options for servers that don't run an lpd daemon?

Thanks again for any help,
Peter

.

Relevant Pages

  • Re: IIS and SBS 2003
    ... I have a new sbs2003 install and if I telnet to localhost ... port 80, and type hhh and hit enter it returns a HTTP/1.1 400 Bad ... "broken" sbs server, it connects but then dumps me. ... If I http to localhost, companyweb or anything I get Cannot Find ...
    (microsoft.public.windows.server.sbs)
  • Re: Suggestion for a lexical (login mode via TCPIP)
    ... Not sure of it is the right one to modify or to add another one, but it would be useful to be able to get information on whether the user us coming in via FTP, TELNET, etc. ... This would also allow a LOGIN.COM to check if someone is coming in through a secure/SSL port for instance. ... For the HP SSH server, it seems to be undefined. ... forget about the possibility of virtual terminals. ...
    (comp.os.vms)
  • Re: RDP access to SBS 2003 - HELP please
    ... Might I add that 'out of the box', when I first got the server it worked ... of it to the telnet prompt and quit. ... Try the remote desktop connection to see if it works. ... the effect that it can't connect to xxx.xxx.xxx.xxx port 23. ...
    (microsoft.public.windows.server.sbs)
  • Re: IP Blocker in SBS2003 exchange
    ... > What I was trying to explain in the telnet section was that I realise ... > the server is listening for connections on ports 110 and 25. ... > but he can connect to port 110. ... > well as another wireless broadband connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: User access form remote Site ove managed VPN
    ... I think you have the syntax wrong in your telnet command. ... If you try and use a colon, it defaults to port 23 which is why you got ... the basic directions for implementing a terminal server on SBS2003 domain. ... managed VPN link between remote sites and headoffice. ...
    (microsoft.public.windows.terminal_services)