Topic revisited -new user sorry

Archived from groups: microsoft.public.windowsxp.general (More info?)

I'm not real conversant with this, but have had success by disabling the
dialup modem in Device Manager. It seems that Windows just didn't want to
work with both the NIC and the Modem in one machine.

Then, when on the road, you can disable the NIC, reenable the Modem and it
should work for you.

"aarch" wrote:

> I used to connect to the internet with a connextant soft k56
> dialup modem, after i installed a cablemodem i cannot use
> the dialup connection. I get error 633 that the modem
> is in use or the configuration is wrong. Granted i do not
> need the dialup while the cable connection works but I travel and
> occasionally need DUN access. I need to use my dialup connection to the
> internet, and my isp has not been able to help me, since all seems well
> with my configuration. I get error 633 when i dialout.
> The connextant k56 modem is operational according to device manager.
> However Querying gets an error message "the port cannot be opened,
> check hardware conflicts, etc.").
> There are no device conflicts.
> I do not have any misc devices running.
> Have removed all instances of modem in safe and regular mode,
> and reinstalled also no good.
> I cant find anything that is useing the com port.
> Hyperterminal gets a "disconnected" message and will not dial. Phone
> lines are good.
>
>
> I have seen several versions of this problem in many instances on the
> web, but have seen no fixes - just frustrated owners.
>
>
> FYI - I sent my laptop in to mfg and they did a reformat (what else
> would you expect to be done). Upon returning I tried the DUN and it
> worked fine.
> After I hooked up the cable modem and connected the first time, i was
> unable to get the dial up modem to work -my friend error 633 was back.
> I can't afford to be reinstalling the os everytime I visit an area
> without wireless or cable modem access. There has to be a workaround if
> not a solution. Any suggestions.
>
>
> FYI -(the 2 MS KB docs on error 633 don't seem to apply). aarch
>
>