Any PC Anywhere users?

Admiral Huddy · 27 Feb 2010 at 16:46

I've been given the task of setting up PC Anywhere between two remote PCs.

All is working as expected when the host and remote are on the same network (specifing IP address) but what if want to access the remote system over the internet? I take it the remote system must have a unique IP address or i can't see how this is going to work?

Any idea what I need to set-up?

This has to be PC anywhere.

Thanks

Admiral Huddy · 28 Feb 2010 at 19:15

bumping this? Can i use the WAN IP address?

m4cc45 · 28 Feb 2010 at 19:50

Yes you have to use the WAN IP address and the ports forwarded to the PC. You can use something like dyndns.org and use a generic DNS name rather than it's IP (requires small clien on the PC or setup on most router).

Which version of PCA are you using then I can check the ports you need to forward.

M.

SiriusB · 28 Feb 2010 at 20:01

You could give LogMeIn a look. It is free to use and is secure. It is also web-based meaning you can control any PC you add to the computers list from anywhere else in the world. A small client runs on each computer meaning you do not even need to know what IP the computer is on to connect.

Just throwing it out there as an alternative since you seem to have a solution

Admiral Huddy · 28 Feb 2010 at 20:16

m4cc45 said:
Yes you have to use the WAN IP address and the ports forwarded to the PC. You can use something like dyndns.org and use a generic DNS name rather than it's IP (requires small clien on the PC or setup on most router).

Which version of PCA are you using then I can check the ports you need to forward.

Port forwarding.. any info you got would be helpful. Thanks

M.

I'm using the 12.5 trial version. I have to see it's quite impressive when using LAN. I've entered the WAN IP address but nothing

SiriusB said:
You could give LogMeIn a look. It is free to use and is secure. It is also web-based meaning you can control any PC you add to the computers list from anywhere else in the world. A small client runs on each computer meaning you do not even need to know what IP the computer is on to connect.

Just throwing it out there as an alternative since you seem to have a solution

Many thanks.. Gave this a go today. Although it's simple and easy to use, I'm not sure about the level of secuiry it uses. PCA is approved by the Data Protection Agency, which is a requirement.

theheyes · 28 Feb 2010 at 20:45

Admiral Huddy said:
Many thanks.. Gave this a go today. Although it's simple and easy to use, I'm not sure about the level of secuiry it uses. PCA is approved by the Data Protection Agency, which is a requirement.

May I ask where you got this information from? I wasn't aware that they approved any product over another. In fact, I got the impression they purposely stopped short of this.

m4cc45 · 28 Feb 2010 at 20:49

You need to port forward 5631 to the LAN PC. Then connect your test PC to the internet (not the LAN) and then try and access it via it's public IP.

M,.

SiriusB · 28 Feb 2010 at 20:53

I don't know the ins and outs of how it works, I do know it creates a certificate for each connection and uses AES-256. Entirely moot though if the software requires DPA approval. No idea if LogMeIn is or is not approved.

m4cc45 · 28 Feb 2010 at 22:02

It's more the fact that you can't really lock down logmein. It's accessible for everyone with a web browser. PCA can be locked down to point to point (with static IP's) it also has username and password authentication (I believe even to the point of domain integration) and is secure.

M,

SiriusB · 28 Feb 2010 at 22:26

Well, with logmein you need to know someones account details to access the dashboard. You then need to know the password for each particular computer and then you need to know valid logon credentials for said computer. You need 3 pieces of information to log into someone's machine.

However, as with any third-party service there is the extra point of failure, namely the LogMeIn servers. I just threw it out there as an option. I use it extensively to manage client workstations remotely as it allows me to view their screen as they show me a problem, and I can also show them solutions.

There are probably hundreds of machines altogether that I deal with and remembering the IP and password for them all would not be possible [or insecure as I would have to write them down!]. But horses for courses and all that!

Admiral Huddy · 1 Mar 2010 at 08:26

theheyes said:
May I ask where you got this information from? I wasn't aware that they approved any product over another. In fact, I got the impression they purposely stopped short of this.

The person I'm doing this for has made this a request.

I have used LogMeIn and it's pretty good. The only thing i have noticed that the remote PC isn't locked down and blanked out, meaning anyone near the remote PC can see what the remote person is doing.

m4cc45 said:
You need to port forward 5631 to the LAN PC. Then connect your test PC to the internet (not the LAN) and then try and access it via it's public IP.

M,.

Sorry may I ask you to expand on that a little. I'm not that much of a networking guru

What would be the services IP address in theis case?

i.e. Service name = "PC Anywhere", Start=5631, End=5631, IP Address = ??

m4cc45 · 1 Mar 2010 at 09:03

IP address would be the local IP address of the PC you want to connect to.

So it's the LAN IP of the PCA Host.

M.

SiriusB · 1 Mar 2010 at 09:48

Admiral Huddy said:
The person I'm doing this for has made this a request.

I have used LogMeIn and it's pretty good. The only thing i have noticed that the remote PC isn't locked down and blanked out, meaning anyone near the remote PC can see what the remote person is doing.

During remote control click Options at the top of the screen and you will see some checkboxes on the far left. You may blank the screen during use and lock the keyboard. Once checked they should remain the default.