Subject: | |
From: | |
Reply To: | |
Date: | Fri, 4 Aug 2000 07:48:51 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I just upgraded my new work computer from NT 4 to Windows 2000 and ran into
a problem with the internal modem. The modem was installed in a Gateway P2
computer, but I moved it over the new Gateway P3 system (with the Win2k). It
is an ISA internal Microcom 33.6K modem that was set as serial port COM 3.
Under Win2k, the modem would not be recognized, and I could not manually
select COM 3 through the software - Win2k was showing only COM 1 and 2. I
found nothing in the Microsoft Knowledge Base on this. Is there something
special to do with Windows 2000 to use COM 3? Gateway support knew nothing
of this, and I did not see any special settings in the C-MOS setup.
Problem 2 cam up when I decided to solve the COM 3 problem by changing the
modem to be COM 2. I disabled the internal COM 2 through C-MOS, and Win2k
detected the modem this time with no problems. However, I am trying to
enable RAS so that I can dial into my computer at work. The network
"incoming connection" setup seemed to go fine, and I was able to configure
all of the settings. However, the modem does not answer any incoming calls.
Also, the dialer application acts as if there is no modem (I used this app
to test the modem).
Anybody have Windows 2000 pro set for remote access? Any suggestions as to
what I may be doing wrong? I have RAS client under Win2k on my home machine
working with no problems, it is the server end that I am having difficulties
with.
Thank you for any help.
Peter Shkabara
____________________________
[log in to unmask]
http://pesh.what.cc
The NOSPIN Group Promotions is now offering
special "Free-After-Rebate" Software specials in conjunction
with Beyond.com. We have new offers all the time!!!
http://nospin.com/promotions
|
|
|