Pecular Win2k DUN problem
This is a discussion about Pecular Win2k DUN problem in the Windows Hardware category; My Windows 2000 Pro has recently devloped a strange little DUN problem. . . . After a hard reboot, I connect to the internet flawlessly. It also disconencts flawlessly. . . . . . . . The problem comes when I try to re-connect.
My Windows 2000 Pro has recently devloped a strange little DUN problem....
After a hard reboot, I connect to the internet flawlessly. It also disconencts flawlessly........
The problem comes when I try to re-connect.
It proceeds up to the point where it says "Verifying User name and Password", then it simply stalls. After a couple mins(anywhere from 2-5), it disconnects with the following error: "Error 619: The Specified Port is not connected"
I figures out what the error means, and what Win2k says I should do to fix it, which is "reboot your computer to make sure configuration settings take effect" So i reboot, and it works fine again till i want to reconnect again without rebooting..... It'd begenning to drive me crazy!
Win2k first did this about 4 days ago.
I lived with it for 2, then formatted and reinstalled from scratch, and it was fine up until about 3 hours ago(Aug 22nd)when the problem came back up again!
Heres my hardware if it helps
Celeron 366
128mb RAM
Intel MU440EX mobo
Aztech 56k PCI winmodem(i know, yuck!)
PCI Voodoo Banshee 16mb
Matrox 10gb
Yamaha ymf740
oh ya, i even uninstalled the modem(and delted driver files) and let windows reinstall from the CD(no latest drivers.....Aztech doesnt seem to know what Windows 2000 is.....Bastards)
I also tried it with an old ISA 288 i have lying around.... so I have a feeling its windows itself being stupid, not my hardware.
Any help will be greatly appreciated.
After a hard reboot, I connect to the internet flawlessly. It also disconencts flawlessly........
The problem comes when I try to re-connect.
It proceeds up to the point where it says "Verifying User name and Password", then it simply stalls. After a couple mins(anywhere from 2-5), it disconnects with the following error: "Error 619: The Specified Port is not connected"
I figures out what the error means, and what Win2k says I should do to fix it, which is "reboot your computer to make sure configuration settings take effect" So i reboot, and it works fine again till i want to reconnect again without rebooting..... It'd begenning to drive me crazy!
Win2k first did this about 4 days ago.
I lived with it for 2, then formatted and reinstalled from scratch, and it was fine up until about 3 hours ago(Aug 22nd)when the problem came back up again!
Heres my hardware if it helps
Celeron 366
128mb RAM
Intel MU440EX mobo
Aztech 56k PCI winmodem(i know, yuck!)
PCI Voodoo Banshee 16mb
Matrox 10gb
Yamaha ymf740
oh ya, i even uninstalled the modem(and delted driver files) and let windows reinstall from the CD(no latest drivers.....Aztech doesnt seem to know what Windows 2000 is.....Bastards)
I also tried it with an old ISA 288 i have lying around.... so I have a feeling its windows itself being stupid, not my hardware.
Any help will be greatly appreciated.
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Aug 23
Aug 26
0
5 minutes
Responses to this topic
OP
Forgot to add this, if it helps any....
an excerpt from win2ks modem log
08-22-2000 22:01:19.242 - Modem type: MDP7800-U Modem
08-22-2000 22:01:19.242 - Modem inf path: mdmlt3.inf
08-22-2000 22:01:19.242 - Modem inf section: Modem_PNP_DF
08-22-2000 22:01:19.492 - Opening Modem
08-22-2000 22:01:19.502 - 115200,8,N,1, ctsfl=1, rtsctl=2
08-22-2000 22:01:19.502 - Initializing modem.
08-22-2000 22:01:19.512 - Send: AT<cr>
08-22-2000 22:01:19.533 - Recv: AT<cr>
08-22-2000 22:01:19.533 - Command Echo
08-22-2000 22:01:19.533 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.533 - Interpreted response: OK
08-22-2000 22:01:19.533 - TSP(0000): Making call
08-22-2000 22:01:19.543 - Send: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
08-22-2000 22:01:19.833 - Recv: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
08-22-2000 22:01:19.833 - Command Echo
08-22-2000 22:01:19.833 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.833 - Interpreted response: OK
08-22-2000 22:01:19.843 - Send: ATS7=60S30=0L0M1\N3%C1&K3B0B15B2N1\J1X4<cr>
08-22-2000 22:01:19.863 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.863 - Interpreted response: OK
08-22-2000 22:01:19.863 - Waiting for a call.
08-22-2000 22:01:19.873 - Send: ATS0=0<cr>
08-22-2000 22:01:19.893 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.893 - Interpreted response: OK
08-22-2000 22:01:19.893 - 115200,8,N,1, ctsfl=1, rtsctl=2
08-22-2000 22:01:19.893 - Initializing modem.
08-22-2000 22:01:19.903 - Send: AT<cr>
08-22-2000 22:01:19.923 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.923 - Interpreted response: OK
08-22-2000 22:01:19.933 - Send: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
08-22-2000 22:01:20.224 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:20.224 - Interpreted response: OK
08-22-2000 22:01:20.234 - Send: ATS7=60S30=0L0M1\N3%C1&K3B0B15B2N1\J1X4<cr>
08-22-2000 22:01:20.254 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:20.254 - Interpreted response: OK
08-22-2000 22:01:20.254 - Dialing.
08-22-2000 22:01:20.254 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING
08-22-2000 22:01:20.254 - TSP(0000): LINEEVENT: LINECALLSTATE_PROCEEDING
08-22-2000 22:01:20.264 - Send: ATDT#######<cr>
08-22-2000 22:01:46.421 - Recv: <cr><lf>CONNECT 45333 V42bis<cr><lf>
08-22-2000 22:01:46.421 - Interpreted response: Connect
08-22-2000 22:01:46.421 - Receive Connect but CD was low, Waiting for signal to go high
08-22-2000 22:01:46.441 - CD has been raised
08-22-2000 22:01:46.441 - Connection established at 45333bps.
08-22-2000 22:01:46.441 - Error-control on.
08-22-2000 22:01:46.441 - Data compression on.
08-22-2000 22:01:46.441 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
08-22-2000 22:02:16.444 - Read: Total: 42, Per/Sec: 0, Written: Total: 83, Per/Sec: 0
08-22-2000 22:02:46.938 - CD dropped--Remote modem hung up. ModemStatus=00000030
08-22-2000 22:02:46.938 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
08-22-2000 22:02:46.938 - TSP(0000): Dropping call
08-22-2000 22:02:46.938 - Hanging up the modem.
08-22-2000 22:02:46.938 - Recv: <cr><lf>NO CARRIER<cr><lf>
08-22-2000 22:02:46.948 - Interpreted response: No Carrier
08-22-2000 22:02:46.958 - Send: ATH E1<cr>
08-22-2000 22:02:47.249 - Recv: <cr><lf>OK<cr><lf>
an excerpt from win2ks modem log
08-22-2000 22:01:19.242 - Modem type: MDP7800-U Modem
08-22-2000 22:01:19.242 - Modem inf path: mdmlt3.inf
08-22-2000 22:01:19.242 - Modem inf section: Modem_PNP_DF
08-22-2000 22:01:19.492 - Opening Modem
08-22-2000 22:01:19.502 - 115200,8,N,1, ctsfl=1, rtsctl=2
08-22-2000 22:01:19.502 - Initializing modem.
08-22-2000 22:01:19.512 - Send: AT<cr>
08-22-2000 22:01:19.533 - Recv: AT<cr>
08-22-2000 22:01:19.533 - Command Echo
08-22-2000 22:01:19.533 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.533 - Interpreted response: OK
08-22-2000 22:01:19.533 - TSP(0000): Making call
08-22-2000 22:01:19.543 - Send: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
08-22-2000 22:01:19.833 - Recv: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
08-22-2000 22:01:19.833 - Command Echo
08-22-2000 22:01:19.833 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.833 - Interpreted response: OK
08-22-2000 22:01:19.843 - Send: ATS7=60S30=0L0M1\N3%C1&K3B0B15B2N1\J1X4<cr>
08-22-2000 22:01:19.863 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.863 - Interpreted response: OK
08-22-2000 22:01:19.863 - Waiting for a call.
08-22-2000 22:01:19.873 - Send: ATS0=0<cr>
08-22-2000 22:01:19.893 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.893 - Interpreted response: OK
08-22-2000 22:01:19.893 - 115200,8,N,1, ctsfl=1, rtsctl=2
08-22-2000 22:01:19.893 - Initializing modem.
08-22-2000 22:01:19.903 - Send: AT<cr>
08-22-2000 22:01:19.923 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:19.923 - Interpreted response: OK
08-22-2000 22:01:19.933 - Send: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
08-22-2000 22:01:20.224 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:20.224 - Interpreted response: OK
08-22-2000 22:01:20.234 - Send: ATS7=60S30=0L0M1\N3%C1&K3B0B15B2N1\J1X4<cr>
08-22-2000 22:01:20.254 - Recv: <cr><lf>OK<cr><lf>
08-22-2000 22:01:20.254 - Interpreted response: OK
08-22-2000 22:01:20.254 - Dialing.
08-22-2000 22:01:20.254 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING
08-22-2000 22:01:20.254 - TSP(0000): LINEEVENT: LINECALLSTATE_PROCEEDING
08-22-2000 22:01:20.264 - Send: ATDT#######<cr>
08-22-2000 22:01:46.421 - Recv: <cr><lf>CONNECT 45333 V42bis<cr><lf>
08-22-2000 22:01:46.421 - Interpreted response: Connect
08-22-2000 22:01:46.421 - Receive Connect but CD was low, Waiting for signal to go high
08-22-2000 22:01:46.441 - CD has been raised
08-22-2000 22:01:46.441 - Connection established at 45333bps.
08-22-2000 22:01:46.441 - Error-control on.
08-22-2000 22:01:46.441 - Data compression on.
08-22-2000 22:01:46.441 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
08-22-2000 22:02:16.444 - Read: Total: 42, Per/Sec: 0, Written: Total: 83, Per/Sec: 0
08-22-2000 22:02:46.938 - CD dropped--Remote modem hung up. ModemStatus=00000030
08-22-2000 22:02:46.938 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
08-22-2000 22:02:46.938 - TSP(0000): Dropping call
08-22-2000 22:02:46.938 - Hanging up the modem.
08-22-2000 22:02:46.938 - Recv: <cr><lf>NO CARRIER<cr><lf>
08-22-2000 22:02:46.948 - Interpreted response: No Carrier
08-22-2000 22:02:46.958 - Send: ATH E1<cr>
08-22-2000 22:02:47.249 - Recv: <cr><lf>OK<cr><lf>
Well after doing a quick lookup of your modem I find that it is an Lucent modem manufactured by Aztech. Are you using the latest Lucent driver version? See Lucent modems are software modems and they rely on a driver to interpret normal phone commands from the system and change them into the actual tones on the phone line. Lots of times what happens is something in this driver messes up. When that happens you normally have to just simply remove your modem from the modem control panel and reboot. Then Windows will reinstall the modem and write over the current files and reinitialize any possible support files that it may be using
Gee, I was reading this BBS to see if I could find a problem similar to mine, and there you go.
I had EXACTLY the same problem.
Now I reinstalled win2k - the prob is gone.
I was using sp1, dx8beta, IE 5.5.
My specs:Gigabyte 7-IX, 128Mb, K7 700, G400 DH 32Mb, Sblive, Diamond Supraexpress 56k external. Latest drivers and bios for everything.
Now I wonder what the problem is, it was really anoying having to reboot every time I wanted to reconnect to the internet...
I had EXACTLY the same problem.
Now I reinstalled win2k - the prob is gone.
I was using sp1, dx8beta, IE 5.5.
My specs:Gigabyte 7-IX, 128Mb, K7 700, G400 DH 32Mb, Sblive, Diamond Supraexpress 56k external. Latest drivers and bios for everything.
Now I wonder what the problem is, it was really anoying having to reboot every time I wanted to reconnect to the internet...
OP
JediBaron i wish it were that simple......
Ive tried that many times, even tried a diff PCI slot AND an ISA hardware modem.....
Neither one solved the problem.
I'm getting ready to do a full format this time, and see if that fixes it(last time i just deleted win2k and fdisk/mbr because i didnt want to loose my stuff)
Ive tried that many times, even tried a diff PCI slot AND an ISA hardware modem.....
Neither one solved the problem.
I'm getting ready to do a full format this time, and see if that fixes it(last time i just deleted win2k and fdisk/mbr because i didnt want to loose my stuff)
I don´t think it´s a modem specific problem, I have a completly diferent hardware platform and an external hardware modem and had the same problem.
Only a fresh install cured it.
Only a fresh install cured it.
