Re: Request for help: troubleshooting pcAnywhere with TZO + Linksys

From: Mr. Land (graftonfot_at_yahoo.com)
Date: 05/21/03 

Date: 21 May 2003 13:59:26 -0700

Hi Gary,

Thank you very much for your reply. I've actually read a couple of
items suggesting that, despite the fact that the Linksys seems to be
successfully forwarding ports 8000, 8001 and 8080 to my Web server,
and despite the fact that the router's Port Forwarding configuration
page suggests that it is also forwarding the ports required by
pcAnywhere, in actuality it may NOT be forwarding these required
ports. I've already done a poweroff/poweron reset of the router, with
no effect. But I wonder if there is some tool or utility I can run at
the server that will allow me to determine if requests are actually
arriving there on the ports in question, having been forwarded by the
router as expected?

In the meantime, your idea of testing from a dial-up connection is a
good one. I'll rig that up and give it a try.

Thanks again.

Gary A. Edelstein <edelsgNO@SPAMyahoo.com.invalid> wrote in message news:<t7ancvorh685cpu6h5hcvav8g9bulo2l6j@4ax.com>...
> On 21 May 2003 08:16:58 -0700, graftonfot@yahoo.com (Mr. Land) wrote:
>
> >Hello,
> >
> >I am hoping someone can help me troubleshoot a problem that started
> >happening to me recently.
> >
> >I have a home server that I have been accessing from my office via
> >pcAnywhere. Sometime within the past few days, I have lost the
> >ability to connect, and I'm not sure how to troubleshoot this.
> >
> >My setup is as follows: I have several PC's sharing a DSL connection
> >via a Linksys router. One PC is a Windows 2000 Server; the others
> >various flavors of Windows and Linux. All PC's are configured to get
> >their local LAN IP addresses from the Linksys, except the server,
> >which has a static IP of 192.168.1.2. On that server, I have three
> >Web applications running on ports 8000, 8001 and 8080 (port 80 is
> >blocked by my ISP.) I also run pcAnywhere host on that machine
> >(configured with the default ports, 5631 and 5632).
> >
> >I use TZO dynamic DNS to access the server from the public Internet.
> >The Linksys forwards the above-mentioned ports (plus a few others) to
> >the static address of the server.
> >
> >From my office, I can access all 3 of the Web applications
> >(mydomain.com:8000, :8001, :8080) and I USED to be able to connect a
> >pcAnywhere remote to the pcA host running on that same machine, but
> >that no longer works.
> >
> >I've checked with the IS people where I work and they've assured me
> >that they have not made any changes. I am not aware of any changes
> >that I may have made.
> >
> >What troubleshooting I've done is as follows:
> >
> >Retrieved the current, assigned IP of the Linksys router from TZO and
> >tried connecting pcA from my office using that IP: that didn't work.
> >Tried connecting to the pcA host via a pcA remote from another one of
> >the machines on my home LAN with pcA configured to use the server's
> >static IP: that worked. Then tried connecting same using
> >mydomain.com: that worked, also! (Does that go out to TZO for
> >resolution, or does the Linksys "remember" that it is "mydomain.com"?)
> >
> >It seems that on that last test, the pcAnywhere remote is indeed
> >"going out" to the TZO nameservers, getting the name resolved, then
> >successfully connecting the required ports (or maybe not?). It is
> >only when I try to connect from my office that it fails (I have no way
> >to test any other location on the Internet.)
> >
> >Is there some methodology and/or tools I could use to determine where
> >the connection is failing?
> >
> Assuming you've changed nothing at home, then the only things I can
> think of are your DSL ISP is blocking the PcA ports or your work is,
> despite what they told you.
>
> A test from outside your work environment trying to connect to home
> from the open internet would be a good idea. Could you do that say
> with a dial up modem connected temporarily to your work machine? Gary
> E
>
> |Gary A. Edelstein
> |edelsgNO@SPAMyahoo.com.invalid (remove NO SPAM and .invalid to reply)
> |"We have met the enemy and he is us." - Walt Kelly's Pogo

Relevant Pages

  • Re: SBS 2003 - FrontPage 2003 can not connect to site on Internet
    ... I pasted the config /all below and I do not know what you mean by forwarding ... the ports, so maybe we did not do that. ... into the Server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Access
    ... I have opened all relevant ports on the router and they are forwarded to the ... IP of the external NIC of the server. ... > You should go for port forwarding where you define that all incoming traffic ...
    (microsoft.public.windows.server.sbs)
  • Re: SSH, X11 forwarding and TCPIP V5.4
    ... > on the window connection ssh tunnels ... > local ports accept connections from other hosts: ... exactly the same SSH server config as you posted, ... forwarding refused" when I connect to my SSH server. ...
    (comp.os.vms)
  • Re: Web Site
    ... Ive got ports 79 to 82 forwarded to the .101 which is the ... >> I am running windows 2000 advanced server. ... >> ftp site. ... I have forwarding enabled for the ports I am ...
    (microsoft.public.windows.server.general)
  • Re: PCanywhere and ISA 2000
    ... Forget all this "ports & publishining" stuff. ... > Thank you to everyone but with all these problems I have decided to go with> a terminal server instead. ... What version of PCA are you using? ... I seem to remember>> reading somwehere that 10.0 and below had some sort of problem with ISA - ...
    (microsoft.public.windows.server.sbs)