Error 633 trying to use dial-up.

[custer]

I have WinXP pro and when I try to use my backup dial-up connection I get Error 633: Modem in use or not configured correctly. More Info gives "some app is monitoring the port".

I don't have any Fax Monitor app or anything else running... and as far as I can see after days of trying to trace this problem.... it's a bug in XPProSP2.

This is a Lectron I56LVP-F70 and I transferred it to a Win2kPro machine to post this, to prove it works.

Any ideas? Has anyone been able to trouble shoot this 633 error successfully in XP Pro? Ty.

[bassman]

Are the drivers correct for the modem?

[custer]

I tried windows update, installing the oldest drivers I could find, installing drivers meant for a modem without a speaker from modemsite.com ..... the modem was in this box when I got it.... I don't have the original install cd.

This is more trouble than what it's worth. I wasted the whole weekend reading everything I could find cuz I wanted to solve this problem. If someone here can't point me in the right direction I'll just pull it and throw it away. It's only a 10 dollar modem anyway. Anyone have any ideas?

I'm getting the impression that winxp is seeing the software driver for this modem as an external app that's controlling the com port.

[custer]

The www.lectron.com.tw site isn't online anymore, or the netherlands site. Is this company out of business now? Anyone?

All I see now is an Agere driver for the chipset. Does anyone have a Lectron install cdrom?

[BipolarBill]

I have found that this error is common if you have an existing broadband connection. MS really messed up by not fixing this problem in a service pack yet.

My experience is that you cannot have a "backup" dial-up connection.

[custer]

Thank you, BPB. That's about the conclusion I was drawing. Even disabling the cable connection in XP still won't let the back-up even dial... nada, just that immediate Error 633. Quering the modem shows no problems and as I say, it works fine in the old Win2kPro box, which also has the cable connection, although thru a nic card, rather than thru a usb port.

I suppose I could try that, letting it connect thru the nic card, deleting the other entry for the usb and try it that way with the cable connection then disable it as in Win2kPro, but I doubt that would make any difference.

You saved me the expense of trying a modem with a controller... that's what I had planned next.

[custer]

No, it didn't work. Nothing has worked.

And it dawned on me today at work that if I give up this cable connection to go back to dial-up, I'll have to format and do a clean install of WinXP to erase traces of the cable connection.

[Rocketmech]

You mean XP keeps the connection enabled even if you "disable this device in this configuration" in Device Manager ? What if you just remove the nic and/or disable in the bios if its onboard lan ? Then run the Internet Connection Wizard to see if it will allow you to reconfig the DU modem as your connection device.

[custer]

This is a 3com cable modem [bought one instead of renting] and it will connect thru the nic or the usb port, Rm. I tried disabling both the onboard network interface controller and the usb controller. Same thing: Error 633: The modem [or other connecting device] is already in use or is not configured properly.

Clicking 'More Info' gives 'If this is a dial up connection, the COM port that the network connection attempted to use is already in use by another active network connection or another process [for example a phone line monitoring, such as a fax program] blah, blah, blah.

Ty for the reply, mate. Any other ideas? Anyone?

Added: In control panel, under Network Connections I don't have the option to delete a LAN or high-speed Internet Connection. I can only disable it.

[tantone]

I find this odd. What about notebook users on XP who have modems but use the office network as well?

Is it an issue of which was installed first, or a simultaneous usage thing?

I've never run into this, though I don't often have the need to install a modem into a PC with broadband access.

[custer]

Ty for the reply, tantone. I see your reply is more to addressing the real techies here and I thought I'd clarify. I've never tried to access the net simultaneously with the dial up and the broadband.

It's got me believing BipolarBill had it dead on. It's a bug in WinXP.

In Win2kPro, all I ever had to do was just unplug the power adapter to the cable modem and the dial up would connect, no problem.

But I'd sure like to find a way around it. I have just one monitor and it's a pain to pull all the connectors from the P4 and fire up the old AMD K6/2.

[custer]

I found it! After nearly a month of reading everything I could find thru google hits I found it!

In a command window type this:

netsh interface ip reset log.txt
[enter]

The log file:

