how-to block ads
|
|
view: topics flat text |
|
Comments on news posted 2002-05-29 17:15:36: Wired news is running an article on the infamous 678 error that appears in Windows XP users running DSL connections. ..
|
 sdd75
join:2001-10-14
Maryville, TN | service engine soon Error 678 is another one of the errors that I call a 'service engine soon light'. It is roughly as descriptive in telling you what is wrong with your connection as the 'service engine soon light' in your car. The light in your car tells you something isn't working. It doesn't tell you what the something is and it doesn't tell you in what way it isn't working.
Error 678 is much the same. It basically says server not responding or no answer from server. In the case of dial up, it simply means you at least had dial tone, but beyond that you simply failed a handshake. It doesn't say why. In the case of Windows XP, it means that you failed a handshake for some reason, whether it was no sync, bad NIC, bad cable, bad provisioning, or who-knows what else. You need to service engine soon, because you didn't connect.
Other errors you will see that are just as uninformative are error 650 for PPPoA Windows 95, 98, ME. Error 721 for PPPoA Windows NT, 2000. Time out while connecting to server for 3rd party PPP software. They all mean the same thing. It's just a different program telling you in its own way you need to service engine soon. | |
| | | The REAL Problem Darn you MS haters!
It is obviously the greedy DSL companies, the shoddy software makers, the stupid ID10T end users, the failure of the Bu$h/Klinton administration(s) to educate the masses for free using taxpayer dollars, and the international terrorists who are causing all these security violations, error messages, bugs, flaws, holes, viruses, crashed systems lost data, and (ineffective) Gestapo privacy violations.
But everyone knows MS couldn't be the source of these problems even though these issues never arise with MAC, Linux, Unix, or BeOS.
You corporate rimmers need to grow up and look out for yourselves. M$ sure looks out for themselves. | |
|  uther
join:2001-12-04
Saint Louis, MO | Want to fix error 678? Check out www.anzwers.org/free/xpdsl
Click on the link that says "network setup wizard"
Read the text, follow instructions.
This was published by a DSL technician.
I fix about 75% of my Error 678 problems this way.
Enjoy.
Uther | |
| | | It is Both XP and ISP problem I am a vivid unix/linux fan, infact that is what I am posting this message on. I have a 98/xp machine also that I tried to hook my alcatel modem on. Here is the 678 problem:
The remote machine failed to respond.
Ok, this tells you nothing, tech. support freak or not. What it does tell you is that there is a problem. Specifically (esp. in my situation), WinXP PPoE was not detecting which of the two network cards held the modem. There was absolutely no traffic going between the network card and modem (you net. eng. freaks all have solid net. sniffers, try it.) If XP had a frickin way to deliver the PPPoE settings (VPI,VCI - Adapter), then we wouldn't be having this problem. Another problem is if you upgraded to XP from 98, and kept the PPPoE services > they corrupt your registry. If this is you, type "netsh interface ip reset log.txt" at your DoS cmd prompt. If this isnt you, and you have a virgin xp build, then just pray for the next release of MS pppoe, and hope that it has options. Being a lead SBC net. engineer gives me the ability to see if any traffic was even hitting the modem, which it wasnt, and with that information and the sniffers info, I found the root(?) of the problem > no traffic between the adapter and the alcatel. Even if you select 1 single network card (disable, or remove the second card) and try it, still no traffic. Read the log.txt if you tried the DOS command, you will see some bad registry values if your IP stack was corrupt. I recommend connecting via Unix PPPoE.
THE ISP PROBLEM
The ISP's added to the problem by putting the PPP layer in between you and the ethernet. Why authenticate when you got the line (virtually) drug to your frickin house? Some ppl like the added security, but why do what the OS does for you? Just a way to cope with the system that was in when DSL was being designed to be put into place, that system being of ISDN architecture, which used PPP (it was the only digital arch. to work with >> they just modified its phase quatature modulation to increase bandwidth (which is what DSL is - google it). So for the record, it is both of these ppls problems, but 678 is, for the most part MS. And I like all computers/os's (not mac's, they are just good hardware for linux ). Each OS offers its own, MS has a problem with this one, but not too many other probs exist with XP (which is the first MS os i can recommend to the linux scared users). Well, just stop the bitching and figure it out, ego's will do you no good in this cIb3rsp/\c3.
Derek
Network Security
"The lead of 7 to work with it first...."
SBC DSL
| |
| | | 3 ways to fix error 678 If you have more than one NIC card installed, take your ethernet (or cat5) cable out of one NIC card and put it in the other. reboot.....voila!!!!!Instant fix!
If you only have one nic card, try disabling your voicemail, call waiting, etc on your phone line.Then try to connect.
Powercycle your modem, which means while your computer and your DSL modem is still ON, unplug all cords from the back of your modem, leave down for 2 minutes, plug them back up, and IF your DSL modem is closer than 8-12 inches away from ANYTHING that is electrical or magnetic or if it is sitting on carpet, move it 8-12 inc. away, or put a thick book or magazine under your DSL modem if on carpet. reboot....and then it should connect. If it still does not connect, then call your OEM, because there is a misconfiguration in your XP. This is very common in XP. You usually get it when you first get your XP, and once you get it once, you shouldn't get it again!!! | |
|
| |
|
