H
Howard Hartman
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello.
I have an odd problem with a Windows 2000 server. I recently added a US
Robotics v.92 56K modem to this server and Symantec's pcAnywhere for remote
access.
When the modem was installed, it was properly detected on COM1. The drive
used was the one from the CD included with the modem. The modem is brand
new. After the modem was installed, pcAnywhere could not access it to open
a host session.
I rebooted the server and the US Robotics modem was re-detected as new
hardware. This time it was installed on COM2, even though it was not
connected to COM2.
Another reboot of the server caused another re-detect of the modem, this
time installing on COM3. In Device Manager, the modem is shown as working
properly on COM1 and COM2, but not working on COM3. If I remove any one of
these modems, Windows 2000 will re-detect on the next reboot.
I've found that pcAnywhere is still having trouble finding the installed
modem. After tinkering with Windows port settings and pcAnywhere settings,
I was able to get pcAnywhere to establish a remote session, but only once.
When the session is ended, the modem is not reset for another host session.
Rebooting the server will re-establish pcAnywhere connectivity for one
session.
Does anyone have ideas as to why Windows 2000 detected 3 modems? I believe
this problem is the root cause of why pcAnywhere is having trouble resetting
after the first session.
Thanks.
Howard
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
Comment: Digital signature guarantees authenticity
iQA/AwUBQbmsJ9/hBQ7O4WklEQIydwCff7q4Su5xKldnZPm8Df3BemJItMEAnidp
0KZH9zP6PBMT58T3+x7Z9vRx
=rNFw
-----END PGP SIGNATURE-----
Hash: SHA1
Hello.
I have an odd problem with a Windows 2000 server. I recently added a US
Robotics v.92 56K modem to this server and Symantec's pcAnywhere for remote
access.
When the modem was installed, it was properly detected on COM1. The drive
used was the one from the CD included with the modem. The modem is brand
new. After the modem was installed, pcAnywhere could not access it to open
a host session.
I rebooted the server and the US Robotics modem was re-detected as new
hardware. This time it was installed on COM2, even though it was not
connected to COM2.
Another reboot of the server caused another re-detect of the modem, this
time installing on COM3. In Device Manager, the modem is shown as working
properly on COM1 and COM2, but not working on COM3. If I remove any one of
these modems, Windows 2000 will re-detect on the next reboot.
I've found that pcAnywhere is still having trouble finding the installed
modem. After tinkering with Windows port settings and pcAnywhere settings,
I was able to get pcAnywhere to establish a remote session, but only once.
When the session is ended, the modem is not reset for another host session.
Rebooting the server will re-establish pcAnywhere connectivity for one
session.
Does anyone have ideas as to why Windows 2000 detected 3 modems? I believe
this problem is the root cause of why pcAnywhere is having trouble resetting
after the first session.
Thanks.
Howard
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
Comment: Digital signature guarantees authenticity
iQA/AwUBQbmsJ9/hBQ7O4WklEQIydwCff7q4Su5xKldnZPm8Df3BemJItMEAnidp
0KZH9zP6PBMT58T3+x7Z9vRx
=rNFw
-----END PGP SIGNATURE-----