Re: [TCPIP V5.4] DHCP client problem/observation
From: Peter 'EPLAN' LANGSTOEGER (peter_at_langstoeger.at)
Date: 01/30/04
- Next message: David J. Dachtera: "Re: stupid backup tricks (long)"
- Previous message: Rob Young: "Re: Rumours of (CPU) Wars"
- In reply to: JF Mezei: "Re: [TCPIP V5.4] DHCP client problem/observation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 30 Jan 2004 01:47:41 GMT
In article <4018C75A.EC332941@istop.com>, JF Mezei <jfmezei.spamnot@istop.com> writes:
>> 2) If I have a DHCP server (and I currently have) which unfortunately doesn't
>> send client hostnames (type 12 "ho and "SYS$SYSDEVICE:[TCPIP$DHCP]CLIENT.PCY"
>> contains "request hostname" of course) the DHCP client writes something like
>>
>> The DHCP server did not pass a host name for this host to use
>> Using the requested hostname <hostname> instead
>
>Are you trying to assign a fixed domain name for each machine ? If so, you
>probably have to define a group with all the common features, and then define
>individual hosts with host specific infomation (ethernet address and host name).
I do not talk about the DNS server. It is there, has its problem, but I won't
like to see VMS (here the DHCP client) to be affected by such a problem. And
as I wrote, I have no problem with the domain name, only with the host name.
>> and there it goes and all works. It seems that this happens only if there
>> is a file "SYS$SYSDEVICE:[TCPIP$DHCP]HOSTNAME." but not the file
>> "SYS$SYSDEVICE:[TCPIP$DHCP]interface.DHC" - as it is with the first boot.
>
>for me, there is a namepool.; file. It contains the root (my domain name),
>address of the server, as well as the mask used to generate the dynamic host names.
That's DHCP server management. I'm talking about the client instead...
>I am not sure what you are trying to do ?
Get most of the bugs out of VMS software ?
And this is here the right audience I guess.
>Are you wishing to have the DHCP server provide a client with a host name, or
>do you wish the DHCP server to accept whatever host name a client requests ?
I want the DHCP client to have a consistent behaviour. If I have an DHCP
server which doesn't provide a host name, I want to see the DHCP client
to use its own (and requested) host name instead. And this should happen
EVERY TIME (and not only until the interface.DHC exists).
>Do you need specific host names assigned to specific machines, or do you want
>to generate "random" DNS names ?
I use SCSNODE names for the hostnames (and the DECnet nodenames of course)
and I assign fixed IP addresses to these hostnames and I want to see the
VMS systems use these names. In the DHCP server, the hostname is assigned
to the Mac.Add, too (but it doesn't send it. Why, is another problem, but
not a VMS one) but regardless where the hostname should come from, it
ends with a VMS systems with "unknown.DOMAIN.NAME" as its name.
Currently I use fixed addresses (and not the DHCP client) just to get rid
of the "unknown" but I might end adding a DELETE *.DHC;* to the LOGIN.COM
of the DHCP client as well.
Having the DHCP client as an advantage for remote configuration of IP
addresses, subnet mask, domain (but not host) names, nameservers, gateways
timeservers and so on is totally gone with such an disadvantage.
-- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist
- Next message: David J. Dachtera: "Re: stupid backup tricks (long)"
- Previous message: Rob Young: "Re: Rumours of (CPU) Wars"
- In reply to: JF Mezei: "Re: [TCPIP V5.4] DHCP client problem/observation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
