If interested with ! For your home and professional networks

[Philippe...@laposte.net]

http://vouters.dyndns.org/tima/Windows-Unix-OpenVMS-DNS-Comparing_DNS_search_order_between_operating_systems.html

This document mainly focuses onto hostnames lookup order by three different operating systems.

[Scott Dorsey]

So, I have a machine running Multinet V4.4 which I have inherited, and it
needs to have banners turned on for ssh connections. Unfortunately the docs
I have are all V4.2 or earlier, and the ones on the web are all V5.0 or later
and the early ones have no ssh and the later ones appear to be very different.

Looking at the system, I went to
multinet_specific:root:[multinet.ssh2]sshd2_config.
which should be the valid sshd configuration file. I removed the comment
from the following line:
BannerMessageFile "sys$manager:ssh_banner.txt"

And that now should turn the banners on, right? I put an appropriate
banner in the ssh_banner.txt file but nothing happens. Restarting the
server gives no error message but no banners. Rebooting does nothing.

So my suspicion is that it's either not reading that config file or else
it doesn't know what to do with the BannerMessageFile line.

If I go into multinet configure/servers and set the parameter "port 512"
on the ssh server, it doesn't move to port 512. So clearly the parameter
setting information in the V5.0 manual does not apply to V4.4, and quite
possibly other things don't either.

Any suggestions? Oh, running VMS 7.2-2 for whatever that is worth.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."

[John E. Malmberg]

The method that Microsoft Windows uses is actually more complex than it
that article and can involve accessing a WINS server, a browsing
service, and broadcasting for a response to the name.

Normally you will only see this on a company LAN with a domain
controller, not on a personal home network.

I am not motivated to look up the exact details, but this difference
caused many miss-diagnosis as to what was actually failing in the name
resolution, because they were trying to diagnose a failure of one type
of name resolution by using diagnostic tools designed for a different type.

In general Microsoft Windows programs that use the Unix socket API look
in the hosts file first, the DNS second, and then fall back to various
Microsoft name to IP resolutions.

For Microsoft Windows programs that use the Win32 API use the Microsoft
name resolutions first and if that fail, fall back to using the Unix
methods. The Microsoft name resolution order can be controlled by
system administrator, so may be different for different sites.

This is documented somewhere in a Microsoft networking configuration guide.

Most of the problems with the Microsoft name resolutions also were
traced down to a misconfiguration caused by someone who did not read
that guide. Many of the errors would result in a configuration that
would appear to work for a period of time and then shut down resolving
the incorrectly configured name.

Currently I am having to periodically restart the Microsoft DNSClient
service as it randomly stops talking to the local VMS DNS Server.

Regards,
-John
wb8...@qsl.network
Personal Opinion Only

[Steven Schweda]

> So, I have a machine running Multinet V4.4 [...]

I know nothing, but Google Groups thinks that your
question is in some unrelated thread, which is a pretty good
way to hide it from anyone who might be interested.

[Scott Dorsey]

Reposting this with the references field cleaned up (sorry abour that):

[Stephen Hoffman]

On 2013-04-22 18:21:48 +0000, Scott Dorsey said:

> So, I have a machine running Multinet V4.4 which I have inherited, and it
> needs to have banners turned on for ssh connections. Unfortunately the docs
> I have are all V4.2 or earlier, and the ones on the web are all V5.0 or later
> and the early ones have no ssh and the later ones appear to be very different.

> ...

> Any suggestions? Oh, running VMS 7.2-2 for whatever that is worth.

AFAIK, the HTML-format documentation is usually installed with
Multinet, so you may have a copy of the 4.4 manuals already installed
on that box. But if not, here's a copy of V4.4 that's accessible:
<http://deathrow.vistech.net/docs/multinet/multinet-v44/admin_guide/Ch30.htm#E47E31>


Looks like the Banner stuff wasn't documented, or there was a
documentation error. The PrintMotd toggle is probably the closest to
what you want. Try that.

I'll presume there's some reason this box is still running fossil
versions, and no, I'm not really interested in what the particular
fig-leaf might be.

And FWIW, remember to clean out the References: in the nntp posting
headers when you're using the "reply" and also cleaning out the
contents of the previous posting, or (easier) just use the "new"
feature to get a new posting. Otherwise, your posting gets threaded in
with what you replied to...


--
Pure Personal Opinion | HoffmanLabs LLC

[Stephen Hoffman]

That was a spammy-looking subject line, Phillip.

It's probably easiest to register a domain and to run DNS services on the LAN.

DNS was invented because maintaining those hosts files was a headache,
after all.

FWIW, various operating systems also only read the host file when their
(caching) DNS resolver is starting up, too. In the case of OS X
Server, there's a HUP signal you can send the mDNSResolver to ask it to
dump and reload its cache.

What to use in place of the hosts files? Well, use a DNS server, or
two. Windows Server is pretty good at DNS services, and OS X Server,
Linux, BSD and various other operating systems can all provide DNS
services. Yes, OpenVMS can certainly provide DNS services, though
involving older revisions of BIND and with a low-level
configuration-file-based user interface. While you're adding DNS
services, add in user authentication via Active Directory or Open
Directory or otherwise, and you can have single sign-on, too.

I've been using OS X Server for DNS for quite a while, and have some
detailed postings introducing DNS services in general, and on the OS X
Server platform.

Running a DNS server on a Mac Mini, a PC Engines board, or a plug
computer is low power and low noise, too. While DNS needs to be
continually available, a home network requires negligible processor
power and storage.

Yes, you can use a made-up domain, but for US$10 per year, or less, you
can have a real and registered domain. Or use a subdomain of a domain
you've already registered. Just do avoid using .local or any domain
you didn't register. And FWIW, .private is not among the RFC or
ICANN-reserved domains.

[Bob Koehler]

In article <kl3v3s$5kc$1...@panix2.panix.com>, klu...@panix.com (Scott Dorsey) writes:
>
> If I go into multinet configure/servers and set the parameter "port 512"
> on the ssh server, it doesn't move to port 512. So clearly the parameter
> setting information in the V5.0 manual does not apply to V4.4, and quite
> possibly other things don't either.
>
> Any suggestions? Oh, running VMS 7.2-2 for whatever that is worth.

What is the file protection on the message?

[Scott Dorsey]

World has read permssion.

[Paul Sture]

In article <kl3v3s$5kc$1...@panix2.panix.com>,

klu...@panix.com (Scott Dorsey) wrote:

> If I go into multinet configure/servers and set the parameter "port 512"
> on the ssh server, it doesn't move to port 512. So clearly the parameter
> setting information in the V5.0 manual does not apply to V4.4, and quite
> possibly other things don't either.
>
> Any suggestions? Oh, running VMS 7.2-2 for whatever that is worth.

It's been a long time since I worked with Multinet.

Does stopping and restarting the ssh service do the trick?

--
Paul Sture