AR.MSG@forsythe.stanford.edu (Scott Gould) (05/24/89)
Hello, Hello
I've got another HP related communication problem.
I got a message from an HP employee stationed in France. He sent a
message to me through Bitnet at:
<AR.MSG@STANFORD.BITNET>
On the address header his address is:
<ptc%hpindda@hp-sde.sde.hp.com>
When I tried to reply to this account it bounced :-(
In the text of his mail he suggested I use the account name:
<ptc@hpgnd.hp.com>
When I send to this account I think it just gets lost in space.
My questions are:
How come he can send a message to me but I cannot return one??
Is Bitnet messing this up or should I try to connect up through a
Bitnet/HP address??? If so, what would a Bitnet-HP address look
like? Are there problems with the basic HP communications nodes?
Should I sell my HP stock?
Thanks (again) for the help!!
Scott
[1172] TUE 05/16/89 08:07 FROM PTC%HPINDDA@HP-SDE.SDE.HP.COM "Paul Congdon":
24 LINES
Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.01) with BSMTP id 4203; Tue,
16 May 89 11:06:52 EDT
Received: from hp-sde.sde.hp.com by CUNYVM.CUNY.EDU (IBM VM SMTP R1.1) with TCP;
Tue, 16 May 89 11:06:46 EDT
Received: from hpda.HP.COM by hp-sde ; Tue, 16 May 89 08:06:36 pdt
Received: from hpindda.HP.COM by hpda.HP.COM; Tue, 16 May 89 08:07:03 pdt
Received: by hpindda.HP.COM; Tue, 16 May 89 08:07:13 pdt
Date: Tue, 16 May 89 08:07:13 pdt
From: Paul Congdon <ptc%hpindda@hp-sde.sde.hp.com>
Full-Name: Paul Congdon
Message-Id: <8905161507.AA07005@hpindda.HP.COM>
Apparently-To: ar.msg@stanford.bitnet
Hello Scott Gould,
This is a test, this is only a test.
Regards Paul Congdon (ptc@hpgnd.hp.com)
---------------------------- Replies Sent -------------------------------------
REPLY ON 05/17/89 08:55 FROM AR.MSG "Scott Gould": YeeOww!
Paul,
Let me know if this makes it through.
Scott
To: PTC%HPINDDA@HP-SDE.SDE.HP.COM
cc: AR.MSGbrian@ucsd.EDU (Brian Kantor) (05/25/89)
I just spent some time chasing a similar problem with mail to HP going It seems that internet mail going to hpiosa.hp.com is getting rejected as being for a non-existent host. The story is this: Our root nameserver (the NIC) tells me that there are three nameservers for HP.COM 1. sde.hp.com 2. nnsc.nsf.net 3. hplabs.hp.com When querying these, sde.hp.com doesn't respond - perhaps it's broken. nnsc.nsf.net responds, and its authority records lists sd.hp.com, so I'm going to assume that it's done a zone transfer or something to serve as a secondary server. It doesn't know anything about 'hpiosa'. hplabs.hp.com responds too. The serial number of the authority records from hplabs is MUCH higher than the one I got from nnsc, and the host I'm looking for IS listed with hplabs. The short-term workaround is for my poor suffering luser to address his mail to "@hplabs.hp.com:user@hpiosa.hp.com" so that the host resolution will be done on hplabs, which presumably knows about the contents of its nameserver. The long-term solution is probably for the secondary server at nnsc to ALSO check with hplabs. It might also be a worthwhile thing to set the timeout just a bit shorter so that it checks once a day or so. Brian Kantor UCSD Office of Academic Computing Academic Network Operations Group UCSD C-010, La Jolla, CA 92093 USA brian@ucsd.edu ucsd!brian BRIAN@UCSD
ala@hpindda.HP.COM (Alyson L. Abramowitz) (05/25/89)
/ hpindda:comp.mail.misc / AR.MSG@forsythe.stanford.edu (Scott Gould) / 3:28 pm May 23, 1989 /
Hello, Hello
I've got another HP related communication problem.
On the address header his address is:
<ptc%hpindda@hp-sde.sde.hp.com>
When I tried to reply to this account it bounced :-(
My questions are:
How come he can send a message to me but I cannot return one??
Is Bitnet messing this up or should I try to connect up through a
Bitnet/HP address??? If so, what would a Bitnet-HP address look
like? Are there problems with the basic HP communications nodes?
Should I sell my HP stock?
Thanks (again) for the help!!
Scott
Don't sell your HP stock yet. I can send mail out to BITNET just
fine (and receive replies inward) so it should work. A couple of
possibilities:
1) try ptc%hpindda@hp-sde.hp.com
2) try ptc%hpindda@hplabs.hp.com
3) try ptc%hpgnd@hplabs.hp.com
I would guess that all three of those will work. Your hpgnd address
is in theory supposed to work but I've never actually seen it work
yet. Meanwhile, the syntax is: user%node@<internet host>. You can
substitute hp-sde.hp.com or hplabs.hp.com for <internet host>.cricket@hp-ses.SDE.HP.COM (Cricket Liu) (05/26/89)
It seems that internet mail going to hpiosa.hp.com is getting rejected
as being for a non-existent host.
Oh, it exists. I just peeked over the partition and it's still there.
The story is this: Our root nameserver (the NIC) tells me that there
are three nameservers for HP.COM
1. sde.hp.com
2. nnsc.nsf.net
3. hplabs.hp.com
When querying these, sde.hp.com doesn't respond - perhaps it's broken.
I just checked sde and it responds. I think there was a bit a trouble this
past weekend, but it's been worked out.
nnsc.nsf.net responds, and its authority records lists sd.hp.com, so I'm
going to assume that it's done a zone transfer or something to serve as
a secondary server. It doesn't know anything about 'hpiosa'.
It shouldn't. hpiosa is hpiosa.corp.hp.com. nnsc should have NS records
pointing to corp.hp.com's three master servers, though, one of which is
sde.hp.com.
hplabs.hp.com responds too. The serial number of the authority records
from hplabs is MUCH higher than the one I got from nnsc, and the host
I'm looking for IS listed with hplabs.
I'll check into this.
The short-term workaround is for my poor suffering luser to address his
mail to "@hplabs.hp.com:user@hpiosa.hp.com" so that the host resolution
will be done on hplabs, which presumably knows about the contents of its
nameserver.
That'll work, but it's unacceptable for the long term. Your "poor suffering
luser" should be able to send mail to user@hpiosa.corp.hp.com. I'll get on
it.
cricket
Integrated Office Systems cricket@hpiosa.corp.hp.com
Hewlett-Packard Corporate (415) 424-3723
Palo Alto, California