HP3000-L Archives

January 2003, Week 2

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:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Thu, 9 Jan 2003 10:45:27 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (117 lines)
Northern Credit Bureaus Inc wrote:
> There are tons of messages regarding:
> $ smbclient -L S969KS
>
> Added interface ip=192.168.1.8 bcast=192.168.1.255 nmask=255.255.255.0
>
> Session request failed (0,0) with myname=S969KS destname=S969KS
>
> Unspecified error 0x0
>
> Your server software is being unfriendly

IIRC, this is due to DNS issues.

> *****************************************************************************************
> Here is my configuration:
>
> MPEIX:
> RELEASE: C.60.00 MPE/iX HP31900 C.16.01 USER VERSION: C.60.02
>
> sh> uname -n  -->> S969KS
> NETTOOL.NET.SYS --> NAMEADDR -->CACHE --> NAME -->>  S969KS.JET.ROYAL In cache.192.168.1.8
>
> *********************************************************************
>
> After reading all I could find on the net and newsgroup, here is what I concluded:
>
> RESLVCNF.NET.SYS  overtakes HOSTS.NET.SYS, so I renamed HOSTS to HOSTS1
>
> Apparently when you do an nslookup it looks at the file
>
> :
>
> /BIND/PUB/etc/named.conf

This file is used by /BIND/PUB/NAMED, which you generally don't need to run
unless you want your e3000 to be a caching DNS server.

/BIND/PUB/bin/nslookup uses /etc/resolv.conf which should be a symlink pointing
  to /SYS/NET/RESLVCNF.

> Here is the content of RESLVCNF.NET.SYS
> #resolv.conf file
> #Copy this file to RESLVCNF.NET.SYS if that file does not already exist.
> #
> #format (without the '#', of course):
> #
> domain S969KS.JET.ROYAL
> #search <path1> <path2> ... <pathn>
> nameserver 192.168.1.8
> #nameserver <secondary server's IP address>
> #nameserver <tertiary server's IP address>
> #
> #Note 1: Change the domain entry on the last line of this file to your
> # actual domain.
> #Note 2: The search entry is optional. Add one if users on this system will
> # commonly try to connect to nodes in other domains.
> #Note 3: Add one to three (typically 2 or 3) nameserver entries at the end
> # of this file. Make sure they are each an IP-address where a server
> # resides. If you have no server, do not add any nameserver entry,
> # so the resolver will not time-out trying to connect to a server
> # that does not exist; rather, it will immediately revert to the
> #
> #example (replace 'hp' with your company's name):
> #
> #search local-domain.hp.com other-domain.hp.com hp.com
> #
> domain S969KS
> nameserver 192.168.1.8
> 127.0.0.1 localhost S969KS   (I added this line as suggested on the internet)

There are several problems here.

The "domain" entry must be the portion of the fully qualified domain name NOT
including the host name.  I.e. on the jazz.external.hp.com e3000, RESLVCNF says:

domain external.hp.com

But you don't want to say "domain jet.royal" because jet.royal is an HP Probe
(?) name, not a DNS name.  RESLVCNF is for DNS naming purposes ONLY.  You need
to use your Internet DNS domain name here, not jet.royal.

If your cut/paste was accurate, you are specifying statements twice.  You must
only have a single domain statement.  You may have multiple nameserver
statements, but it doesn't make any sense to duplicate the same IP address.

Your nameserver statement is referring to the apparent IP address of your
e3000, and you are saying "yes, I am running NAMED here on my e3000 at that IP
address".  I suspect you really aren't running NAMED on the e3000, and this is
in fact generally not necessary.

Most e3000 sites' nameserver entries in RESLVCNF refer to external DNS servers
running elsewhere within their organizations, not to the e3000 itself.  If your
RESLVCNF refers to external nameservers, then you do not need to run NAMED on
the e3000.

The "127.0.0.1 localhost S969KS" is mangled information that needs to be in the
HOSTS file.  You really want at least two HOSTS entries:

127.0.0.1 localhost
192.168.1.8 s969ks

Because many Sendmail users initially get their e3000's DNS configuration wrong
too, I wrote a shell script called dnscheck
(http://jazz.external.hp.com/src/dnscheck.tar.Z) which does comprehensive
configuration checking and tells you about any problems it finds.

Untar the script to your e3000, make sure it has POSIX execute permissions, and
then run it from the shell from any non-SM user.  Correct any problems noted by
the script and rerun it until no more problems are found.
--
[log in to unmask]
Remainder of .sig suppressed to conserve expensive California electrons...

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

ATOM RSS1 RSS2