setting: australia.  WinXP Pro.

intro: i am having a serious Communications problem under WinXP.  hopefully someone 
can give me some useful tips before i gouge my eyes out.


background: i have/had an external 56k acer-branded modem (Ambient is whats underneath 
the hood i think).  even though i can load the proper acer driver and have winXP 
detect the modem, etc, when i go to use a dial-up connection i get an "error 692" 
- which doesn't really mean anything except so-called hardware problems and windows 
can't talk to the modem.  BUT if i load my modem as a standard 33.6 modem, i have 
no problems dialing out, and when my ISP  is doing well i can easily get 5-6KB download/sec, 
so i know im still getting a fast connection.

current history: so, i moved to a new house, and my old ISP just couldn't make a 
high speed connection.  i thought it might be because i'm on different phone lines 
(im stuck with a provider called optus which runs, when it has the wiring
in place, everything on its own cable network).  anyways, i switched to a new isp 
and it ran well for about 6 weeks or so.  then, about 2 weeks ago, i started getting 
connection drops.  sometimes my connection wouldn't even last
30 seconds, and sometimes it would last for 15 minutes.  and, during off peak times 
i seem to get the standard smooth, no-drop connections that last for as
long as i want them to last.  this is all very expensive since you pay BY THE CALL 
in australia.  at first, i thought it was the ISP overselling (and i still do), but 
i also began to wonder if my modem could be the problem.  so, i've now
gone and bought a new external modem.  this time it's a Swann Speed Demon (australian 
brand i think) that also seems to be running Ambient under the hood.  the first time 
 I plugged it in on com1, i got the same type of error about
loading the 56k modem fine (and windows seeing it) and then not being able to make 
a connection.  so, i thought maybe it was the com port.  i switched to com2, windows 
detected the modem, loaded the drive AND IT DIALED OUT!  then i thought, sadly, that 
maybe that was the problem with the old modem, so i disconnected the new one, and 
put the old one on com2 and had windows detect
the modem and load the driver successfully, but it wouldn't dial out (error 692). 
so, i think, must be the modem after all?  BUT, i then put the Swann back on com2, 
windows detects and loads fine, but gets ERROR 692 when dialing!!!
now, i've tried to load and remove both modems on each com port several times, but 
all i get is ERROR 692 when using the proper drivers.  when i load the modem as a 
'standard 33.6 modem' it dials out fine.   i was also restarting the machine between 
each add/remove of the modems just to see if it made any difference. any thoughts 
on how to beat XP into submission and dial out properly again?  i really want to 
be convinced that it is my ISP's fault so i can continue to vent rage at them. and 
i REALLY, REALLY, REALLY DO NOT WANT TO RE-INSTALL XP over this crap.

thanks.


Alan Rubin
mrmacross@hotmail.com

Tip: Run a free scan for common Windows errors ad

