Conference ranger::pathworks_netware

re: .0

hmmmmm....

NVT isn't suppose to work well under *any* "Windows" environment.  

John

    Hi John,
    
    So the next question is will there be an NVT for Windows '95? If yes,
    will it work over Token Ring? :-)
    
    cindy
    

    So the next question is will there be an NVT for Windows '95?

>>> I sincerely doubt it...

   If yes, will it work over Token Ring? :-)

>>> Yes


>>>
>>> Now for my question: If a customer has Windows 95 clients and OpenVMS,
>>> why not simply use TCP/IP as the transport?  It comes free with Windows 95
>>> and OpenVMS (via NAS).  If not TCP, why not DECnet?  Comes free with
>>> PATHWORKS on the client and free with NAS on the server.
>>>
>>>
>>> John    

    
    NVT will work under Windows-95.  (There were some issues, but they
    go resolved in the fall of 1995.  I doubt whether anyone tested
    it explicitly using token-ring, but there is no reason why it shouldn't
    work with any particular frame-type.)
    
    A few caveats...
    
    	(1) Make that they use the NVT client piece that
    	    we supply on the client-volume that comes as part
    	    of the PATHWORKS NetWare server.  (Look in [PWVN$SYSVOL.PUBLIC])
    
    	(2) If they are using SETHOST as their terminal emulator, be sure
    	    that they are using the latest version.  (V6.0.011).
    
    	(3) Do all the operations from a single 'DOS-box' window.  (Load 
    	    NVT first, then bring up the terminal emulator, then make
    	    the NVT connection.)
    
    	    Whether we officially 'support' this is a different question.
    	    And, I don't recall whether *multiple* NVT sessions from the
    	    same Windows-95 client were shown to work.  But, our collection
    	    of testing notes indicate that NVT was basically working under
    	    Windows-95 (after bugs specific to Windows-95 were fixed in
    	    both the NVT 'tsr' and SETHOST pieces).
    
    	    
    						Dave

    Hi Dave!
    
    Either I forgot how to get sethost and NVT working or I am doing
    something incorrect.  
    
    I go to a DOS window on 95. I copy over NVT.EXE, I load NVT.exe. This 
    is successful. I then copy sethost 6.0.011 and invoke SETHOST.  I 
    select F3, Communications, Setup, Network, NVT, ALT-T, enter on my 
    service.  F3 to get back to Sethost. 
    
    Service type is now NVT, Session 1 states Connect-NVT14-inactive.  How 
    do I activate this client?  I press F3 to return to SETHOST, press
    enter a couple of times, no username prompt, no errors.
    
    I also happen to be running Novell's NetWare Client 32 and not the 
    Microsoft client. Nor am I using Token Ring. Did I miss a step?
    
    Thanks!
    
    cindy
    
    p.s. to John. Customer states to use TCP/IP they would have to use the
    LANman server which is now additional overhead on the server. Customer
    also states additional licenses would have to be purchased. Current
    resolution based on your reply is to use a serial connection to a
    DECserver.  But if we can this to work...I know this is Dave's favorite
    customer!
    

    Hi,
    
    I just copied over the nvt.exe from a 5.0e server. Works fine with
    Sethost.  The NVT.EXE is dated 9/29/95. Just like the other copy I was
    using for testing.
    
    hmmm....
    
    but it works! I'll check versions with the customer.
    
    cindy