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

Conference ranger::pwosf

Title:PATHWORKS for OSF/1
Notice:see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX
Moderator:CPEEDY::LONG
Created:Thu Apr 22 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1874
Total number of notes:6870

1854.0. "Invalid license when making a connection via ras" by RANGER::BACHUS::DHAENS () Tue May 13 1997 15:25

    subj:
    	Via a RAS no connection to a Pathworks server because of bad
    license.
    
    A Windows 95 client with Pathworks 32 installed receives a error58 when
    making a connection to the Pathworks server.
    On the server the license server reports a:
    Tue May 13 16:47:28 1997 CLIENT_LICENSE_INVALID:
            Client Id = ^P,
            Client Addr = ,
            Product = ^PM-|M-^?^_^A,
            Group = default,
            Reason = No Licenses Available
    This while the client has a license stored locally.
    We loaded the license to the client via the network connection.
    
    We can work around with a server based license.
    
    What must be done to assign a license to a RAS client?
    
    /Geert
T.RTitleUserPersonal
Name
DateLines
1854.1Known problem with Windows NT RAS server defaultsJAMIN::WASSERJohn A. WasserWed May 14 1997 15:2029
> Windows 95, PATHWORKS 32, RAS connectionto a PATHWORKS server, error 58 
> This while the client has a license stored locally.

Symptom: PATHWORKS servers act as if a PATHWORKS client connected via
Dial-Up NetBEUI (RAS) through a Windows NT RAS server does not have a
client license, even when it does.

Cause: By default the Windows NT RAS server will only allow connections
to the "Workstation" and "Messaging" services on a Dial-Up client.  When
asked by the PATHWORKS server to connect to the License Transponder
service, the Windows NT RAS server replies that although such a service
is present on the client, it is not ready to accept any connections.

Solution: Set the REG_DWORD

        "HKEY_LOCAL_MACHINE\
                SYSTEM\
                        CurrentControlSet\
                                Services\
                                        RemoteAccess\
                                                Paremeters\
                                                        NetBIOSGateway\
                                                                RemoteListen"

        in the Windows NT Registry of a RAS server to the value 2 (or
        create it with that value if it doesn't exist). This allows
        connections to all NetBIOS services on the RAS client such
        as the License Transponder service.

1854.2two parametersRANGER::BACHUS::DHAENSFri May 23 1997 11:0813
    
            "HKEY_LOCAL_MACHINE\
                    SYSTEM\
                            CurrentControlSet\
                                    Services\
                                            RemoteAccess\
                                                    Paremeters\
                                                            NetBIOSGateway\
                                                                   
    Remotelisten=2
    enablebroadcast=1
    
    /Geert Dhaens