[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference jamin::pathworks32

Title:Digital PATHWORKS 32
Moderator:SPELNK::curless
Created:Fri Nov 01 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:337
Total number of notes:1612

229.0. "Print Services over Multinet IP?" by ALFSS2::MEADOWS_C () Tue Apr 15 1997 16:22

    
    Is PATHWORKS 32 Print Services supported using Multinet 3.5b on the 
    VMS side? Does anyone have any experience doing this with Multinet?
    
    We are able to PING the VAX from the PC and vice-versa. He can make 
    file and print share connections over IP. He does not run DECnet on 
    either side. We are using a PC running 95, not NT.
    
    We have tried setting up a remote printer and everything looks 
    fine but when we try to do a TEST QUEUE we get the error 
    %PWPRINT-E-TCPOPERR, TCP/IP Open Error
    Same error is all that shows in log file. 
    
    When printing from a DCL prompt it goes to the queue then the queue 
    permanenetly stalls until we reset the queue. 
    
    In PWPRINTMGR we set this up as follows:
    queue	BABC_HD_211A
    node name 	150.135.67.19 (in same subnet as VAX)
    protocol	TCP/IP
    connect	direct
    location	LPT1: (In my test with UCX it would not work unless set to 
                       LPT1:. We tried the share name as well in his 
                       configuration). 
    
    VAX is defined in LMHOSTS on PC and PC is defined in local name table 
    on VAX.
    
    Thanks in advance for any assistance. 
    
    Cindie Meadows
T.RTitleUserPersonal
Name		DateLines
229.1here's some hints...INTONE::BUMPUSTue Apr 15 1997 18:0120
    I'm no expert but I did some setup of PWPRINT myself via both DUNIX 
    and VMS systems......
    
    The location you speak of in your note you say it is set to LPT1:.
    This may need to be set to the node name of the "serving" Win95
    PC including the printer queue_name....  e.g. \\pc_lab\hplaser.
    
    If that makes sense, try it.  If you try it and still it won't work
    then.....let's just see if you can do local printing between the Win95
    PC and the attached printer (on the lpt1: port on the back of your PC).
    Send a notepad note to the printer and make sure it comes out.
    
    Other stuff to try.....refer to my note (I forget which number, it
    is about 10 notes earlier in this same conference...).
    
    Let me know how you do.
    
    \\dave_b
229.2ALFSS2::MEADOWS_CTue Apr 15 1997 19:0820
    
    
    We've tried so much it gets hazy but I will try again. 
    
    The Help files, which I did read thoroughly, actually state that 
    Connection type: DIRECT is used in most cases and gave the options 
    as filename, printername or port. 
    
    In the case of Connection type:NETWORK it listed \\NTserver\Declaser as 
    the only option. 
    
    Is \\PCserver\printername valid when set for Connection type:DIRECT ?
    
    Not documented as such, but I will try again and post results, even
    though for me, using UCX works fine with DIRECT and LPT1. 
    
    Thanks for any suggestions,
    Cindie
229.3Can We IPMT When Multinet Is Suspect?VMSNET::P_NUNEZThu Apr 24 1997 10:1610
    
    But the real question that needs answering for support purposes is:
    
    	Does PWPRINT officially support Multinet?  
    
    If yes, we can IPMT.  If no, we can't, so we push customer to Cisco.
    We just need to know.  We've not found anything documented for 3rd
    party vender IP stacks (just DEC's).  
    
    Paul
229.4SPD & release notesCPEEDY::ORRThu May 01 1997 11:317
FYI,

 I reviewed the release notes and the SPD and could not find any reference
to using/supporting PWPRINT with UCX only. All references say TCP/IP and
I see nothing for specific implementations...

Ed
229.5PATHWORKS 32 User Guide Page 7-9ALFSS2::MEADOWS_CFri May 02 1997 18:0921
    
    
    
    Quoting Page 7-9 of the PATHWORKS 32 User's Guide:
    
    INSTALLATION PREREQUISITES
    Operating system and network protocol requirements are as follows:
    
    Operating System 		Network Protocol
    
    OpenVMS v5.5-2 or later	TCP/IP Services for OpenVMS v3.3 or later
                                DECnet phase IV or DECnet/OSI
    
    Open VMS Alpha v6.2		TCP/IP services for OpenVMS v3.3 or later
       or later			DECnet phase IV or DECnet/OSI
    
    
    
	Cindie
229.6ALFSS2::MEADOWS_CFri May 02 1997 18:156
    Also see page 7-3 -- Network Protocol Implementation and Support 
    
    Only lists DECnet, DECnet/OSI and/or TCP/IP services for OpenVMS (UCX) 
    when using OpenVMS.
229.7User Guide vs Release notes & SPDCPEEDY::ORRWed May 07 1997 15:4116
Cindie,

 Thanks for the reply. 
 
re:  references in the user's guide. 

 I am not sure the customer is accepting the user's guide as the
document to follow. I had hope that the SPD or release notes would address
this issue. I think more is needed than the user's guide. But at least that is
something.

Unfortunately, the site in question may make their decision to continue to use
PATHWORKS based on TCP/IP compatability.

thanks,
Ed