Zack Kline
2006-12-02 18:45:19 UTC
Hello,
I'm an OpenVMS hobbyist who just started with both the OS and
Multinet a few days ago.
I'm running the VMS system the only way a blind person can
reasonably do it: via an emulator on top of a Windows PC, with
consequently a Windows-ish networking setup. It consists of a router,
which serves wireless connections to the rest of my house, while my PC
is hard-wired in. I've a few choices here.
I can have Multinet try to configure a DHCP address, though
whenever I do this it fails for some reason which I'm very unclear on.
Or, I can let routed, or whatever process it actually is, communicate
with my router and get my Verizon DNS server that way. This seems to
work alright. Here's the trick, though...
I'd like to run servers, such as SMTP, SSH, etc, through the
Multinet system. Possibly make this into a public access box of some
kind. I can forward ports through the router, no problem. The issue
mostly is that I don't have a domain name of my own. I use dyndns.org
to give me a fake one. I've set that fake one to the hostname in the
Multinet configuration, but still, multinet check gives me a few
warnings, as below:
%MNCHK-I-LOGVRFY, personal login command procedure does not use
'F$VERIFY(0)
%MNCHK-W-NSNLADDR, address 71.111.56.220 in DNS for local host name
zkline.dyndns.org is not an interface address
%MNCHK-I-EXTRADDR, address 192.168.0.200 in local host table does not
appear in DNS entry
%MNCHK-I-EXTRADNSADDR, address 71.111.56.220 in DNS entry does not
appear in local host table
While these mostly make sense, I wonder what to do about them?
71.111.xx.xxx is my router's external IP address. The internal one, to
which ports are redirected, is 192.168.0.200.
In closing, I'd appreciate any help in getting this configured
properly. I was told I might try setting up a small master name server
for a small domain, but not sure what that'd do...
Thanks,
Zack.
I'm an OpenVMS hobbyist who just started with both the OS and
Multinet a few days ago.
I'm running the VMS system the only way a blind person can
reasonably do it: via an emulator on top of a Windows PC, with
consequently a Windows-ish networking setup. It consists of a router,
which serves wireless connections to the rest of my house, while my PC
is hard-wired in. I've a few choices here.
I can have Multinet try to configure a DHCP address, though
whenever I do this it fails for some reason which I'm very unclear on.
Or, I can let routed, or whatever process it actually is, communicate
with my router and get my Verizon DNS server that way. This seems to
work alright. Here's the trick, though...
I'd like to run servers, such as SMTP, SSH, etc, through the
Multinet system. Possibly make this into a public access box of some
kind. I can forward ports through the router, no problem. The issue
mostly is that I don't have a domain name of my own. I use dyndns.org
to give me a fake one. I've set that fake one to the hostname in the
Multinet configuration, but still, multinet check gives me a few
warnings, as below:
%MNCHK-I-LOGVRFY, personal login command procedure does not use
'F$VERIFY(0)
%MNCHK-W-NSNLADDR, address 71.111.56.220 in DNS for local host name
zkline.dyndns.org is not an interface address
%MNCHK-I-EXTRADDR, address 192.168.0.200 in local host table does not
appear in DNS entry
%MNCHK-I-EXTRADNSADDR, address 71.111.56.220 in DNS entry does not
appear in local host table
While these mostly make sense, I wonder what to do about them?
71.111.xx.xxx is my router's external IP address. The internal one, to
which ports are redirected, is 192.168.0.200.
In closing, I'd appreciate any help in getting this configured
properly. I was told I might try setting up a small master name server
for a small domain, but not sure what that'd do...
Thanks,
Zack.