generalnetworkerror.com is dedicated to dispelling the myth — and sometimes running joke — that the network is usually the source of unknown and errant behavior in applications.
The application itself (through not accounting for likely exceptions to data issues or incomplete coding in extreme cases ) is the usual suspect when chasing down the root cause of errors that yield the infamous “General Network Error” when the app or its underlying framework have no better idea for what went wrong.
Although the network is far from fault-free, and bad network design and poor operational processes are leading contributors toward common networking issues, we explore and discuss Networking Best current Practices (NetBcP) to reduce network fingerpointing before applicaton errors come up (or to close network gaps when the finger is correctly pointed in the right direction).
This site promotes best current practices in networking through either direct involvement of networking technologies or through research in areas of interest.
The author is a Network Engineer in the trenches, specializing primararily (as will become obvious) in Cisco Systems hardware (and, honestly, a bit biased in that direction so you’ve been warned). Over 15 years in direct network engineering design/support and 25 years overall in IT.
I currently manage the network for a number of automotive web sites that provides research tools for consumers on both new and used vehicles, and dealer services such as lead generation and delivery.
The forums are vendor-agnostic, so all topics are welcomed as long as they pertain to and promote good networking practices and discussions. My current employer neither endorses nor sponsors this site, so they shall remain anonymous.
Visitors to generalnetworkerror.com come from across the globe.