It would seem that admitting this (on 3COM's part) would be financially impossible. There would be an outcry for replacement cards, especially those who are under support and guaranteed contracts. You do have a good point. Mine have never had the hanging issues at all. However, I have seen the lost connection issues. I am personally concerned about that. I also do not upgrade my code until I see how it effects everyone else first. My rule is: I can keep them with OK services. I can't with experimenting with services that don't work at all. BTW, my actual connected users get OK service from the 3COM chasis. However, I do know about the support failures. Coming from LT, with ausome support, I am missing them already. Fortunite for me, LT owns my support contract through my retailer. Jason -----Original Message----- From: owner-usr-tc@lists.xmission.com [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Scot Desort Sent: Sunday, October 17, 1999 5:14 PM To: usr-tc@lists.xmission.com Subject: RE: (usr-tc) ISPCon/3Com Open Meeting I have only been a 3COM customer for a few months, and I do not regret my decision, YET. Many on this list have been jilted by 3COM for a long time. It will take a lot to win these folks back. I was previously using a Microcom modem platform, and my end user connect issues have virtually been eliminated. But I am small, and new to 3COM, so my voice has little weight on this subject. And I cannot compare 3COM to Ascend or LT NAS's. I was thinking -- while the DSP and Hiper code controls almost all of the cards' functions, is it possible that the physical hardware on the DSP cards is playing a role in these problems? My cards are all less than 3 months old, and I've NEVER experienced the modem-pair hanging problem that plagues many here. I also have very, very few connect issues. Could it be the HARDWARE revisions on the DSP cards are also effecting performance and stability? Just a thought... -Scot -----Original Message----- From: owner-usr-tc@lists.xmission.com [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Jason A. Nunnelley Sent: Sunday, October 17, 1999 4:26 PM To: usr-tc@lists.xmission.com Subject: RE: (usr-tc) ISPCon/3Com Open Meeting I hear a lot of complaints about 3COM on this list. Is the general idea that 3COM should not be used? I used PM3s, with a lot of connection issues, but little management headaches. I have considered CISCO (even tried one out), but have heard the nightmare stories about connection issues. Is there a feeling that the Ascend is better? Hmmm. Why don't I dump my 3COM and go back to LT. I got excellent support there. I have never even been able to get 3COM to give me the TC Software, and I paid for the support contract. They tell me I have to prove I have a support contract every time I call. Do they just SUCK? That is the feeling I am getting from this list. Is that what you guys mean to say: "Run from 3COM, they SUCK!" Jason -----Original Message----- From: owner-usr-tc@lists.xmission.com [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Ed Sent: Saturday, October 16, 1999 4:46 PM To: usr-tc@lists.xmission.com Subject: Re: (usr-tc) ISPCon/3Com Open Meeting Again yes there is a problem with V90 on 3com. Ascend units will do V90 with a client 3com modem in cases where 3com TC won't... this is DEFINITELY a problem that has been addressed but not resolved. You would think this would concern 3com more than it does... just like all the complaints about support on this list. Oh well when everyone is switching to a different platform they may care but it will be too late. Ed ----- Original Message ----- From: Allen Marsalis <am@shreve.net> To: <usr-tc@lists.xmission.com> Sent: Saturday, October 16, 1999 6:11 PM Subject: Re: (usr-tc) ISPCon/3Com Open Meeting Same here. That's pretty much exactly how we feel about it. However we occationally find a user with a good sportster/3com modem who can't get v.90 on our TCS but can on our TNT (eval) and more importantly, can with our competitors. Users won't stay with 28.8 when they can get 48k elsewhere.. If there were no modem code issues, I'd be more than happy to send the eval back. Instead, I'll probably get an invoice... Well back when we started, we bought a superstack and it worked of course but when I found out it was half-duplex on all 10T ports, we sent it back and opted for a catalyst.. But nowadays I'm sure things are different. We outgrew the catalyst and now have a fastiron and we love it.. I realize that switches don't call for much support, but we did have some issues with the catalyst. Ciscos support as amazing and they even called back again just to make sure we were happy. 3com on the otherhand wanted to charge us for support on a 1 day old switch! I just wanted to double check to see that their was no fdx on the ports before sending it back. They could have cared less whether I returned it or not.. So I did! Allen - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.