No Response
Larry McDowall (Symantec)
>I have the following situation: I have a PC in the Netherlands
>runing pcAnywhere v8.0 on a WIN 95 OSR2 release that is acting as a
>HOST over the network using TCP/IP. The Remote is a PC running NT
>4.0 with SP3 and pcAnywhere V8.0. An over the network (TCP/IP)
>connection works fine, however, when I fire up ISDN on the HOST side
>from the remote side in order to connect to a local ISP in the
>Netherlands from the states, it appears pcAnywhere freezes. In other
>words, from the remote side I can no longer do anything, yet, on the
>HOST side the dial in on the ISDN attaches to the local ISP and the
>web browser works fine. Something appears to be blocking the
>connection between HOST and remote once the ISDN connection is made
>from the HOST via the remote. I might add the link between the
>Netherlands is a Frame Relay circuit of about 56k bandwidth. Prior
>to utilizing FR we had a dedicated leased line running 56k and this
>connection used to work. I would find it hard to believe that going
>from leased line to FR would or could casue this problem.
Hello Don,
Thank you for using our online discussion groups.
It appears that you are attempting to use pcANYWHERE32 over a WAN
TCP/IP connection to manually start the host's Dial-Up Networking
connection to an ISP via an ISDN adapter. When you do this, you loose
the remote control session.
This is true: Dial-Up Networking does not allow the computer that it
runs on to use a regular network. All network activity, including
pcANYWHERE32 that is active on it, is shut down. You will have to
reboot the host after the Internet connection is finished to regain
the regular network connectivity. Note that this is as designed by
Microsoft; there is nothing that we can do to work around this as far
as I know.
Please let us know if we can assist you with any other questions or
issues in the future.
---------------------------
Larry McDowall
pcANYWHERE Online Support
Symantec Corporation
Please continue to post your messages to the public discussion groups as Symantec does not provide support via private e-mail.
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/allservices_pca.html
---------------------------
Don Sachnoff
Based on what you said, I am not sure why this worked in the past.
Up until we moved the WAN circuit from leased line to Frame Relay
about two weeks ago we were doing this were doing this for the last
4-5 months. I also know when we switched back over to the leased
line it started working again. This would imply something is going
on over the FR circuit that is not present over the leased line.
Unfortunately, the corporate direction is to migrate all WAN circuits
to FR. I thought perhaps there was something else that could be
causing this problem.
thanks Don
Don Sachnoff
Larry McDowall (Symantec)
Hello Don,
This message appears to be a duplicate of your earlier message. Please
check there for my response to this message.
Thanks for your cooperation.
Larry McDowall (Symantec)
>Based on what you said, I am not sure why this worked in the past.
>Up until we moved the WAN circuit from leased line to Frame Relay
>about two weeks ago we were doing this were doing this for the last
>4-5 months. I also know when we switched back over to the leased
>line it started working again. This would imply something is going
>on over the FR circuit that is not present over the leased line.
>Unfortunately, the corporate direction is to migrate all WAN circuits
>to FR. I thought perhaps there was something else that could be
>causing this problem.
Hello Don,
Thanks for the additional information.
A leased line is not a network connection, but rather similar to a
direct serial connection. However, a frame relay is a network
connection. So, as described, this is no longer possible to do with
your new configuration. Most likely you will need to find an alternate
method of performing this since Dial-Up Networking cannot coexist with
a LAN or WAN.
Please let us know if we can assist you with any other questions or
issues in the future.
Don Sachnoff
That certainly explains the reason why it worked previously.
Appreciate your help on this.
thanks Don
Don Sachnoff
One other question. How would the workstation which is running WIN95
and is a node on an ethernet segment know that the data is coming off
a FR versus a leased line since both types of circuits terminate in a
router prior to the ethernet segment?
thanks Don
Larry McDowall (Symantec)
Hello again Don,
Thanks again for using our online services.
A router is only uses to send the computer data between two locations.
It does not determine what type of data is being sent, or how it is
being sent to it, or by what connection method.
pcANYWHERE32 uses a leased line as a COM port connection; there are no
network protocols involved. pcANYWHERE32 uses a frame relay's network
protocols, such as TCP/IP. This type of connection may seem the same
to a user, but the computers treat it in a much more different manner.
Don Sachnoff
Even when I was using the leased line for connection, pcAnywhere was
still set up using TCP/IP as the protocol. Yes, you are correct the
router just moves the packets from point a to point b. However, I
guess I am still confused as to why pcAnywhere works off a leased
line but not off a FR circuit even with TCP/IP as the protocol
defined in pcAnywhere. The IP packets should be the same regardless
of whether you are using FR or leased. In addition, leased may be
considered a "serial" connection, however, the connection to the node
is still 10BT using TCP/IP.
lost
Don
Larry McDowall (Symantec)
Hello Don,
I apologize for any continued confusion on this.
I was under the impression that your leased line did not use TCP/IP,
but was rather a slower, "serial" connection using modems as its
connection device.
Nevertheless, when Dial-Up Networking (DUN) is started, the local
network is immediately stopped. (Normally, a warning message is issued
to the user before this occurs as well by the operating system.)
I am not certain how you were apparently able to connect over a TCP/IP
leased line connection, and then run DUN on the host without being
inadvertently logged out.
Most likely, something it was doing with TCP/IP was not considered by
the operating system as a network, which if true, would theoretically
then remain active while DUN ran.
Don Sachnoff
Joseph Wheeler (Symantec)
wrote:
>Please excuse the last message, I clicked the wrong key! I did some
>further testing. This time I had the host set to SPX and local also
>set to SPX. I was able to connect as I would expect just like using
>TCP/IP but somewhat slower and I was then able to initiate a call as
>before but did not lose my pcAnywhere connection. It appears to work
>using SPX for the link and TCP/IP for the DUN. The only problem I
>ran into was when I went to another user running his copy of
>pcAnywhere v8.0 and set him up for SPX and attempted to connect to
>the host in the Netherlands over the Frame Relay circuit, the
>response was host could not be found. Yet from my pc, I had no
>problem connecting to the host using SPX. Any thoughts as to what
>the problem might be? The other user was able to connect using
>TCP/IP but was not able to do the DUN. We are both using the same
>version of pcAnywhere and the PCs are running NT4.0.
Hello Don,
Is there a Novell file server on this network? In order to see SPX
hosts under Windows NT, you will need a Novell file server on the
network. Was service pack 3 reinstalled after installing pcANYWHERE?
It is also important to ensure you have installed the latest hot fixes
from Microsoft.
We have a document available from our Knowledge Base on configuring
SPX connections at:
http://service1.symantec.com/SUPPORT/pca.nsf/docid/199763112924
---------------------------
Joseph Wheeler
Don Sachnoff
segment in the Netherlands. There are also several Novell servers
here in the states but not on the same segment as the user's work
station.
The user as well as myself are using SP3 on the NT4.0 workstations.
I can see the device in the Netherlands yet the other user can not.
In addition, the only option I have is SPX not IPX. The same holds
true with the other user here in the states. The pc in the
Netherlands with pcAnywhere can use either IPX or SPX. This pc is a
WIN 95 using version 8.0 of pcAnywhere.
I looked at the article you referenced, however, I didn't see
anything that I wasn't doing.
Don
Larry McDowall (Symantec)
Thanks for this new information.
On 21 Sep 1998 17:08:58 GMT, Don Sachnoff wrote:
>In response to your query below, yes, there is a server on the
>segment in the Netherlands. There are also several Novell servers
>here in the states but not on the same segment as the user's work
>station.
>
>The user as well as myself are using SP3 on the NT4.0 workstations.
>I can see the device in the Netherlands yet the other user can not.
>In addition, the only option I have is SPX not IPX. The same holds
>true with the other user here in the states. The pc in the
>Netherlands with pcAnywhere can use either IPX or SPX. This pc is a
>WIN 95 using version 8.0 of pcAnywhere.
>
>I looked at the article you referenced, however, I didn't see
>anything that I wasn't doing.
I will need to do some research on this issue and then get back to you
within a few days or so. Thanks for your patience and understanding.
---------------------------
Larry McDowall
Symantec Online Support
Symantec Corporation
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:
Tips on Using Symantec's Online Tech Support Discussion Groups
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 technical support page:
Technical Support
http://www.symantec.com/techsupp/
---------------------------
Larry McDowall (Symantec)
Thanks for your patience while we researched this issue.
On 21 Sep 1998 17:08:58 GMT, Don Sachnoff wrote:
>In response to your query below, yes, there is a server on the
>segment in the Netherlands. There are also several Novell servers
>here in the states but not on the same segment as the user's work
>station.
To my understanding, the Novell file server must be on the same
segment to enable SPX to work correctly. If it is not, then it most
likely will not work successfully with pcANYWHERE32.
>The user as well as myself are using SP3 on the NT4.0 workstations.
>I can see the device in the Netherlands yet the other user can not.
>In addition, the only option I have is SPX not IPX. The same holds
>true with the other user here in the states. The pc in the
>Netherlands with pcAnywhere can use either IPX or SPX. This pc is a
>WIN 95 using version 8.0 of pcAnywhere.
The Windows 95 computer will need to use SPX, not IPX, if they are
using that. IPX and SPX are not compatible with each other.
>I looked at the article you referenced, however, I didn't see
>anything that I wasn't doing.
Please let me know if we can be of further assistance. Thanks.
If you need to continue this issue, since this has message thread has
been going for some time now, let's start a new message thread then.
Please respond back (if necessary) and let's start from scratch on
your configuration and exact issues. This way, we can help clarify
much of the details concerning only this issue, since we have
discussed many things since this thread's beginning. Thanks.