T.R | Title | User | Personal Name | Date | Lines |
---|
5275.1 | Based on the number of attempts to write the note... | twick.nio.dec.com::PETTENGILL | mulp | Mon Feb 24 1997 22:19 | 1 |
| I'd say off hand that you have a local network hardware problem.
|
5275.2 | | UTRTSC::KNOPPERS | Oswald Knoppers | Tue Feb 25 1997 04:44 | 20 |
| > %SYSTEM-F-REJECT, connect to network object rejected
>
> This happens all the time..............
This is a very frequent problem with HP printers. The problem is that the
default behaviour of the telnet symbiont is that it will disconnect the
link between jobs. When the symbiont makes the second connection to the
printer for the second job, the printer is apparently not jet ready to
accept a new connection and rejects is. You can change the telnetsymbiont's
behavior by defining the ucx$telnetsym_idle_timeout logical.
> Printing a NULL-block (0/0) file will hang the queue. The job hangs
> in "processing"-state.
This sounds like a known UCX problem, fixed in latest ECO. What version of
UCX are you running?
Regards,
Oswald
|
5275.3 | It's LPD ! | ASHAM::H_ANDERSSON | | Tue Feb 25 1997 07:21 | 15 |
|
Hi,
re .1
It's not a networkproblem. I get the "reject" EVERY time the
LPDsymbiont tries to send the next job on the outgoing LPDque,
nomatter how small or how big the job is.....
re .2
It's LPD, not TELNETSYM and I use UCX V4.1 ECO2. But I get
the same problems with other UCX-versions.
/Hakan
|
5275.4 | LPD, Telnet... problem is the same... | UTRTSC::KNOPPERS | Oswald Knoppers | Tue Feb 25 1997 07:41 | 16 |
| > It's LPD, not TELNETSYM and I use UCX V4.1 ECO2. But I get
> the same problems with other UCX-versions.
Sorry, misread that. The problem is still the same though. Apparently the
printer is not (yet) ready to accept the new connection and rejects it.
Unfortunally unlike with telnet printing, there is no idle timeout logical.
In my opinion this is a problem in the HP and you customer should take it
to them.
The only thing you can do to minimize the pain is to use a logical to make
the retry interval shorter (UCX$LPD_RETRY_INTERVAL).
Regards,
Oswald
|
5275.5 | IPMT ?? | ASHAM::H_ANDERSSON | | Tue Feb 25 1997 08:51 | 13 |
|
Oswald,
Thanks for your reply. We have already tried the UCX$LPD_RETRY_INTERVAL
and thats not an option in this case.
> In my opinion this is a problem in the HP and you customer should
> take it to them
It's my opinion to, but should I post an IPMT to see if it's an
official opinion ???
/Hakan
|
5275.6 | whats in an (official) opinion? | UTRTSC::KNOPPERS | Oswald Knoppers | Tue Feb 25 1997 09:12 | 16 |
| > Thanks for your reply. We have already tried the UCX$LPD_RETRY_INTERVAL
> and thats not an option in this case.
By defining this logical to a low value should speed up things. If not,
there is something else the matter.
> It's my opinion to, but should I post an IPMT to see if it's an
> official opinion ???
It *is* actually the printer sending the reject. This is proof enough (IMHO)
that the problem is not ours. So lets not spend money on this by examining
HP problems.
Regards,
Oswald
|