Discussion Locked

RAS Error

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are running an NT Server with Small Business Server 4.5. Every day clients have trouble getting onto the internet via the proxy. If you try to dial the phone book entry on the server the following message appears: RAS Error 633: The Port is in Use or Not Configured. Microsoft Technet suggests upgrading to the latest service pack (article Q162807), but installing SP6a has yielded no results. Stopping and starting the RAS service and switching the modem on and off also makes not difference. Intask manager, nothing seems to be hogging the port (VNC is disabled). The modem is using the unimodem driver supplied with NT. The only way to get the port back is to reset the server and doing that once or twice a day is not really a solution. Any help would be greatly appreciated.

5 replies

by rawright

I ran into the same problem when I installed SBS 4.5 at work - the biggest mistake I ever made. Not knowing any better, I accepted all the default settings recommended by the installation program. As a result, Fax Service was installed and enabledto answer incoming calls. Since we had only one modem installed, it grabbed the modem and would not release it for other uses, resulting in the same error message you're getting every time a user tried to access the modem for another purpose. WhenI reconfigured the Fax service for outgoing calls only, the problem ceased.

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.

This discussion is closed to new replies.