HP3000-L Archives

August 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lars Appel <[log in to unmask]>
Reply To:
Lars Appel <[log in to unmask]>
Date:
Fri, 17 Aug 2001 17:19:49 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (55 lines)
>shell/iX> smbclient -L <sambaserver>
 ...
>c:\> net view\\servername

>I am at a loss as to what I should use in the place of <sambaserver> and
>servername.  I have tried various things, including the IP address, without
>success.
 ...
>  I am sure it is something simple, but I don't know what it is.

Jim,

I am afraid, but it is probably not "something simple"... It seems to
boil down to the horribly confusing topic of network name resolution.

Why confusing? Well, maybe because there are 3 flavours that are
originally unrelated, but can become intermixed when platforms that
run NS/3000 and or ARPA and or NetBIOS networking start with one of
the name resolution mechanisms and fall back to the others later.

NS/3000 name resolution
  basically uses the NSDIR file, and PROBE as well as PROBE PROXY
  requests. Their order is configurable in NMMGR. PROBE and PROBE
  PROXY are kind of shouting into the local network segment "can
  the machine named XYZ please respond with its address?" opposed
  to "can anybody tell me the address of machine XYZ please?".

ARPA name resolution
  basically uses a local HOSTS file or a DNS name server, which
  has a centrally maintained list of host names and IP addresses

NetBIOS name resolution
  basically uses a local LMHOSTS file or a WINS server or some
  kind of local broadcast in the style of "looking for XYZ..."

Also notice that the three different flavours of name resolution
work with totally different "name spaces", i.e. NS 3000 names have
the 3-part node.domain.organization structure, ARPA names have an
n-part host.example.domain.org structure (which can be confused
with NS names when the name uses 3 parts), and NetBIOS names live
in a flat space without the "dotted hierarchy".

Maybe some of the networking gurus can add some on-topic material ;-)

Lars.


PS: I found the first few chapters of my Samba book useful. While
it does not discuss NS/3000, it does explain the basics of NetBIOS
networking and compares it to ARPA style networking (hey, Samba is
homed in the world of Unix/Linux... they don't have NS/3000 there).

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2