PCAnywhere host inaccessible after SP2 XP upgrade

  • Thread starter Thread starter Ian
  • Start date Start date
I

Ian

I use custom ports with PCAnywhere to access various
machines on our network when outside, and post-SP2
upgrade for XP this functionality is not working.

I suspect windows firewall is blocking request and would
like to know the minimum essential programs that PCA 10
needs to act as a host.

I presume that's safer than just opening the 2 custom
ports wide to any programs. I don't find the Windows
Firewall exception stuff documented well enough for me,
I'd like some more examples or help in there.

Any advice is welcome.
 
I would disable the ICS for the test. if it works, then enable ICS with
exception. If ICS with exception gives the same problem, use netstat command
to check the port status.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
Thank you Robert, but you're talking a bit above my head
with the acronyms.

I assume ICS is the Windows firewall, which I can easily
turn on and off, yes.

When you say "...with exception" I presume you mean just
specify the custom ports to leave open for PCA or
anything else trolling along.

I expect that will work but I wanted to have those ports
only open for the specific .EXE's that PCA requires for
this system to be a host. From poking around the
Firewall options it looks as if I can (a) add the
PCA's .EXE that isn't yet on the list, and (b) use some
sort of syntax to open just that particular .EXE up for
only the 2 custom ports it needs. That would be more
secure.

Maybe my assumptions are wrong about the custom
capabilities of the Windows Firewall.

I can also look up how to use the netstat command.

As a thanks and courtesy(?), note you have a grammar
error in your SIG file.

-Ian
 
Back
Top