Summmary: Need help with DHCP Client & Name servers
- From: Ken Fairfield <ken@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 01 Jan 2007 13:29:04 -0800
First, a BIG thanks to all who replied, especially John Santos,
JF Mezei and Jeff Campbell. Various of your comments and hints
put me on the right track. :-)
To restate the problem, I was in a Catch 22 situation with
not being able to query or setup my Linksys BEFRSR41 Cable/DSL
Router because I didn't have a browser on my PWS 600au (VMS 7.3-1
and TCPIP Services V5.3-ECO-2). In addition, the manuals that
come with the Linksys don't talk about the router's default
settings. (I didn't think to go to www.linksys.com when I was on
another system to see if they had more detailed information...)
In the end, I did the following:
1) On the "virgin" VMS system, I did @TCPIP$STARTUP
and let it configure DHCP on EWA0/WE0. It also
configures Telnet and SMTP.
Having done so, I could do TCPIP SHOW INTER/FULL and
see the IP address, network and broadcast masks.
In addition, doing a TCPIP SHOW NAME and see the
IP addresses of the DNS servers for my internet
provider.
2) I did @TCPIP$SHUTDOWN, then DELETE SYS$SYSTEM:TCPIP*.DAT;
to remove all the configuration files. I also removed
the TCPIP$TELNET and TCPIP$SMTP accounts and their
directories, etc., just to have a "clean" system again.
3) Finally, and now knowing the IP addresses and masks to
use, I did @TCPIP$CONFIG. I went through all five
options under the "Core environment" section:
Domain: I made up a domain like JF suggested.
Interfaces: I did a "manual" configuration of the
primary address and masks, using
192.168.1.50 since I'd already confirmed
that the router is at 192.168.1.1 and
it defaults to DHCP addresses starting
at 192.168.1.100.
Routing: I took the default answer of NO for
ROUTED and GATED, and supplied the
router's address, 192.168.1.1, as the
default route.
BIND: I supplied the IP addresses of my
provider's name servers (and I think
I also needed to supply my made-up
domain again.
Timezone: This is/was already configured so the
configuration procedure just writes
some messages and exits.
Under the "Client components" section, I enabled
Telnet and FTP, which also enables the respective
Servers.
Having done this basic configuration, doing @TCPIP$STARTUP
got me working and able to resolve names. :-) I.e., I could
then "ftp ftp.itrc.hp.com" for example.
A few comments:
1) I had to configure EWA0_MODE at the console to Auto-Negotiate
(or whatever the text is...I don't have it in front of me). I tried
all four of the other settings, but the PWS wouldn't talk to the Linksys
unless negotiation was turned on and successful.
2) Related to (1), on a reboot, auto-negotiation doesn't always
succeed. I have somewhat better luck booting from a powered-off
state, but about 25% of the time, it fails and I have to reboot.
I think I saw some mention of this in a different thread on DHCP...
3) For reasons not relevant here, my system was at (fully patched)
VMS 7.3-1. Therefore, even though I was able to ftp the CSWB kit,
I couldn't install it (deep sigh...). I spent some time going down the
road of installing Mosaic, but the kit I pulled from FREEWARE70 also
required V7.3-2 or better... Yet another reason to keep our systems
reasonably up to date.
Thanks again, Ken
--
Ken & Ann Fairfield
Who: Ken dot and dot Ann
Where: Gmail dot Com
.
- Follow-Ups:
- Re: Summmary: Need help with DHCP Client & Name servers
- From: JF Mezei
- Re: Summmary: Need help with DHCP Client & Name servers
- Prev by Date: Re: vmware VMS ISO ?
- Next by Date: Re: Summmary: Need help with DHCP Client & Name servers
- Previous by thread: Re: DECterm special escape sequences ?
- Next by thread: Re: Summmary: Need help with DHCP Client & Name servers
- Index(es):
Relevant Pages
|
|
