3,840 current Google search engine results for “general network error” on site:microsoft.com.
When in doubt, Microsoft (as does everyone else) throws the network under the bus every time they characterize unknown errors as network errors (generally speaking). A vast majority of hits are SQL-related which can be expected with the number of clients talking to SQL servers over the network compared to other network resources (or should I say resources on the other end of the network).
Here are a few Microsoft KB articles helping to promote confusion and pointing the finger in another direction:
My favorite workaround in the last KB article is:
To work around this issue, ignore the error message, and then resend the message to the remote access client. The error does not recur.
Or does it?