more Remote Connection trouble

Today I could not connect to Jupiter remotely from blackhawk.  I went to Shamrock and tried to remote connect to jupiter from quick and I could not (quick is on the local network with jupiter).  After checking several things, I turned the Windows firewall off, and then I could connect from quick.

This is confusing for several reasons.  First, why was the windows firewall even on?  I would have assumed that the PC Tools firewall would have turned off the windows firewall when the PCT firewall was installed. Second, remote desktop was selected (checked) in the windows firewall as being one of the applications that was allowed to go thru the windows firewall.  Same for the PCT firewall.  So if it was allowed by the windows firewall AND the PCT firewall, then why did it not work?

I will try to remote connect to jupiter again from blackhawk tomorrow and see if it works.

remote desktop thru PC Tools firewall

I have been trying to use remote desktop to connect to jupiter (at Shamrock) from blackhawk (at Cotton Plant).  It did not work.  Today I figured out that the PC Tools firewall (PCTF) on Jupiter was blocking the connection attempts by blackhawk.

The configuration of the PC Tools firewall is tricky because in the applications tab of the PC Tools firewall config screen, it lists Remote Desktop as an allowed application for both inbound and outbound connections.  So I thought it would work, but it did not.

I figured out that the Cotton Plant IP had to be added to the trusted IP list in the PCTF profiles screen. I will have to add my notebook computer's IP address at Brook Chase apts if I want to remote connect to Jupiter from home.

I was at the Shamrock office (where jupiter is) today but I was able to test the remote connection to jupiter from blackhawk by first remote desktopping out to blackhawk from jupiter and then remote desktopping back into jupiter from blackhawk. Cool!

Blackhawk virus problem at Cotton Plant

Got "Internet Security 2010" virus somehow on blackhawk computer at Cotton Plant about a week ago. I tried to fix it with Vipre anti-spyware, but then the computer always went straight back to logon screen when you logged on. So I brought the original win xp disk with me from Shamrock to re-install Windows.

At first I tried to look at contents of harddrives on blackhawk using a linux live cd. The PClinux os disk that I burned hung when I tried to boot from it, but an old "Tiny Me" linux disk worked. I was able to see everything on the hard disks. When I put in the win xp disk, I tried the option to use the recovery console (I think) to repair the existing version of win xp, but it asked for administrator password, and I did not know it, so I reinstalled win xp. When I say reinstalled, I mean that I chose the "repair existing version of windows" choice rather than wipe out the existing version and start completely over. Now it seems to be working OK.