[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

4181.0. "DOMAIN Name = PATHWORKS Alias " by VMSNET::P_NUNEZ () Fri Feb 28 1997 12:03

    
    Um, we've got a customer who has managed to name is domain and his
    PATHWORKS cluster alias the same name.  We've duplicated at the CSC
    using v5.0E.  Is this something the code/product should detect and not
    allow (although since anyone can simply edit lanman.ini to reach this
    setup, you'd have to stop it during process startup)?
    
    We used SETINI (@SYS$UPDATE:PWRK$SETINI.COM) and, at first, tried to
    change the alias name to equal the domain name - setini wouldn't let
    us (great!), but then we turned right around and were able to change
    the domain name to equal the alias name (boo!).  Should this be QAR'd? 
    
    We then started PATHWORKS (on both nodes in the cluster) and it started
    w/o apparent problems.  Also worked fine as a BDC - accounts replicated
    anyway.
    We can see that some NETBIOS names aren't getting claimed, though none
    of the listen names are missing. Our assumption then is that if we can
    determine what names are missing and what their purpose is, we can find
    where this illegal setup breaks something.  The chart below shows, on
    the left, the names when the alias name and domain name were both NBA;
    while on the right are  the names when domain=NBA and
    alias=ALFPW1_ALIAS:
    
$ diff nb4.log nbafter.log/par
-------------------------------------------------------------------------------
File PWRK$LMROOT:[LANMAN]NB4.LOG;3     |  File PWRK$LMROOT:[LANMAN]NBAFTER.LOG;
------------------- 3 ------------------------------------- 3 -----------------
NBA             x20   1 Unique Regist  |  ALFPW1CMTSERVER x20   1 Unique Regist
PWRK$LALFPW1    x4c   2 Group  Regist  |  ALFPW1_ALIAS    x20   2 Unique Regist
ALFPW1          x20   3 Unique Regist  |  PWRK$LALFPW1    x20   3 Unique Regist
ALFPW1CMTSERVER x20   5 Unique Regist  |  ALFPW1          x 0   4 Unique Regist
PWRK$LS         x47   6 Group  Regist  |  ALFPW1          x20   5 Unique Regist
PWRK$LALFPW1    x20   7 Unique Regist  |  ALFPW1_ALIAS    x 0   6 Group  Regist
^^^^^^^^^^^^^^A xfe   8 Unique Regist  |  NBA             x 0   7 Group  Regist
ALFPW1          x 0   9 Unique Regist  |  ^^^^^^^^^^^^^^A xfe   8 Unique Regist
PWRK$LALFPW1    x43  10 Unique Regist  |  PWRK$LALFPW1    x43   9 Unique Regist
                                       |  NBA             x1c  10 Group  Regist
Session status:                        |
name num 11, # sessions 5, rcv dg=6,   |  Session status:
LSN     State   Local Name      Soc    |  name num 11, # sessions 4, rcv dg=7,
0       LISTEN  ALFPW1CMTSERVER x20    |  LSN     State   Local Name      Soc
0       LISTEN  NBA             x20    |  0       LISTEN  ALFPW1          x20
0       LISTEN  ALFPW1          x20    |  0       LISTEN  PWRK$LALFPW1    x20
0       LISTEN  PWRK$LALFPW1    x20    |  0       LISTEN  ALFPW1CMTSERVER x20
                                       |  0       LISTEN  ALFPW1_ALIAS    x20
-------------------------------------------------------------------------------

    Paul
T.RTitleUserPersonal
Name
DateLines
4181.1JAMIN::WASSERJohn A. WasserMon Mar 03 1997 12:38108
From deep in the bowels of the Microsoft documentaiton:

Microsoft Windows NT 4.0 Server Resource Kit
	MS Windows NT Server 4.0 Networking Guide
		Appendix G: NetBIOS Names

  
Microsoft networking services running on a Windows NT-based computer are
identified by using NetBIOS names. NetBIOS names can be used to identify 
a unique computer or a special group of computers. NetBIOS names are 16 
characters in length and the 16th character is a special character used 
by most Microsoft networking services. Various networking service and 
group names are registered with a WINS server by direct name registration 
from WINS-enabled computers or by broadcast on the local subnet by non-WINS 
enabled computers.  The nbtstat command is a utility that you can use to 
obtain information about NetBIOS names. In the following example, the 
nbtstat -n command produced this list of registered NetBIOS names for 
user "Davemac" logged on to a computer configured as a primary domain 
controller and running under Windows NT Server with Internet Information 
Server.

Name		16TH	 Type	Description
DAVEMAC1 	<00>	UNIQUE	workstation service name
DAVEMAC1 	<20>	UNIQUE	server service name
DAVEMACD 	<00>	GROUP	domain name
DAVEMACD 	<1C>	GROUP	domain controller name
DAVEMACD 	<1B>	UNIQUE	master browser name
DAVEMAC1 	<03>	UNIQUE	messenger name
INet~Services 	<1C>	GROUP	Internet Information Server group name 
IS~DAVEMAC1....	<00>	UNIQUE	Internet Information Server unique name
DAVEMAC1+++++++	<BF>	UNIQUE	network monitor name

NetBIOS Unique Names
The following table lists the default 16th byte value appended to unique 
NetBIOS computer names by various Microsoft networking services.

Table G.1    16th Byte Character for Unique Names
  
16th Byte	Identifies 
<00>	Workstation service name. In general, this is the name that is 
	referred to as the NetBIOS computer name. 

<03>	Messenger service name used when receiving and sending messages. 
	This is the name that is registered with the WINS server as the 
	messenger service on the WINS client and is usually appended to 
	the computer name and to the name of the user currently logged 
	on to the computer.

<1B>	Domain master browser name.  This name identifies the primary 
	domain controller and indicates which clients and other browsers 
	to use to contact the domain master browser. 

<06>	RAS server service

<1F>	NetDDE service

<20>	Server service name used to provide sharepoints for file sharing.

<21>	RAS client

<BE>	Network Monitor agent

<BF>	Network Monitor utility 



NetBIOS Group Names

	The following table lists the default 16th byte character appended 
	to commonly used NetBIOS group names.

Table G.2    Default 16th Byte Character for NetBIOS Group Names
16th Byte	Identifies 

<1C>	A domain group name, which contains a list of the specific addresses 
	of computers that have registered the domain name. The domain 
	controller registers this name.  WINS treats this as a domain group, 
	where each member of the group must renew its name individually or 
	be released. The domain group is limited to 25 names. When a static 
	1C name is replicated that clashes with a dynamic 1C name on another 
	WINS server, a union of the members is added, and the record is marked 
	as static. If the record is static, members of the group do not have 
	to renew their IP addresses.

<1D>	The master browser name that is used by clients to access the master 
	browser. There is one master browser on a subnet. WINS servers return 
	a positive response to domain name registrations but do not store the 
	domain name in their databases.  If a computer sends a domain name 
	query to the WINS server, the WINS server returns a negative response. 
	If the computer that sent the domain name query is configured as h-node 
	or m-node, it will then broadcast the name query to resolve the name.
 
<1E>	A Normal group name. Browsers can broadcast to this name and listen on 
	it to elect a master browser. These broadcasts are for the local 
	subnet and should not cross routers. 

<20>	A special group name called the Internet group that is registered 
	with WINS servers to identify groups of computers for administrative 
	purposes. For example, "printersg" could be a registered group name 
	used to identify an administrative group of print servers.

_MSBROWSE_,	
	Instead of a single appended 16th character, "_MSBROWSE_," is appended 
	to a domain name and broadcast on the local subnet to announce the 
	domain to other master browsers.