Hello folks @ 3000-l,
Re: Networking Basics, Samba, and TCP/IP
-------------------------------------------------Jim Phillips writes--
Following some off-list discussion, I'm left wondering if someone here
has, or knows where to find, a concise checklist for setting up TCP/IP
networking on the HP3000. For instance, I got stuck during Samba
set-up because my "TCP/IP networking wasn't configured properly". For
my system, this meant that I never set up a hosts file (and we didn't
have a DNS server). However, I never needed a hosts file for basic
TCP/IP networking (such as NS/VT or Telnet or ping) to work correctly.
That is, until I wanted Samba to work. :-) So, I was thinking that a
concise checklist would be a good idea. Any networking gurus want to
handle this?
-------------------------------------------------Jim Phillips writes--
I am not familiar with how Samba works so from my perspective it is
just another server which runs on top of TCP/IP and on UDP from what I
have seen. Each server "may" have different requirements on which
services or features of the NS-Transport are necessary to be enabled
and configured for correct operation. The various services required
are typically only turned on and configured as necessary on the basis
of which service is required by the client or server, so I would
disagree when you say "TCP/IP networking wasn't configured properly".
Each Server/Client such as NS/VT or Telnet or FTP or SAMBA have
NS-Transport services which "may" need to be configured in addition to
what is already enabled and configured. For many of these services it
is not possible to pre-configure them as they contain or expect
parameters which are specific to your site and your companies or
corporations network design and systems organization.
I understand from discussion with a friend who works with Samba that
it should be configured for the short form of the HP-3000 NS-Services
node name. This would be found in NMMGR at the top of the screen
after you select [OPEN Config].
On my system the name is:
Local HP 3000 node name [ALETA.ATL.HPCOM
]
and the short form of the name would be "ALETA".
After Samba is configured with this short name, then it is possible
for one or more "optional" services to be enabled to support name to
IP lookup. You might rely on the NS-Services name to IP lookup
"PROBE" if the systems which are running this server are connected to
the local network. You might wish to configure a RESLVCNF file to
point to a DNS Server which could respond to a name lookup request
with the short name configured in Samba if your organization supports
a DNS Server. You might wish to configure an entry in a HOSTS file
if your organization does not support DNS. Now with the NSSWITCH
patch you can optionally configure the entry in the HOSTS file even if
you already use DNS for name lookup request for other servers.
As per my discussion with my friend who does the Samba dance, further
documentation is available in the "netbios name resolution chapter in
the ONLINE O'Reilly book "Using Samba":
http://www.samba.org/samba/oreilly/using_samba
Further details on the NS-Transport name resolution lookup and
configuration can be found on-line at:
http://docs.cup.hp.com/
using the probe, reslvcnf & hosts keywords.
ns-services - probe
arpa-services - reslvcnf & hosts
Further details on the new nsswitch service can be found in the 3000-l
archives at:
http://raven.utc.edu/cgi-bin/WA.EXE?S1=hp3000-l
with keyword nsswitch
Further details on probe, reslvcnf and hosts can also be found in the
3000-l archives.
I hope this helps.
Regards,
James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
