My first job in IT, I worked for a small local ISP. The boss taught me most of what I know about how the internet and DNS works. He had some issues similar to what you're talking about where some brands of switches didn't like the traffic produced by some other networking hardware. The way he explained it was that all the networking equipment was working within the allowed limits, but some shifted the packet boundaries to one end or the other of the allowed area and the other hardware expected it at the other end and so the two pieces of hardware clashed. Don't recall the brands in question, but I am thinking one was a Cisco router and the other may have been 3Com. Anyway, I think the solution at the time was to get rid of the Cisco router and run routing on a monster server with multi-port nics in it. :-)
-----Original Message----- From: Phil Brutsche [mailto:[email protected]] Sent: Wednesday, September 22, 2010 6:08 PM To: NT System Admin Issues Subject: Re: My whole network went down! I read "they've" to mean the 3Com. 10-15 years ago 3com 3c905 10/100 PCI NICs used to have horrible problems autonegotiating with Cisco 2900XL switches, and probably other Cisco models too. I haven't seen this problem in quite a while. On 9/22/2010 4:52 PM, Webster wrote: > Is the "they've" in your last sentence referring to Cisco switches or > 3Com NICs? It looks like you are saying that Cisco switches have never > seemed trustworthy to ME2 since (whatever). -- Phil Brutsche [email protected] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
