3Com Impact IQ Non-connects (fwd)

MegaZone (megazone@livingston.com)
Thu, 10 Jul 1997 15:17:11 -0700 (PDT)

Once upon a time Michael Brennen shaped the electrons to say...
>I posted the 3Com low level trace last Friday (I know, it was a holiday),
>and to this list on Monday, and have heard nothing back. Is anyone
>looking at this? I just need some idea that someone in Livinston support
>is looking at this so I can pass *something* back to the clients.

This list is NOT an official support channel. Anything and everything
posted here is liable to be ignored. Do not rely on portmaster-users for
getting things to Livingston. I know I ignored your post since I didn't
have any ideas and this isn't a support channel - and I have no clue
whatsoever what any of that 3Com data means. I've never touched one. For
that matter that PM-3 debug you got is engineering level stuff. An 'isdn-d'
is probably better.

>FWIW: the 3Com Impacts were able to connect for a while. It is hard to
>say, but I think they lost the ability to connect was when I enabled OSPF
>to add another class C for subnetted ISDN LAN dialup.

The LAN routing protocol would make no difference at all to the ability
of the 3Com to connect. The only thing it MIGHT change is the ability to
route AFTER a connection is established - but it won't impact the actual
connection.

-MZ

--
Livingston Enterprises - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com
For support requests: support@livingston.com  <http://www.livingston.com/> 
Snail mail: 4464 Willow Road, Pleasanton, CA 94588