Re: DHCP client - Help configuring.
- From: JF Mezei <jfmezei.spamnot@xxxxxxxxxxxx>
- Date: Sun, 07 May 2006 03:35:20 -0400
shofu_au@xxxxxxxxxxxx wrote:
DHCP configuring WE0
subnet mask : 255.255.255.0
IP address : 192.168.1.12
broadcast address: 192.168.1.255
default gateway : 192.168.1.1
The DHCP server did not pass a host name for this host to use.
Using the requested hostname "ds10" instead.
DNS lookups for the requested host name may not function.
%TCPIP-E-NAMEERROR, error processing name service request
-TCPIP-E-BINDDISABLE, BIND resolver is disabled
%TCPIP-E-NAMEERROR, error processing name service request
-TCPIP-E-INSBINDDATA, insufficient data to enable BIND
You don't need to consigure a bind server on VMS., but you need to tell
it about a bind resolver.
From the above, it appears that VMS DHCP client isn't getting DNS serverIPs. (either because the router isn't sending them, or because the DHCP
client doesn't know what to do with those fields).
Do you have a disk:[TCPIP$DCHP]CLIENT.PCY file ? It shoudl contain at least:
$ TYPE CLIENT.PCY
class_id TCPVMS
lease_desired 86400 # 24 hour lease
request routers
request host_name
request dns_servers
request dns_domain_name
(this is straight from the manual).
$set def disk:[TCPIP$DHCP]
$lib/extract=client_pcy/output=client.pcy sys$library:tcpip$templates.tlb
this will give you the above client.pcy. There are more parameters you
can add in it.
After the DHCP negotiation, you would want to :
TCPIP SHOW INTERFACE WEA0/FULL
TCPIP SHOW ROUTE
TCPIP SHOW NAME
You shoudl get something like:
$ tcpip show name
BIND Resolver Parameters
Local domain: chocolate.com
System
State: Started, Enabled
Transport: UDP
Domain: chocolate.com
Retry: 4
Timeout: 4
Servers: bike
Path: No values defined
Process
State: Enabled
Transport:
Domain:
Retry:
Timeout:
Servers:
Path:
The "Domain" is the domain that automatically gets added when you make a
request for just a node name.
(eg: asking for "pastry" results in "pastry.chocolate.com" being sent to
the DNS server.
The "servers" portion is where the DNS servers get listed. Seems that
TCPIP servres really wants a host name in there, but DHCP might be able
to put in tthe IP address. To have a "host name" in there, you must
TCPIP SET HOST node ip.address
This defines it ins the local hosts databnase so that the translation is
available to the stack before the interface is fully defined.
Note, it isn't your fault you are having problems. Many people have had
problems with the DHCP client.
(in the end, you may find it MUCH easier to defined fixed IP for your lan).
.
- Follow-Ups:
- Re: DHCP client - Help configuring.
- From: shofu_au
- Re: DHCP client - Help configuring.
- References:
- DHCP client - Help configuring.
- From: shofu_au
- Re: DHCP client - Help configuring.
- From: JF Mezei
- Re: DHCP client - Help configuring.
- From: shofu_au
- DHCP client - Help configuring.
- Prev by Date: FIBRE-SCSI V8.0 patch
- Next by Date: Re: Why HP will not market OpenVMS ,,,
- Previous by thread: Re: DHCP client - Help configuring.
- Next by thread: Re: DHCP client - Help configuring.
- Index(es):
Relevant Pages
|