Printer via Print server with tcp/ip

[Jan van den Ende]

Hakan,

I stand corrected.

Obviously one of the effects of so many printers must have been that contention was rare.

Proost.

Have one on me.

jpe

[Bill Hall]

Edgar,

My first thought on reading your post was that you have an asynchronous communication problem, probably the handshaking. Are you using a network print server connected to the printer's serial port or parallel port such as one of the HP Jetdirect servers?

Bill

[Edgar Ulloa]

Hi
The print server is a internal card of tally printers.

another one is conected a print server hpjetdirect 300x with same efects.

I will try to regenerate the queue completly and try again.
regards

[Edgar Ulloa]

Labadie ask me about reply/ena=printer

this message show me continue

TCPIP$TELNETSYM - (planta) open_socket_ast invoked with bad IOSB 556: device time out

[Hakan Zanderau ( Anders]

Edgar,

You have to tell me the whole story.......

It worked/works when.....
and when we...... it fails.

Have the printers/queues ever worked as expected ?

I have a lot of other questions, but let's start here.

One thing about the logicals....
The logicals are red at image activation ( start of the queue ).
You can't define a logical name without restarting the queue ( killing the symbiont process ) and the logicals are used during the lifetime of the symbiont process.

Now we are talking about logicals for TELNETSYM. ( to avoid any remarks )

regards,

Hakan Zanderau
HA-solutions

[Jan van den Ende]

Edgar,

>>>
Printer queue LTA120, busy, on YIRE2::"lta120:9100",
<<<
combined with
>>>
TCPIP$TELNETSYM - (planta) open_socket_ast invoked with bad IOSB 556: device time out
<<<

leads to the question:

What is the result of NSLOOKUP LTA120 , if executed from YIRE2 ?
(if it not already exists, first create a foreign command symbol
$ nslookup :== $ TCPIP$NSLOOKUP
)
If this gives a result, and the result is the correct IP address, try PING LTA120
If NSLOOKUP fails, then check your name resolution. (do you use DNS or TCPIP$HOSTS? ;
How is your DNS defined? And the ROUTING?

The open_socket_ast is usually a sign of unrecognised queue address.

Proost.

Have one on me.

jpe

[junaid akhtar]

As we are using Integrity Rx3600 and VMS 8.3
and we are printing through 3com switch on PRINTRONICX printer using tcpip.here is the command we are using .it may help you
Make a file name TCPIP_QUEUS.COM
and put the following command in it
$ init /queue (logical name of printer) /process=tcpip$telnetsym /start /default=(nofeed,flag) /on=node name::"ip address of printer:9100"
put this file in startup file.

[Hakan Zanderau ( Anders]

Edgar,

Sorry, but I'm leaving this thread.

[Hakan Zanderau ( Anders]

Sorry Edgar, but I can't leave this without

Jan, have you EVER tried starting a TELNET-queue using a NON-existing hostname ?

$ INIT/QUE/START/PROC=TCPIP$TELNETSYM/ON="IDONTEXIST:9100" TEST
%SYSTEM-F-IVDEVNAM, invalid device name

regards,

Hakan Zanderau
HA-solutions

[Jan van den Ende]

Hakan,

>>>
Jan, have you EVER tried starting a TELNET-queue using a NON-existing hostname ?
<<<

Yes. I know that.

-Have you ever started a queue succesfully on on node, and then failed over to a node that did NOT have the correct name resolution?
-Have you ever had a printer (relocated and) given an other IP address WITHOUT informing VMS management?
-Have you ever have the network people reconfigure some subnet without telling you?
(-and have you ever had a printer removed, without the users realising that the printer they have "always" used is now gone?

All these generate
open_socket_ast
and if:
your printers are spread up to 100KM away; your network people are a different group, located in a different building;
your periferal device handling department is a different group again, which ONLY understans M$, and are incapable of understanding WHY they should report changes in periferal configs to others than the M$ admins,
THEN you get used to "open_socket_ast", on average at least one new one each week.

fwiw.

Proost.

Have one on me.

jpe