[4150] in SIPB bug reports
bfinger name@babson
daemon@ATHENA.MIT.EDU (mhpower@mit.edu)
Sun Oct 10 16:25:22 1993
From: mhpower@mit.edu
To: lopes@mit.edu
Cc: bug-sipb@mit.edu
In-Reply-To: "[4143] in SIPB bug reports"
Date: Sun, 10 Oct 93 16:24:36 EDT
> I am trying to bfinger my friend at Babson College
>When I do "bfinger name@babson" it says:
>
>BABSON is the name of a group (VAXcluster) of the nodes
>Y and X.
...
>Question 1: How do I get node X
My guess is that there's currently only one node, and the staff at
Babson haven't yet updated the BITNET software to recognize that there
aren't separate nodes Y and X. For example, on the Internet,
vaxvmsy.babson.edu is an alias for vaxvmsx.babson.edu.
> and it said: No active path to Y is currently available
> I assume this means that Y does not exist ...
Right. Regardless of whether there are machines called Y and X at
Babson, these certainly aren't names registered for external BITNET
use, so I don't suspect there's any way to specify one individually.
If you want to ask the people at Babson, I'd suggest writing to
postmaster@vaxvmsx.babson.edu
> ... Then I tryed:
> bfinger name@babsonY,
I agree that it'd be more likely that a node named BABSONY would exist
than one named simply Y, but it turns out neither of these exist in
the BITNET node tables.
> bfinger name@babsonY, and I got no message back. In fact, no
> matter what I use right after the word "babson", I never get
> a message back.
This may have been a temporary network glitch or outage. Currently,
you would get a "DMTRGX304E No active path to BABSONY is currently
available" error message back for that.
Matt
