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

Conference noted::pwv50ift

Title:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:CPEEDY::KENNEDY
Created:Fri Dec 18 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4319
Total number of notes:18478

4185.0. "Unlicensed Win95 client can connect" by CTHU22::M_MORIN (Mario Morin, Hull CSC - Canada) Mon Mar 03 1997 10:30

Hi,

Ever since PATHWORKS for Windows95 came out we were always under the
impression that an unlicensed PC coulc not connect to a PATHWORKS V5
Server.

Indeed, at the CSC, many customers have called to say that they can't
connect.  When we check and find out they're not running the licensing
component on the client we tell them to do so and they're OK from that
point on.

Now, in our lab at the CSC, we have more than one unlicensed Windows95
PC that CAN connect to our server and we have tried everything imagineable
to make it fail as it's supposed.  When we have a look at the license
registrar log file on the server, we see that the PC is being recognised.
With PWRK$LRLOGVERBOSE = "1" we get to have a detailed log file and see
the message "Recognised license" when it tries to connect and it's 
allowed in.

This PC has had a license at some point.  We have revoked it, deleted
the PWLICLM.DAT file on it, restarted the server, and have double-checked
that there are no server-based licenses loaded on the server.

Can anyone shed some light on this?

PATHWORK V5.0D ECO 3 Server, VAX.

Thanks,

/Mario Morin
Hull CSC - Canada
T.RTitleUserPersonal
Name		DateLines
4185.1VMSNET::S_VORESmile - Mickey's Watching!Mon Mar 03 1997 11:0718
    >Ever since PATHWORKS for Windows95 came out we were always under the
    >impression that an unlicensed PC coulc not connect to a PATHWORKS V5
    >Server.
    
    This is the case for NT (and OS/2??), and for quite a while the server
    thought that 95 was NT, hence this impression.  I can't find the note
    in which this was discussed, but it was changed (to allow 95 in) at
    least a year ago (Steve K, you remember?).
    
    The truth (and current versions do this 'right') is that a DOS PC with 
    no licensing software is able to connect as a "down-level" client -
    this includes PWv4, pwv5/5.1/6 with PWLICLMT removed, WfW and 95.
    
    I'm not sure what's going on with your clients.
     
    
    -Sjv
4185.2W95 treated same as WINCPEEDY::KENNEDYSteve KennedyMon Mar 10 1997 17:0712
    .1> (Steve K, you remember?).
    
    I can't find any discussion on this in this conference (it may have
    only been a IPMT thing), but SteveV's comments in .1 are correct.  
    
    When W95 clients first came out, the PATHWORKS file server incorrectly
    identified these clients as WNT clients (due to the dialect they
    negotiated and the way in which we looked at this). This problem was
    corrected in our source code in Feb '96 and I believe the fix was made
    available to the field in the V5.0D-ECO1 kit.
    
    \steve
4185.3moreCPEEDY::KENNEDYSteve KennedyMon Mar 10 1997 17:1928
.0> This PC has had a license at some point.  We have revoked it, deleted
.0> the PWLICLM.DAT file on it, restarted the server, and have double-checked
.0> that there are no server-based licenses loaded on the server.
    
    Did you reboot the client?  If you didn't reboot the client, the client
    may still be using a "loaded" license to connect.
    
    If the client is being let in without a license, there shouldn't be
    anything logged to the license regustrar's log file (especially not
    "regognized license"), however another place to check for info is the
    event log from ADMIN/Analyze - this may (should?) list clients which
    are allowed access without a license.
    
    Lastly, remember that the license registrar maintains an in-memory
    cache containing client's who have had their license(s) validated
    within the last 24 hours. If the file server asks the license registrar
    to validate that a client is licensed and the registrar has done that
    within 24 hours, the license registrar will not actually perform the
    license check if the client is still in cache.  To disable the cache,
    define the following logical:
    
    $ define/system  PWRK$LrNoCacheCheck  1
    
    The license registrar cache should only be disabled during testing and
    trouble shooting.
    
    \steve