home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!mccall!cmu-tek-newsgate!list
- Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
- Subject: Name resolver difficulties with CMUTEK
- Message-ID: <009657BC.CBEA5A80.7269@talvax.physics.mcmaster.ca>
- From: system@talvax.physics.mcmaster.ca
- Date: Tue, 22 Dec 1992 20:04:49 EST
- Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
- Organization: The Internet
- Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
- Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu
- Lines: 24
-
- Hi,
-
- I'm running CMUTEK 6.6-5 with MX 3.1c on VMS 5.4-2 on a MicroVAX 3100.
- Normally the name resolver works fine. Once in a while (and somewhat
- spuriously) if I try to resolve a name which I know doesn't exist,
- eg by misspelling part of the node name, I get back an error "maximum
- referral limit exceeded" and then the UDP port for the name resolver
- closes itself. I can do an IPNCP NAMRES START to get things working
- again, but the name resolver seems even more fragile after that and
- may cease to function after the next bad name. The process named
- NAMRES is still around even if the name resolver itself no longer
- seems to work.
-
- So far the only pattern I've been able to establish is that the re-
- solver works for three to five days after an @IP_STARTUP with a clean
- message queue, then craps out. If I clear the message queue and do
- a NAMRES START, it may crash on the next bad name. If I do another
- @IP_STARTUP, it's good for another few days.
-
- Any suggestions? I've set it up by the book with the suggested values
- for SYSGEN parameters and everything else is default.
-
- Cheers....G. Hackman, system@talvax.physics.mcmaster.ca
-
-