| reply to nornradd
Re: The #1 reason I've found for the error I'm surprised that Wired wrote such a crappy article.
The 678 error on WinXP while running DSL is, like Net Force said, equivalent to a cannot connect error. You will find that most of those errors are caused by virtual channel lockups between the exchange and the IPSN [IP Services Node]. The lockups mostly occur when there's an upstream buffer overflow [ie. you are hosting a Q3 server on a 64/128 uplink]. The only solution is to reset or rebuild the channel. The former will keep your existing PVC ID and the latter will create a new one.
Sure, there will be instances when this error is PC based and can be solved by a simple connection profile recreation or a reinstall of the NIC. BTW, check your MTU settings especially if you're a gamer.
To those of you running routers, have you ever seen a router's connection status as 'Trying'? It will either be authentication related or channel related. There's not much that can go wrong with a router based DSL connection.
My 2 cents.  |
