W2K Server Won't Accept PCAnywhere TCP/IP Connection

[ewm0826]

I built a W2K server recently to do two functions:
1- for off site remote access & file transfers
2- for use as a server for Federal Express Server software.

PCAnywhere did accept TCP/IP connections but now that Fedex software is installed does not. My assumption is the Fedex software is blocking ports.

Anyone know if Windows 2K can override this blocking? Where would I look? I assume the registry, but am not familiar with W2K reg edit. Fedex technical is useless, so I need the experts here.

PS: Have tried other ports on PCAnywhere, no luck.

 

[Seizure]

I think PcAnywhere uses TCP – 5631,UDP – 5632 by default. These ports are changeable on later versions. On NT/2000 machines you can issue a "NETSTAT -a" from the command line to see if the Fedex program is using these ports. Look for "listening" on port 5631. For an article on how to change the ports on version 10.5 use this link.

http://service2.symantec.com/SUPPORT/pca.nsf/docid/2001021417112312

Jim - Synnex Info Tech

 

[Seizure]

Do they use a NAT router or do they dial up. If they use NAT and port mapping, FedEx probably restricted the incoming port to their own service address. That's what I typically do when I remotely manage systems. Is there more than one computer at the site connected. Start PcAnywhere on the machine and look at the event log. Use "Netstat -a" from the command line to see if PcAnywhere is listening on 5631. They may have used the options tab in the 2k ip configuration to filter by port. If they use dial-up check the IP config for it as well for filtering. Jim - Synnex Info Tech

 

[ewm0826]

Jim:
Thanks for your ideas. We have the system config'd to use ports that are not the default in PCAnywhere. The router/firewall has been verified so we covered that.

I will be trying netstat to see if that points me in the right direction. I did find out that another similar server in another location of ours will not run netstat. When called, all it does it put a dialog that says "Can't initialize..." or something similar. I think the Fedex folks are trying to lock down the machines real tight.