Re: Need help with DHCP Client & Name servers




John Santos wrote:
JF Mezei wrote:

[snip]

The Linksys router defaults to 192.168.1.1 (IIRC, or maybe

That's right, 192.168.1.1 ...

192.168.0.1). If you hard-code some other address into your Alpha
in that subnet, the Linksys should route for it, and the DHCP server
in the Linksys should notice that something on the LAN is using whatever
address you chose for your Alpha, and not try to serve it to another
client.

OK, that's interesting. I didn't try that because I didn't know what
the Linksys
might do if the port was set up for DHCP. OTOH, if there's no DHCP
request
the Linksys shouldn't care???

[...]
The Linksys uses 255.255.255.0 (/24). I think it's 192.168.1.1, but I'm
not certain.

Yes, this is what I found.

[...]
Before zapping all the config files, and re-running TCPIP$CONFIG,
did you already run it the first time? Lots of TCPIP configuration
problems seem to be from people installing it and then diving into
the various configuration stuff without first running through
TCPIP$CONFIG, which seems to set up some things that there is no
other way of initializing.

TCPIP$CONFIG is/was run the first time I did TCPIP$STARTUP, and
configured DHCP on the WE0 interface. But it doesn't configure BIND.

In particular, I think it creates the
config files JF mentions above. It also creates various VMS accounts
used by some (but not all) of the TCPIP clients and servers. I don't
think the DNS client (resolver) needs a special VMS account, but the
DNS server definitely does.

I've done a little debugging and found that even though the client.pcy
file does a "request DNS_domain" (I think), no domain is returned,
just the IP addresses of the DNS servers.


[...]
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).


Don't remember if it asks for host names. It might, but they are
definitely not needed for name resolution. In fact, it *has* to
use the IP addresses, because if it only knew the host names, it
couldn't resolve them to locate the name servers :-)

I think as JF mentioned elsewhere, I need to configure a local domain
to make BIND happy, at least, that's what I'll try next.

[...]
My Linksys doesn't talk telnet, just HTTP as far as I can tell.

Precisely, which is why I'm in this "fix". I can telnet/port=80
192.168.1.1,
but I can't do the required authentication with no browser...

Thanks to John, JF, and Steven M. Schweda (who replied privately) for
all your suggestions. I'll do some more experimentation and let you
all
know the results. If worse comes to worst. my duaghter will arrive
with her
iBook on Sunday and I'll be able to browse to the router from her
system.

Thanks again, Ken
--
Ken Fairfield

.



Relevant Pages

  • Re: Need help with DHCP Client & Name servers
    ... in the Linksys should notice that something on the LAN is using whatever ... might do if the port was set up for DHCP. ... the various configuration stuff without first running through ... used by some of the TCPIP clients and servers. ...
    (comp.os.vms)
  • Re: [SLE] DHCP-DNS question
    ... >> names from the DHCP, ... There are some DNS servers, that work with DHCP servers to maintain host ...
    (SuSE)
  • Re: networking private and public hosts questions
    ... DHCP isn't going to "help". ... you need to run NAT. ... Move all the Servers to the private side of the Firewall and start ... Controllers must point to themselves in thier DNS Setting and the ISP's DNS ...
    (microsoft.public.win2000.networking)
  • Re: Dynamic DNS, DNS Records & Scavenging
    ... There are two DHCP ... Both the servers are set to update A and PTR records for clients. ... DNS however this doesn't seem to be the case. ... DNSUpdateProxy and when i did this i saw my test laptop register its ...
    (microsoft.public.windows.server.dns)
  • Re: DHCP
    ... Open the event in event viewer, under the 2 arrows is a copy button, click it and paste it into the posting. ... "Meinolf Weber" wrote: ... I do not intend to change DNS or DHCP servers. ...
    (microsoft.public.windows.server.general)