[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 09, 2001 3:37 PM
To: hao vu; 'David Sanderson'; [EMAIL PROTECTED]
Subject: Re: PING TROUBLE
Ahh- this is a very hard thing to imagine. You are not not able to Ping the
3600 interface because you're not able to get the correct response from the
1600
uot; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, January 10, 2001 11:42 PM
Subject: RE: PING TROUBLE
Thank you, yes it was the 1602. I had them setup back to back to test
before
sending the 1602 offsite. Even though I could ping from the 3640 to the
1602(and to both from the 1602)
I have two routers, 3640 and 1602 both with T1 WIC's w/built in DSU/CSU.
They are connected back to back. The 3640 int s1/1 ip address is
12.10.2.97/29 and the 1602 is 12.10.2.98/29. I can ping from the 1602 both
12.10.2.97 and 12.10.2.98 and from the 3600 I can ping the 1602 -
12.10.2.98. But
You might want to turn on debug then do the ping again.
HTH
HV
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
David Sanderson
Sent: Tuesday, January 09, 2001 4:12 PM
To: '[EMAIL PROTECTED]'
Subject: PING TROUBLE
I have two routers, 3640 and 1602
switch, in order to return a Ping on their own interface.
Confused yet :-)
Phil
- Original Message -
From: "hao vu" [EMAIL PROTECTED]
To: "'David Sanderson'" [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2001 11:25 PM
Subject: RE: PING TROUBLE
Yo
5 matches
Mail list logo
