5 replies
by rawright
by aford
by daven71
I'll give this one a shot. I too only knew of the service pack fix, but there is one other instance I know of when this happens. Not sure if this answer will help because I don't know if you upgraded the OS previously or not, but here is my stab:
If you installed RAS in Windows NT 3.51 before upgrading to Windows NT 4.0 (or higher), the
kernel-mode telephony driver that is used in Windows NT 3.51 is retained and RAS
uses non-Unimodem drivers. If another program uses the Unimodem driver and is
set answer the line automatically, that program causes TAPI 2.0 to control the
communications port. When this occurs, the communications port is not available
to the non-Unimodem version of RAS. The result is Error 633: The port is already in use or is not configured for Remote Access
dial out.
To resolve this problem, remove the non-Unimodem driver and replace it with one
supplied with Windows NT 4.0. To do so, follow theses steps:
1. In Control Panel, double-click Network.2. Click the Services tab.
3. Click Remote Access Service, and then click Properties.
4. If the type of modem listed indicates that the kernel-mode TAPI driver is
still being used [that is, it lists the type as "Modem (modem.inf)"], click
the port, and then click Remove.
5. Click Add to add the Unimodem driver (the driver supplied with Windows NT
4.0) for this COM port.
6. Click Continue and restart your computer when prompted to do so.
Again, doubt you upgraded from3.51, but I only have heard of the solution you already attempted or that the rasdial.exe terminates early causing the port to disappear if configured for dial-up. Any application other than RAS service can cause this to happen. Those are the only instances I know of... sorry. Hope you find the solution because I sympathize with your issues.
by aford
by aford
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending