[Info-vax] tcpip

[FredK]

"Bob Koehler" <koehler at eisner.nospam.encompasserve.org> wrote in message 
news:6XsTfHvDa1CN at eisner.encompasserve.org...
> In article <ian406$91m$1 at usenet01.boi.hp.com>, "FredK" 
> <fred.nospam at dec.com> writes:
>>
>> Not being a TCPIP expert, just a code jockey - the response is
>> understandable and dissappointing.  I have to say that every time I setup 
>> a
>> new version of VMS at home (which I tend to do from scratch) - setting up
>> TCPIP is always a journey for me because frankly I don't really want to 
>> know
>> how TCPIP works - I just want an IP address, and have the handful of 
>> things
>> I need to work to work (like Telnet).
>
>   The person who sets up something should know how it works.
>

Only because they are forced to set it up - as opposed to having it 
semi-automatically (or automatically done).  I don't know how to install the 
ignition system on my car, I don't have to.

The key difference here IMHO is that when someone who isn't  VMS system 
manager or network guy gets a system to use at home - he is faced with the 
"*you* are the network administrator" - it isn't some guy in IT that he 
calls.  Nor is it Windows where it is all trransparent.  If he's a Linux 
geek - he already probably knows how to setup a network because he has to 
:-)  He most likely has a cable modem, wireless router, and a Windows PC. 
He needs to understand how to set things up to work with this home 
environment - a NAT environment.  He wants an IP address and Telnet 
(inbound?  outbound?).  So at minimum he needs to gather information about 
the router and gateway.  Will he use DHCP like his PC.  Routed?  Gated? 
Domain name?  BIND?  Other than making it work - he doesn't really care how 
they work.  Maybe later he will - when he wants to add email for example and 
says "POP what?".