 |
The Question is:
Are any problems known with remote-printing
and W2K ?
Thanks and bye
Klaus
The Answer is :
Occam's Razor -- an exceedingly useful debugging technique, the OpenVMS
Wizard might add -- points at the Windows 2000 system as the problem
here, and not at OpenVMS. Why? By your statements, OpenVMS prints to
Windows NT, but not to Windows 2000. What has changed here? Not how
OpenVMS operates with the remote (target) printer; the target environment
for the printing has changed.
Additionally, "-SYSTEM-F-REJECT, connect to network object rejected"
further points at the target system as the cause of the problem --
OpenVMS tried to connect, and the attempt was rejected by the target
system.
Please entirely expunge the phrase "didn't work" from your vocabulary.
Why? Simply because this statement -- when made in isolation, with
no supporting details -- provides no specific details of the problem(s)
being reported, and thus the problem(s) has/have an infinite set of
potential causes.
Please see topics (1020), (6239), (6316), (4316), (3424), and (2653),
among various discussions of IP printing and rejected connections.
|
|
|
|
|