reset SYSTEM\CurrentControlSet\Services\Netbt\Parameters \Interfaces\Tcpip_{D29A8BBF-CDA5-402C-949E-E8B4BEFF5107}\NetbiosOptions
old REG_DWORD = 2

deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters \EnableLmhosts
added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{762F533B-35BB-4625-B432-AC8DCDA74F18}\AddressType
added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{762F533B-35BB-4625-B432-AC8DCDA74F18}\DisableDynamicUpdate
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{762F533B-35BB-4625-B432-AC8DCDA74F18}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{762F533B-35BB-4625-B432-AC8DCDA74F18}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{762F533B-35BB-4625-B432-AC8DCDA74F18}\UdpAllowedPorts
old REG_MULTI_SZ =
0

added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{D29A8BBF-CDA5-402C-949E-E8B4BEFF5107}\DisableDynamicUpdate
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{D29A8BBF-CDA5-402C-949E-E8B4BEFF5107}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{D29A8BBF-CDA5-402C-949E-E8B4BEFF5107}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{D29A8BBF-CDA5-402C-949E-E8B4BEFF5107}\IpAutoconfigurationSeed
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{D29A8BBF-CDA5-402C-949E-E8B4BEFF5107}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{D29A8BBF-CDA5-402C-949E-E8B4BEFF5107}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{D29A8BBF-CDA5-402C-949E-E8B4BEFF5107}\UdpAllowedPorts
old REG_MULTI_SZ =
0

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \DontAddDefaultGatewayDefault
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \EnableIcmpRedirect
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \EnableSecurityFilters
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \SearchList
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \UseDomainNameDevolution
reset Linkage\Bind for ms_ndiswan. bad value was:
REG_MULTI_SZ =
\Device\{21EE15FF-1C2B-4B64-B683-5D5D4806F352}
\Device\{34621188-F135-46EE-A24A-70085017C93C}
\Device\{9B2ACA75-9B59-407D-875B-DE8ED52960A4}
\Device\{37D31FE3-4214-434D-A143-78A521105111}
\Device\NdisWanBh

reset Linkage\Route for ms_ndiswan. bad value was:
REG_MULTI_SZ =
"{21EE15FF-1C2B-4B64-B683-5D5D4806F352}"
"{34621188-F135-46EE-A24A-70085017C93C}"
"{9B2ACA75-9B59-407D-875B-DE8ED52960A4}"
"{37D31FE3-4214-434D-A143-78A521105111}"
"NdisWanBh"

reset Linkage\Export for ms_ndiswan. bad value was:
REG_MULTI_SZ =
\Device\NdisWan_{21EE15FF-1C2B-4B64-B683-5D5D4806F352}
\Device\NdisWan_{34621188-F135-46EE-A24A-70085017C93C}
\Device\NdisWan_{9B2ACA75-9B59-407D-875B-DE8ED52960A4}
\Device\NdisWan_{37D31FE3-4214-434D-A143-78A521105111}
\Device\NdisWan_NdisWanBh

reset Linkage\UpperBind for USB\VID_0506&PID_2922\00010370E2AA. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for PCI\VEN_10B7&DEV_9200&SUBSYS_00C61028&REV_78\4&853 7DD&0&60F0. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000. bad value was:
REG_MULTI_SZ =
PSched

added Linkage\RootDevice for SW\{EEAB7790-C514-11D1-B42B-00805FC1270E}\ASYNCMAC
reset Linkage\UpperBind for SW\{EEAB7790-C514-11D1-B42B-00805FC1270E}\ASYNCMAC. bad value was:
REG_MULTI_SZ =
PSched

added Linkage\Export for SW\{EEAB7790-C514-11D1-B42B-00805FC1270E}\ASYNCMAC
<completed>


Thank God, the quest is over. Now it works just like Win2KPro, just boot with the power adapter off, and backup dialup works.

[BipolarBill]

You mean that this command did it?

netsh interface ip reset

That's it? Where is MS when you need them?

[Ol'Tunzafun]

http://support.microsoft.com/default...b;en-us;299357

[BipolarBill]

I'm sure there was something like that in the KB, but nowhere do I see a connection between Error 633 (loss of dial-up functionality in the presence of a broadband connection) and rebuilding TCP/IP. They need to have a KB article for it.