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

Conference noted::windows95

Title:	Microsoft Windows 95 ("Chicago")
Notice:	Please read topics 1 to 22 before writing anything
Moderator:	EEMELI::BACKSTROM

Created:	Sun Nov 13 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2958
Total number of notes:	19968

2894.0. "Problem with duplicated Netbios names" by MLNCSC::MISLER () Mon Apr 07 1997 10:53

Here in Italy we have an Unix Server with name build1.mln.dec.com and address
16.192.16.110

In Easynet there is another node with the same short name build1. This node is
build1.eng.pko.dec.com with address 16.118.96.40

Both nodes are registered in DNRS and seen by DNS.

From nodes with Windows 95 here in Italy we can ping and trace 
build1.mln.dec.com (the italian Unix server)

But if we try a Netbios command like net view \\build1 (which does not allows 
us to write the full name) we go on the build1 node in PKO instead of the 
nearest build1 node in MLN (we see that by the command nbtstat -c).
This happens even if we put in the lmhosts file the correct name - address
for build1 in mln.

The temporary solution to that was to disable Wins on Windows95 PC which needs
to access the build1.mln.dec.com server.

The other solution would be to change the name of one of the build1 nodes.

There are other things that we can do to avoid that?

Why Wins in Italy see the remote build1 in pko instead of the local build1
in MLN?

Why DNRS accept these registrations if they create problems?

Any other suggestions?

Did somebody else find that problem?
 
Many thanks for your help

Donatella

T.R	Title	User	Personal Name	Date	Lines
2894.1	Tried forcing different names in LMHOSTS?	SMURF::PBECK	Who put the bop in the hale-de-bop-de-bop?	`Mon Apr 07 1997 11:05`	8
	You should be able to add an entry to your LMHOSTS file with an alternate name for each of the duplicate services, e.g. 16.118.96.60 build1a 16.192.16.110 build1b and access them as \\build1a and \\build1b
2894.2	back to a flat namespace	PARZVL::ogodhcp-125-128-137.ogo.dec.com::kennedy	nuncam non paratus	`Mon Apr 07 1997 11:48`	16
	> Why DNRS accept these registrations if they create problems? DNRS was not set up to track NETbios registrations. If they had tried to register build1.eng.pko.dec.com as a DECnet node, they would not have been allowed, since build1.mln.dec.com already had the DECnet phaseIV name "BUILD1". Unfortunately NETbios names tend to proliferate across the known universe - that machine isn't even registered in a Digital resource domain, it's defaulting to the Workgroup "workgroup". You might contact either the system manager listed in DNRS or the owner listed in the description when you locate that machine through Find -> Computer. Perhaps they can be pursuaded to change the name if you're using build1 for production.
2894.3	Thanks	MLNCSC::MISLER		`Mon Apr 07 1997 16:56`	9
	Thanks for the answers. I wrote to both,the system manager indicated in DNRS and the owner indicated with find computer. But I believe that a strong message should come to the users, establishing that it is forbidden to use on PC with Windows95 names different from the standard. Thanks again Donatella
2894.4		VMSNET::S_VORE	Smile - Mickey's Watching!	`Tue Apr 08 1997 09:22`	4
	What standard? Since when have DIGITAL employees obeyed a "strong message" and from whom should it come?