| The #1 reason I've found for the error I'm a Tier I tech for SBC/Ameritech...usually the error is caused by having more than 1 device enabled in LAN or high speed internet under the network control panel. The other quick fix, and this applies mainly to 3Com NIC's, is to set the card to half-duplex instead of auto detect. |
|
| 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.  |
|
| reply to nornradd
I had that error when I first tried to install the enternet 300 software. I called the tech help desk at SBC and the first thing they asked was what OS I was using. I told him XP and he said I couldn't use that software in XP. He walked me through how to set it up within XP and, problem fixed. I use to get that "time out trying to connect to server" error all the time in Win 98 and I wouldn't call that a windows problem. So far I haven't had any problems with the XP PPPoE (knock on wood.) I would go so far to say thats its even better and more reliable than the enternet software that my DSL came with.
--
"Do or do not, there is no try." - Yoda |
|
| reply to nornradd
also , you may want to switch it to 10baseT rather than 100. the 5360 usually doesnt' like 100. |
|
