Re: Need help with DHCP Client & Name servers
- From: JF Mezei <jfmezei.spamnot@xxxxxxxxxxxxx>
- Date: Thu, 21 Dec 2006 20:47:24 -0500
Ken.and.Ann@xxxxxxxxx wrote:
Very similar to the thread "DHCP client - Help configuring.", from
The short answer:
-make your VMS machine a fixed IP machine. And forget about DHCP. That simple.
step:
DELETE/CONFIRM SYS$SYSTEM:TCPIP$*.DAT
It should delete the following files: (some of those may not exist on your system yet:
Directory SYS$COMMON:[SYSEXE]
TCPIP$CONFIGURATION.DAT;1 TCPIP$HOST.DAT;1 TCPIP$NETWORK.DAT;1
TCPIP$PROXY.DAT;1 TCPIP$ROUTE.DAT;1 TCPIP$SERVICE.DAT;1
This zaps your TCPIP configuration completely.
Choose a private IP subnet for your LAN.
Your choises are in:
10.0.0.0/8 (aka: 10.*.*.* with only first 8 bits significant)
172.16.0.0/12
192.168.0.0/16
(I think there are a couple others but those are the main IP blocks reserved for private use within a LAN).
The last one seems to be the most common for consumer routers's defaults IPs.
Your router's documentation should provide you with the default IP of your router. Lets assume for a minute that it is 192.168.0.1 for safe of discussion. a 16 bit subnet means a 255.255.0.0 network mask. (first 16 bits set to 1).
With this in mind, let say you choose 192.168.0.23 for your VMS host's primary IP interface.
You already know 2 IPs for your ISP's DNS service.
> Servers: 220.233.0.4, 220.233.0.3
With this information, you are reading to go into @SYS$MANAGER:TCPIP$CONFIG
and then configure your core environment:
domain: chocolate.com (or anything you want that makes sense)
Configure your primary interface to have
IP: 192.168.0.23 with a /16 CIRD network or 255.255.0.0 network mask )
It may also prompt you for a host name. For instance "pastry". (which will be pastry.chocolate.com as fully qualified host name) inside your LAN)
For routing, choose NO for ROUTED or GATED routing. You can then enter a default route (gateway in PC parlance), and give the ip address of your router. (192.168.0.1 in this example).
You then define the bind resolver. You can then enter the two IPs from your ISP as bind servers. It may prompt you for host names (which get defined in the hosts database to point to those IP addresses).
You should then have enough configured to have a working TCPIP stack.
Once the start has started:
@SYS$MANAGER:TCPIP$DEFINE_COMMAND defines a whole bunch of "unix" commands.
ifconfig -a (lists your IP interfaces (IP addresses).
ping <ip address>
traceroute <ip address or host name>
Some additional things you could do:
TCPIP SET HOST ROUTER/ADDRESS=192.168.0.1
This way, you can "telnet ROUTER" or "telnet router.chocolate.com" and you connect to that router.
NOte that in all of the above, you have not configured a BIND *SERVER*, only a bind resolver. The TCPIP SET NAME command can be confising because some qualifiers apply to a configured bind server while most apply to the bind resolver.
.
- Follow-Ups:
- Re: Need help with DHCP Client & Name servers
- From: John Santos
- Re: Need help with DHCP Client & Name servers
- From: JF Mezei
- Re: Need help with DHCP Client & Name servers
- References:
- Need help with DHCP Client & Name servers
- From: Ken . and . Ann
- Need help with DHCP Client & Name servers
- Prev by Date: Re: Open sourced VMS as a business concept ?
- Next by Date: Re: Need help with DHCP Client & Name servers
- Previous by thread: Need help with DHCP Client & Name servers
- Next by thread: Re: Need help with DHCP Client & Name servers
- Index(es):
Relevant Pages
|