Conference irocz::terminal_servers

3487.0. "PPP/IPX problem acquiring *client-based* license" by CPEEDY::COOK (Just say NO to that AccViO! - Java!!!) Thu Apr 03 1997 17:04

	    Our "PATHWORKS/NetWare for OpenVMS" group has received
	    a IPMT/CLD case from a customer, which involves using
	    a terminal-server's PPP/IPX functionality.

	    We now have some evidence to believe that the problem 
	    is due to a bug or lack of functionality in the Digital
	    Terminal Server's implementation of PPP/IPX.  

	    Prior to this CLD, we had tested and routinely used
	    the terminal-server's PPP/IPX functionality to
	    connect to PATHWORKS/NetWare OpenVMS file-servers
	    with no problems.  However, we had always been configured
	    to use PATHWORKS *server-based* licensing.

	    The 'wrinkle' in this case, and the single-component that
	    is failing, is *client-based* license acquisition/validation
	    using NetWare/IPX protocols. (See IPMT/CLD case #49139 for 
	    the gory details.)

	    We have captured IRIS traces (of both the successful NT-RAS/PPP
	    box and the unsuccessful Terminal-Server/PPP) trials metioned
	    earlier.  These traces (from the LAN-side of the dialup connection)
	    have not (yet) shed light on the details of the problem.
	    We will be seeking their help for WAN-side tracing and
	    other general expertise in resolving this problem.

	    Our testing here was using one the LKG facility terminal
	    servers (the one at DTN 226-6823).  It is a DS900MC:
		"Network Access SW T2.1 for DS 900MC (BL 12.11-40.00)"
	    Also, here is some of it's possibly-relevant IPX setup info:

		Route Entries:	    5?[K
		RIP Entries:	    1?[K
		SAP Entries:	    0?[K

	    (where the '?'-character appears as an 'inverse-video/solid-block'
	     character on the MSWindows-95 post-connection terminal-window)
	    As mentioned before, this terminal-server functions completely
	    normally in regard to passing all IPX-traffic needed for
	    PATHWORKS file/print functionality (and *server-based* licensing
	    functionality.  It is only this *client-based* licensing
	    functionality (i.e. the subject of this CLD!), that is failing.

	    (There is a possibly-related note...note #3244 in this conference
	    discussing a known/suspected deficiency in the terminal-server's
	    PPP/IPX implementation in some detail.)


					    Dave Cook
					    [PATHWORKS Server Engineering]