• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 957
  • Last Modified:

Error 678 and Accepting dial-in connections Windows XP pro

Hi there,

I'm trying unsuccessfully to setup a windows XP Pro machine to accept incoming dial up connections.

I have created an "Incoming connections" using DUN control panel and the PC accepts the connection fine, however when negotiating I get an "Error 678". The user being used is an administrator account with a secure password (usual 2k3 AD constraints)

I am trying to connect from a windows 7 laptop and I will be testing another Windows XP laptop later today.

Dialing the inbound number from a standard phone gives the usual modem negotiation tones.
Dialing an number FROM this modem works and also gets the usual negotiation sounds.

Dialing human phone from the laptop attempting to connect also succeeds and gets the usual negotiation tones.

It's unfortunately a pretty critical part of our multi-million dollar manufacturing equpment at the moment.

Windows 7 dial up networking diagnosis report can be emailed on request, its a cab file and EE won't let me upload that.

The modem installed in that PC is a new Netcomm InModem 56K V.92 (IN5699) modem and the laptop in use is built in, but also brand new.
On the host machine I have tried "netsh winsock reset" and rebooted. I can still dial out and the phone line is an analogue one so it shouldn't have anything to do with our PABX.
Tim Palmer
Tim Palmer
  • 3
  • 2
1 Solution
here the options from MS for XP :  http://support.microsoft.com/kb/892889
>>  , its a cab file and EE won't let me upload that  <<   rename it to *.txt
Hope this helpful,
****************** In case you cannot reach the site ******************
DUNS ERROR 678 & 679
678 - There is no answer.
679 - Cannot detect carrier.

All versions of Windows - This error can occur if:
You are dialing the wrong number
There is a problem at your ISP or in the telephone network
Your modem is unable to handshake with remote modem before allotted time

Use modem's speaker to listen to connection attempt: Make sure it dials, and make sure you hear remote modem answer tones.

Dial number with regular phone and make sure you hear remote modem answer tones.
Make sure correct phone # is dialed with DUNS - examine Modemlog. (If # dialed is not displayed, adding E1 to extra settings may help. Note also, you may have your telephony/connection settings such that long-distance digit is unintentionally being added to your phone number.)

If you hear your modem handshake, and 678 error appears at same time handshake sound ends, you may need to disable 56k or increase the 'Cancel Call if not connected' time in ControlPanel-> Modems-> Properties-> Connection

Tim PalmerLevel 3 Support TechnicianAuthor Commented:
chihs, thanks, I'd found that one but it wasn't relevant, as I mentioned in my troubleshooting I could make calls and receive them.

nobus, I also found that site, however the only step that was relevant was the netsh winsock reset command which I tried.

I was able to get a Windows XP laptop to make a connection to the PC this evening as mentioned, so I'm not sure what the issue with the windows 7 is, but I think it may have had to do with works PABX system and the dialing out.
I was able to ping a few LAN IPs which was a plus, I'll take it from there.

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

>>  netsh winsock reset   <<  try also the winsockxpfix - i just heard it does more :  http://www.snapfiles.com/get/winsockxpfix.html
Tim PalmerLevel 3 Support TechnicianAuthor Commented:
Thanks nobus, but it did turn out the issue was the connection through our PABX.

I've got different dial up issues now but thats for a new thread. This one just turned out to be the dialing configuration.
Tim PalmerLevel 3 Support TechnicianAuthor Commented:
Issue was PABX related.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now