re: modem installs fine but gets error 692 on dialing Saturday, January 31, 2004 at 8:41 pm Posted by Michelle (417 messages posted) do you have call waiting? if so, disable it. http://www.modemsite.com/56k/duns692.asp http://support.microsoft.com/default.aspx?scid=kb;EN-US;q314846 http://www.grasshoppernet.com/technicalsupport/errors/dun_692.html On Saturday, January 31, 2004 at 7:47 pm, alan rubin wrote: >setting: australia. WinXP Pro. > >intro: i am having a serious Communications problem under WinXP. hopefully someone >can give me some useful tips before i gouge my eyes out. > > >background: i have/had an external 56k acer-branded modem (Ambient is whats underneath >the hood i think). even though i can load the proper acer driver and have winXP >detect the modem, etc, when i go to use a dial-up connection i get an "error 692" >- which doesn't really mean anything except so-called hardware problems and windows >can't talk to the modem. BUT if i load my modem as a standard 33.6 modem, i have >no problems dialing out, and when my ISP is doing well i can easily get 5-6KB download/sec, >so i know im still getting a fast connection. > >current history: so, i moved to a new house, and my old ISP just couldn't make a >high speed connection. i thought it might be because i'm on different phone lines >(im stuck with a provider called optus which runs, when it has the wiring >in place, everything on its own cable network). anyways, i switched to a new isp >and it ran well for about 6 weeks or so. then, about 2 weeks ago, i started getting >connection drops. sometimes my connection wouldn't even last >30 seconds, and sometimes it would last for 15 minutes. and, during off peak times >i seem to get the standard smooth, no-drop connections that last for as >long as i want them to last. this is all very expensive since you pay BY THE CALL >in australia. at first, i thought it was the ISP overselling (and i still do), but >i also began to wonder if my modem could be the problem. so, i've now >gone and bought a new external modem. this time it's a Swann Speed Demon (australian >brand i think) that also seems to be running Ambient under the hood. the first time > I plugged it in on com1, i got the same type of error about >loading the 56k modem fine (and windows seeing it) and then not being able to make >a connection. so, i thought maybe it was the com port. i switched to com2, windows >detected the modem, loaded the drive AND IT DIALED OUT! then i thought, sadly, that >maybe that was the problem with the old modem, so i disconnected the new one, and >put the old one on com2 and had windows detect >the modem and load the driver successfully, but it wouldn't dial out (error 692). >so, i think, must be the modem after all? BUT, i then put the Swann back on com2, >windows detects and loads fine, but gets ERROR 692 when dialing!!! >now, i've tried to load and remove both modems on each com port several times, but >all i get is ERROR 692 when using the proper drivers. when i load the modem as a >'standard 33.6 modem' it dials out fine. i was also restarting the machine between >each add/remove of the modems just to see if it made any difference. any thoughts >on how to beat XP into submission and dial out properly again? i really want to >be convinced that it is my ISP's fault so i can continue to vent rage at them. and >i REALLY, REALLY, REALLY DO NOT WANT TO RE-INSTALL XP over this crap. > >thanks. > > >Alan Rubin >mrmacross@hotmail.com [Reply or follow-up to this message] re: modem installs fine but gets error 692 on dialing Saturday, January 31, 2004 at 9:40 pm Posted by alan rubin (3 messages posted) Nope, no call waiting or any other phone features. On Saturday, January 31, 2004 at 8:41 pm, Michelle wrote: >do you have call waiting? if so, disable it. http://www.modemsite.com/56k/duns692.asp > http://support.microsoft.com/default.aspx?scid=kb;EN-US;q314846 http://www.grasshoppernet.com/technicalsupport/errors/dun_692.html > > [Reply or follow-up to this message] re: modem installs fine but gets error 692 on dialing Monday, February 2, 2004 at 11:03 pm Posted by Baa (145 messages posted) Very simply, try a different ISP, then you'll know for sure whose end the problem is on. Almost all the major ISPs offer free trial periods. Also the 692s can be indicative of improper network settings. Get your ISP to walk you through the network settings to be sure. Good luck. On Saturday, January 31, 2004 at 7:47 pm, alan rubin wrote: >setting: australia. WinXP Pro. > >intro: i am having a serious Communications problem under WinXP. hopefully someone >can give me some useful tips before i gouge my eyes out. > > >background: i have/had an external 56k acer-branded modem (Ambient is whats underneath >the hood i think). even though i can load the proper acer driver and have winXP >detect the modem, etc, when i go to use a dial-up connection i get an "error 692" >- which doesn't really mean anything except so-called hardware problems and windows >can't talk to the modem. BUT if i load my modem as a standard 33.6 modem, i have >no problems dialing out, and when my ISP is doing well i can easily get 5-6KB download/sec, >so i know im still getting a fast connection. > >current history: so, i moved to a new house, and my old ISP just couldn't make a >high speed connection. i thought it might be because i'm on different phone lines >(im stuck with a provider called optus which runs, when it has the wiring >in place, everything on its own cable network). anyways, i switched to a new isp >and it ran well for about 6 weeks or so. then, about 2 weeks ago, i started getting >connection drops. sometimes my connection wouldn't even last >30 seconds, and sometimes it would last for 15 minutes. and, during off peak times >i seem to get the standard smooth, no-drop connections that last for as >long as i want them to last. this is all very expensive since you pay BY THE CALL >in australia. at first, i thought it was the ISP overselling (and i still do), but >i also began to wonder if my modem could be the problem. so, i've now >gone and bought a new external modem. this time it's a Swann Speed Demon (australian >brand i think) that also seems to be running Ambient under the hood. the first time > I plugged it in on com1, i got the same type of error about >loading the 56k modem fine (and windows seeing it) and then not being able to make >a connection. so, i thought maybe it was the com port. i switched to com2, windows >detected the modem, loaded the drive AND IT DIALED OUT! then i thought, sadly, that >maybe that was the problem with the old modem, so i disconnected the new one, and >put the old one on com2 and had windows detect >the modem and load the driver successfully, but it wouldn't dial out (error 692). >so, i think, must be the modem after all? BUT, i then put the Swann back on com2, >windows detects and loads fine, but gets ERROR 692 when dialing!!! >now, i've tried to load and remove both modems on each com port several times, but >all i get is ERROR 692 when using the proper drivers. when i load the modem as a >'standard 33.6 modem' it dials out fine. i was also restarting the machine between >each add/remove of the modems just to see if it made any difference. any thoughts >on how to beat XP into submission and dial out properly again? i really want to >be convinced that it is my ISP's fault so i can continue to vent rage at them. and >i REALLY, REALLY, REALLY DO NOT WANT TO RE-INSTALL XP over this crap. > >thanks. > > >Alan Rubin >mrmacross@hotmail.com [Reply or follow-up to this message] re: modem installs fine but gets error 692 on dialing Tuesday, February 3, 2004 at 10:11 pm Posted by alan rubin (3 messages posted) If it doesn't even get to dial out, how could it be improper network settings causing the 692 error? Thanks so far, Alan Rubin mrmacross@hotmail.com On Monday, February 2, 2004 at 11:03 pm, Baa wrote: >Very simply, try a different ISP, then you'll know for sure whose end the problem >is on. Almost all the major ISPs offer free trial periods. Also the 692s can be >indicative of improper network settings. Get your ISP to walk you through the network >settings to be sure. Good luck. > > [Reply or follow-up to this message] re: modem installs fine but gets error 692 on dialing Tuesday, February 3, 2004 at 10:38 pm Posted by Baa (145 messages posted) You'd have to ask Microsoft that question. On Tuesday, February 3, 2004 at 10:11 pm, alan rubin wrote: >If it doesn't even get to dial out, how could it be improper network settings causing >the 692 error? > >Thanks so far, > >Alan Rubin >mrmacross@hotmail.com > > [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum