Re: Trace failure indication [7:12191]

2001-07-18 Thread Gareth Hinton
ice exists the port does not. > > > > On Friday, July 13, 2001 at 09:43:11 AM, Hire. Ejay wrote: > > > > > Pardon my ignorance, but would you happen to be using unnumbered > interfaces > > > to connect theses routers? > > > > > > -E > &g

Re: Trace failure indication [7:12191]

2001-07-18 Thread Gareth Hinton
> > to connect theses routers? > > > > -E > > > > -Original Message- > > From: Joseph Higgins [mailto:[EMAIL PROTECTED]] > > Sent: Friday, July 13, 2001 1:24 AM > > To: [EMAIL PROTECTED] > > Subject: RE: Trace failure indication [7:12191] >

RE: Trace failure indication [7:12191]

2001-07-15 Thread Tony van Ree
--- > From: Joseph Higgins [mailto:[EMAIL PROTECTED]] > Sent: Friday, July 13, 2001 1:24 AM > To: [EMAIL PROTECTED] > Subject: RE: Trace failure indication [7:12191] > > > This problem shows up on any cisco router that I have tried, about 20 > routers. It appears from

RE: Trace failure indication [7:12191]

2001-07-13 Thread Hire, Ejay
Pardon my ignorance, but would you happen to be using unnumbered interfaces to connect theses routers? -E -Original Message- From: Joseph Higgins [mailto:[EMAIL PROTECTED]] Sent: Friday, July 13, 2001 1:24 AM To: [EMAIL PROTECTED] Subject: RE: Trace failure indication [7:12191] This

RE: Trace failure indication [7:12191]

2001-07-12 Thread Joseph Higgins
Even the example at http://www.cisco.com/warp/public/105/ext_ping_trace.html shows this failure but provides no explanation. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=12246&t=12191 -- FAQ, list archives, and subscription info

RE: Trace failure indication [7:12191]

2001-07-12 Thread Joseph Higgins
This problem shows up on any cisco router that I have tried, about 20 routers. It appears from a debug packet and debug icmp on the final destination router that the final destination router still has the port open while it is handling the previous trace probe. I want to know if anyone can get th

Re: Trace failure indication [7:12191]

2001-07-12 Thread Tony van Ree
Hi, I think you'll find this is quite normal. The "device exist #msecs" , "port non-existent *", "device exists #msecs" and so on. Basically the device exists but the socket you are attempting is not open. Spot on trace I'd say Just a thoought Teunis, Hobart, Tasmania Australia On Thur

Re: Trace failure indication [7:12191]

2001-07-12 Thread Patrick Ramsey
Have you checked duplex? Sometimes speed and duplex settings have a similar effect. Things seem to work properly, but you are dropping packets which slows the application down. Obviously if you have one end at 10 and the other is at 100, you will run into major issues, but sometimes autonegotia