Re-installing RAS for dial out on NT Workstation 4.0 fails
Posted on 1998-10-05
I have a serious problem with my Gateway portable NT
machine (Solo 9100XL) after trying to set it up to use for dial out purposes. It has Service Level 3 installed.
I first configured the dial out connection to cole's (our Solaris 2.6 Unix Sparc 5 machine) PPP modem connection. After having done so, or during this process, I had the Remote Access Server (RAS) process die and I had to reboot. When I rebooted, NT said it found new hardware and wanted to search for it and install the appropriate drivers. Since
NT wasn't telling me what it found, etc. I was suspicious at first and didn't let it continue. However, RAS still would not function, so after another reboot, I let NT search for and install the drivers it thought it needed (it found my PCMCIA modem on COM3 again and defaulted to the generic "Standard modem" drivers. Since I didn't have my driver
disk with me from Gateway at the time, I let it install the generic drivers.
After doing so, everything seemed to work ok. I was able to get a PPP connection to cole, etc. Since things were working, I decided to see about getting a script setup so that I didn't need to open up a terminal window and manually login to the PPP account. As I was looking at some of the sample scripts provided on the system, I remembered that I was using the generic modem driver. Since I had things working and was now trying to "tune" things up, I decided that I would remove the generic driver and install the driver specific for the modem that Gateway had supplied on a floppy disk. So, I did this. However, after that,
I no longer was able to get the RAS services to start upon bootup any longer. The event viewer mentioned RAS error number 615 in the log file. After some searching on the WEB, I found that this error means "The port was not found". Not being able to get around this problem, I decided to uninstall RAS itself (in "Network" under "services" tab)
and re-install it. After uninstalling RAS, the service startup error messages disappeared, as expected.
Now, I could re-install the modem and driver, but would always get the driver name, "Gateway 2000 XJEM3336 Telepath (Modem)", but with a #2 appended like this: "Gateway 2000 XJEM3336 Telepath (Modem) #2". Also, since I wanted to configure for dialup out, it needed to re-install RAS,
which it would do, but it could never see the modem previously installed. It would alway ask if I wanted to install a modem, regardless whether I had the modem and driver installed or not. Under all circumstances, the
RAS installation would never see the installed modem and fail to complete the installation.
So, I am currently stuck at this point in trying to get RAS re-installed and working so that I can use the machine for dial out purposes.
One thing that is strange is that the original modem driver, the one without the #2 on it, is still visible via the "Phone Dialer" program (under Programs/Accessories in the Start Menu). However, the line properties for the modem are inaccessible (not the case for the one with the #2 on it). Anyway, this application apparently "sees" the original driver entry, or what is left of it, but I cannot "see" it
under Control Panel via the "Modems" or "Telephony" programs where I would have the option to remove it.
So, I think I have a problem due to a previous modem driver not being completely uninstalled in some manner and it is keeping the RAS installation from seeing any newly installed modem drivers as well as the original one. Thus, the re-installation of RAS is failing and I can't seem to find a way around the problem.
I have seen this problem before on a desktop NT machine (which also happens to be a Gateway, but I don't think that is relevant here). In that case, we were installing Symantec's WinFax Pro package and RAS lost access to
the modem entries as well. In that case, we finally punted and completely re-installed NT as the machine was not yet in service. That is not an viable option in this situation. I have done a lot of looking around last night on the WEB (even sending a message describing the problem to a newsgroup), but didn't find anything that directly related to this.
I have run out of things to try at this point, so any suggestions would really be appreciated. I really need to have this working as soon as possible.