connection troubles
Roy Susuico (Symantec)
Thank you for using our online discussion groups.
On 28 Sep 1998 21:01:56 GMT, Chuck Sims wrote:
>NT 4.0 Server w/SP3
> Modem USR Sportster 28.8-33.6
>NT 4.0 Workstation w/SP3
> Modem USR Sportster 56k
>
>
>Currently I'm trying trying to connect an NT workstation to an NT
>server using pcAnywhere 8.0. I have disabled the RAS service after
>reading about the problems trying to use RAS and pcAnywhere. The
>server is a host and workstation the remote. The server is not
>picking up when dialing in. All it does is ring. Any help is
>appreciated from tech support or other people who've run into this
>problem.
The issue should be corrected by applying the latest update for
pcANYWHERE32 version 8.0, and the latest .INF file for the USR 28.8-33.6
modem.
To determine if the latest update for pcANYWHERE32 version 8.0 has been
applied, start pcANYWHERE32 then select Help / About pcANYWHERE and verify
the version number. If the version is not 8.02, build 220, then run
LiveUpdate.
To run the LiveUpdate within pcANYWHERE, select Utilities / LiveUpdate.
This procedure will run automatically and update the current version to
8.02.
If you are unable to run LiveUpdate, download 802up_a.exe (4.8 megs) from
the following URL:
http://www.symantec.com/techsupp/files/pca/pcanywhere32_for_windows95nt.html
The following Periodic Update file from our Knowledge Base describes the
fixes with 8.02:
Document Title: pcANYWHERE32 8.0 Periodic Update File
URL: http://service1.symantec.com/SUPPORT/pca.nsf/docid/19971218122738
For the USR 33.6 modem to work with pcANYWHERE32, download an update file
from U.S. Robotics Inc. and install it to Windows 95/NT TAPI. Once
installed to TAPI, pcANYWHERE32 should be able to use the modem and make a
reliable connection.
* If you have a Sportster 33.6 modem, download MDMUSRSP.INF
* If you have a Sportster 33.6 VI modem, download MDMUSRVI.INF
* If you have a Voice capable 33.6 modem, download USRWAVE.INF
USR's web site is http://www.3com.com
You may have an older version of the U.S. Robotics 28.8-33.6 modem that
needs a firmware update. You can verify this by putting the modem into a
terminal mode so you can issue commands directly to the modem. With the
modem in terminal mode, issue the following command:
ATI7 [Enter]
The modem should respond with a list of information that includes a line
that reads as "Supervisor Date".
If the Supervisor date is 11/30/94, you should get a firmware update from
U.S. Robotics Inc. If your supervisor date is not 11/30/94 and you are
experiencing these symptoms, you may still need a firmware update. To
verify whether or not you need the firmware update, contact U.S. Robotics
Inc. at (847)-982-5151.
For more information on this issue, obtain the following document from our
Knowledge Base:
Document Title: U.S. Robotics Modems And Random Disconnections
URL: http://service1.symantec.com/SUPPORT/pca.nsf/docid/199661081042
If the issue continues, please obtain our modem troubleshooting document
from our Knowledge Base:
Document Title: Modem Troubleshooting with pcANYWHERE32
URL: http://service1.symantec.com/SUPPORT/pca.nsf/docid/1997128132842
Good luck and please let me know if the issue continues.
----------
Roy Susuico [Symantec Corp.]
Please continue to post your messages to the public discussion groups as
Symantec does not provide support via private email.
If you have difficulty getting a response, please read the following
article:
http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/1998527114414
For free technical support newsletters, Knowledge Base support articles,
our Online Support Genie, and FAQs, visit our pcANYWHERE support page:
http://www.symantec.com/techsupp/pca.html
Chuck Sims
After having gone through the Knowledge Base I've come upon a few
items. I read about the TAPI modem problems. I've used the modem
log file, nothing unusual there.
As I stated before the Host will not pickup when I call it. When I
come back to look at the host it says: Timeout waiting on Connection.
I've looked under the modem settings and unchecked the "Cancel the
call if not connected within XX seconds". That did not make a
difference. In pcA under security options: Login Options: limit time
to complete login is checked timeout is 3 minutes. Its only letting
it ring about 3 times before I cancel the connection.(normally it
would connect on the first ring on a working system). Unless there
is some other timeout setting hidden some where I dont see how it
comes up with this error if its only ringing and not trying to pick
up.
Here is the info from the modem log file.
09-29-1998 11:51:52.848 - U.S. Robotics 33.6K FAX INT PnP in use.
09-29-1998 11:51:52.848 - Modem type: U.S. Robotics 33.6K FAX INT PnP
09-29-1998 11:51:52.848 - Modem inf path: mdm3com.inf
09-29-1998 11:51:52.848 - Modem inf section: ModemV34in
09-29-1998 11:51:52.848 - 57600,N,8,1
09-29-1998 11:51:52.848 - 57600,N,8,1
09-29-1998 11:51:52.848 - Initializing modem.
09-29-1998 11:51:52.848 - Send: AT<cr>
09-29-1998 11:51:52.848 - Recv: AT<cr>
09-29-1998 11:51:52.978 - Recv: <cr><lf>OK<cr><lf>
09-29-1998 11:51:52.978 - Interpreted response: OK
09-29-1998 11:51:52.978 - Send: AT&F1E0Q0V1&C1&D2S0=0<cr>
09-29-1998 11:51:52.978 - Recv: AT&F1E0Q0V1&C1&D2S0=0<cr>
09-29-1998 11:51:53.108 - Recv: <cr><lf>OK<cr><lf>
09-29-1998 11:51:53.108 - Interpreted response: OK
09-29-1998 11:51:53.108 - Send:
ATS7=60S19=0L0M1&M4&K1&H1&R2&I0B0X4<cr>
09-29-1998 11:51:53.238 - Recv: <cr><lf>OK<cr><lf>
09-29-1998 11:51:53.238 - Interpreted response: OK
09-29-1998 11:51:53.238 - Waiting for a call.
09-29-1998 11:51:53.238 - Send: ATS0=0<cr>
09-29-1998 11:51:53.369 - Recv: <cr><lf>OK<cr><lf>
09-29-1998 11:51:53.369 - Interpreted response: OK
09-29-1998 11:53:13.233 - Recv: <cr><lf>RING<cr><lf>
09-29-1998 11:53:13.233 - Interpreted response: Ring
09-29-1998 11:53:13.243 - Answering the call.
09-29-1998 11:53:13.243 - Send: ATA<cr>
09-29-1998 11:54:06.510 - Recv: <cr><lf>NO CARRIER<cr><lf>
09-29-1998 11:54:06.510 - Interpreted response: No Carrier
09-29-1998 11:54:07.061 - 57600,N,8,1
09-29-1998 11:54:07.061 - Initializing modem.
09-29-1998 11:54:07.061 - Send: AT<cr>
09-29-1998 11:54:07.211 - Hanging up the modem.
09-29-1998 11:54:07.211 - Send: AT&F1<cr>
09-29-1998 11:54:07.441 - Recv: <cr><lf>OK<cr><lf>
09-29-1998 11:54:07.491 - Session Statistics:
09-29-1998 11:54:07.491 - Reads : 83 bytes
09-29-1998 11:54:07.491 - Writes: 81 bytes
09-29-1998 11:54:07.501 - Modem closed.
09-29-1998 11:55:41.236 - U.S. Robotics 33.6K FAX INT PnP in use.
09-29-1998 11:55:41.246 - Modem type: U.S. Robotics 33.6K FAX INT PnP
09-29-1998 11:55:41.246 - Modem inf path: mdm3com.inf
09-29-1998 11:55:41.246 - Modem inf section: ModemV34in
09-29-1998 11:55:41.246 - 57600,N,8,1
09-29-1998 11:55:41.246 - 57600,N,8,1
09-29-1998 11:55:41.246 - Initializing modem.
09-29-1998 11:55:41.246 - Send: AT<cr>
09-29-1998 11:55:41.246 - Recv: AT<cr>
09-29-1998 11:55:41.376 - Recv: <cr><lf>OK<cr><lf>
09-29-1998 11:55:41.376 - Interpreted response: OK
09-29-1998 11:55:41.376 - Send: AT&F1E0Q0V1&C1&D2S0=0<cr>
09-29-1998 11:55:41.376 - Recv: AT&F1E0Q0V1&C1&D2S0=0<cr>
09-29-1998 11:55:41.507 - Recv: <cr><lf>OK<cr><lf>
09-29-1998 11:55:41.507 - Interpreted response: OK
09-29-1998 11:55:41.507 - Send:
ATS7=60S19=0L0M1&M4&K1&H1&R2&I0B0X4<cr>
09-29-1998 11:55:41.637 - Recv: <cr><lf>OK<cr><lf>
09-29-1998 11:55:41.637 - Interpreted response: OK
09-29-1998 11:55:41.637 - Waiting for a call.
09-29-1998 11:55:41.637 - Send: ATS0=0<cr>
09-29-1998 11:55:41.767 - Recv: <cr><lf>OK<cr><lf>
09-29-1998 11:55:41.767 - Interpreted response: OK
Hope this is more helpful than my above.
csims
Chuck Sims
I've done everything that you said to do from your last post and it's
still not working.
also one more small thing about something you said. I hate correcting
you on something(even though it would be right for most things) The
inf for the modem is wrong. The correct Inf for the modem I am using
would be mdm3com.inf. Not the mdmusrsp.inf(this inf is for sportsters
made BEFORE 1996). The modem I am using was made in 1996(dated
12/1996).
csims