home *** CD-ROM | disk | FTP | other *** search
- X-Gateway-Source-Info: INTERNET
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!rpi!usc!news.service.uci.edu!unogate!mvb.saic.com!tgv.com!info-multinet
- Date: 14 SEP 92 18:14:35 GMT
- Newsgroups: vmsnet.networks.tcp-ip.multinet
- X-Return-path: <info-multinet-relay@TGV.COM>
- X-RFC822-From: John C Klensin <KLENSIN@INFOODS.MIT.EDU>
- From: John C Klensin <KLENSIN@INFOODS.MIT.EDU>
- Subject: Re: HELP WITH SYSADM NETWORKING PROBLEMS .....
- X-Envelope-to: INFO-MULTINET@TGV.COM
- Organization: The INFO-MULTINET Community
- Message-ID: <2C2009CB14SEP92181435@TGV.COM>
- Nntp-Posting-Host: Mvb.Saic.Com
- Lines: 49
-
- >I am an Administer for unix based machines on a local network. A professor
- >has put a vax station onto the network. I do not know much about vms administra
- >tion, any help would be great.
- >
- >I am using ucx (sp?) and can do a telnet 146.186.xx.xx, which file(s) allow
- >me to use the name of the machine instead of the numerical address? Also, if
- >I try to telnet outside our local net, I get "network unreachable". Which file
- >do I need to look at to show gateways & routes?
-
- Ken,
- Suggest you back up a step or two, take a deep breath, and understand
- what you are asking about.
- For VMS, as distinct from U**X, there are a lot of different TCP/IP
- implementations. They are *very* different. The answers to questions
- like the ones you ask are different for Multinet, CMU-TEK (the two lists
- to which you sent your inquiry), and UCX (which is what you are
- running). The products (these are not the only ones, by a long shot)
- range in quality and maintainability from "brain-damaged, pre-broken,
- and very hard to get to work and keep working" to Multinet. The latter,
- speaking as a user who was somewhat influential in the evaluation that
- finally led to MIT's switchover from unmentionable other products, is
- the absolute best of the lot (and several other lots) in both product
- quality and support.
- To oversimplify, you have two choices with this, depending on the
- value you and your university place on your time and/or on reasonable
- network interoperability:
- Choice 1: Try to run UCX and get it working properly. You will
- mostly have to rely on DEC for support. Some of the people who
- "support" it show no signs of understanding how to spell "TCP/IP", but
- adequately smart people with an adequate understanding of TCP/IP and
- enough patience have gotten it to work moderately well. You might be
- equally sucessful.
- Choice 2: Go buy something decent that comes with sufficiently good
- documentation and automatic configuration tools to eliminate the sorts
- of questions you ask (and problems you are having) at installation time.
- If "decent" is construed as "better than UCX" in this regard, there are
- several choices--it doesn't take a whole lot. If "decent" is considered
- in the more usual sense, and you put any value on your time at all, take
- some free advice and just get Multinet and put it up. It is also, if
- I recall, very cheap for VAXStations, so this might be fairly painless
- advice. If you decide to look elsewhere, make sure that you get
- something that, like Multinet, supports sufficiently good UCX emulation
- and/or interoperation that any tools that run on the VAXStation that
- expect UCX will think that they are finding it.
-
- john
- klensin@infoods.mit.edu
-
-