pcAnywhere

[bztips]

In my old installation of Wingate 6, I was able to set up a client machine as a pcAnywhere host by using a mapped link.
I've tried the same thing with Wingate 7 with no luck.

Services:
Install TCP Mapping service, specify both Service port and Destination port with the same number used by the pcAnywhere host machine; Destination = internal IP address for the host machine (192.168.0.x); Mapping enabled = True
Ditto for UDP Mapping, with the corresponding UDP port number

Extended Networking | Port Security:
Make sure that both ports are open as Connections from the Internet and LAN Connections to Wingate PC.

With this setup, I can't connect to the pcAnywhere host.

Any ideas on what I'm doing wrong?

[adrien]

Hi

do you get any notifications about port conflicts? If the mapping service is running on the same port as pcAnywhere, it would need to be bound to a different interface to avoid conflict. If pcAnywhere binds to 0.0.0.0, this could cause a problem.

If the port is in conflict, the TCP mapping service probably wouldn't start properly.

WinGate 7 checks a bit more thoroughly for port conflicts before attempting to start a service. WinGate 6 would disable conflicts from blocking ports from being opened. This could cause some issues with some software, e.g. WinGate preventing other software from working properly, so we put in more pre-checks, and don't attempt to start the socket if it would conflict.

Does the service show as started, in the binding tabs as well?

Adrien