[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

4205.0. "Win95/NT v4.0 NBT Broadcast Problem?" by VMSNET::P_NUNEZ () Thu Mar 13 1997 17:06

    
    I can't believe this is so, but so far I can't make it work:
    
    Win95 or WinNT v4.0 with TCP/IP.   I cannot get a response from any
    PATHWORKS license server in my same subnet (unless I add an entry in
    LMHOSTS.).  Tried with WINS disabled too.
    
    I've tried server versions 5.0C ECO3, v5.0D, and V5.0E.  No luck. 
    
    Where <name>=nodename, I get the following results:
    
    NBTSTAT -A <name> 		works. 
    
    NBTSTAT -A PWRK$L<name>     times out.
    
    NBTSTAT -A <cluster-alias>  works (if it's part of a cluster)
    
    SHOW ASTAT PWRK$L<name> 	works (tried from Win95 only)
    
    
    From a PATHWORKS v6 client (our IP stack), it works as expected and I
    can do SHOW ASTAT PWRK$L<name> and get a response.
    
    I ran UCX's TCPIPTRACE utility to trace incoming packets from the
    client - I do see packets come in when I do NBTSTAT -A PWRK$L<name>,
    but I see the same set of packets when I do NBTSTAT -A PWRK$L<garbage>
    (to similate what would happen if the name really didn't exist).  I
    think these packets are just the multicast messages to all license
    servers in the LAN.
    
    Is anyone able to get a license USING NETBIOS BROADCASTS over TCP/IP
    from a Win95 or WinNT v4.0 client?  Please confirm you can...
    
    Paul
    
    
T.RTitleUserPersonal
Name
DateLines
4205.1my pc received a licenseNETRIX::&quot;[email protected]&quot;Gerard van der VeenMon Mar 17 1997 10:3311
with respect to nbtstat the manual says
nbtstat - a <name> performs a netbios adapter status command
against the computer specified by <name>; as there is no computer
PWRK$Lanything there is no answer
nbtstat -A does the same thing for a valid address

when I got my portable it was preconfigured with tcpip only, and I
saw at first boot the obtention of a pathworks license........

Gerard
[Posted by WWW Notes gateway]
4205.2CPEEDY::wells.lkg.dec.com::wellsPhil WellsMon Mar 17 1997 12:138
nbtstat relies on the fact that a workstation name is the 
name that you entered spaced padded to 15 bytes and null terminated 
(16th byte).

You should be able to construct a workstation name given a PWRK$L 
name.


4205.3Other tools?VMSNET::P_NUNEZMon Mar 17 1997 13:1221
    
    RE. .-1 and .-2,
    
    So NBTSTAT -a <name> is looking for <name> with a 16th byte of 00 and
    not a 16th byte of 20 (blank)?  
    
    And if the license server hasn't registered a workstation name (16th
    byte 00), NBTSTAT -a PWRK$L<name> will never get a response?  
    
    However, if I use SHOW ASTAT and specify the name PWRK$L<name> it, by
    default, looks for server service names (that end in %x20), correct?  
    
    Can one expect SHOW ASTAT to work from a Win95 or WinNT DOS window? 
    
    If not, is there any other tool that will allow me to do a findname
    test to determine if a client (win95/WNT) is getting a response from a
    license server?
    
    Thanks,
    
    Paul
4205.4CPEEDY::wells.lkg.dec.com::wellsPhil WellsMon Mar 17 1997 17:1240
>    RE. .-1 and .-2,
>    
>    So NBTSTAT -a <name> is looking for <name> with a 16th byte of 00 and
>    not a 16th byte of 20 (blank)?  

NBTSTAT is presumably asking for a "computer name" not server name.  If the 16th 
byte equals sp then it is in server format.

>    And if the license server hasn't registered a workstation name (16th
>    byte 00), NBTSTAT -a PWRK$L<name> will never get a response?  

Correct - if there's no workstation service, then there is no workstation name.

>    However, if I use SHOW ASTAT and specify the name PWRK$L<name> it, by
>    default, looks for server service names (that end in %x20), correct?  

No, it polls directly for the name that you entered.

>    Can one expect SHOW ASTAT to work from a Win95 or WinNT DOS window? 

I've seen it work from W95 and I've seen it hang - it works for me.  I have never 
seen if work from WNT though that may be because I have never tried it.

>    If not, is there any other tool that will allow me to do a findname
>    test to determine if a client (win95/WNT) is getting a response from a
>    license server?

Can you program?  If so, look at the Netbios() API on W95/WNT.  If it's DOS, look
at int5c and format the NCB as in Win32 Netbios(), though I think the LANA stuff 
will change a bit.

Also, NBTSTAT -c looks interesting if you have access to the client.

Also, ASTAT "PWRK$Lxxxxxx   C" finds the license server on node xxxxxx on all 
lanas.  ASTAT "PWRK$Lxxxxxx   C" /LANA:0 returns an adapter status for node 
xxxxxx on LANA 0 if the license server name is registered.

The format is "PWRK$L" + upcase(node name) + spacepad(upto(15)) + 'C'