I have 3 computers at my dad’s home and I’ve always supported them remotelly using logmein free. They are all in XP Professional and using McAfee suite with no problems. Some days ago my Dad’s computer just went haywire and we bought a new Dell for him… I decided to go with Comodo Suite and all went ok but I can’t just connect to his computer remotelly while all others are ok…so it is not a network issue but his new computer…what could be wrong? any clues? someone else with the same problem? What IP addresses should I use to create a rule to allow all traffic to logmein servers?
There shouldn’t be a problem with LogMeIn. I’ve used this on a number of client PCs who are also running CIS. All I needed to do was to create a global network rule for the “ghost” network adaptor that LMI uses. Once this rule was in place, remote access was possible, once any alerts had been answered appropriately.
As an alternative, you could have a look at Comodo’s EasyVPN. This is like a combination of Hamachi, MSN Messenger and LogMeIn - secure VPN, chat and remote access in the one application.
If you do decide to try this, make sure CIS is set to automatically recognise new networks. This way you can automatically create the appropriate rules right from the get-go.
Well. did another test… Installed Comodo Internet Security on my mom’s computer and it is working fine in the same network and subnet (only - of course… - the ip is different from my dad’s one) and it is working fine. It is something with the firewall. So, I should be the one blamed for a broken installation probably. I recall that when I did this one I was blocked because the discovery of new networks was turned off. I manually entered the new range and it worked but maybe something else has to be done.
By any chance, does anyone have an idea where the validation of LogmeIn may be being blocked? What protocol is used for the validation? Remember that I can connect but somehow or a protocol is being blocked or a port is closed somewhere. I will check the logs since it should be there if it is happening…
To get LMI working, the LogMeIn applications “logmein.exe” and “logmeinsystray.exe” (I’m pretty sure that’s what they’re named) need to be able to get out to the internet and be able to receive a connection from the internet.
To check if they have been blocked in CIS, look in
Hi! You can also try pc file transfer. I have several computers set up with this program and it works good. I don’t have problems with this remote application tool, ever.
speedmaster,
This was sent to me by Todd Dyer at LogMeIn: Often times the user name is really an alias and need the real name etc.
If you login to your computer through the XP/Vista Welcome Page, the name shown on that page may or may not be your username. To find your true username, do the following at the target computer:
Windows XP:
Go to Start
Click Run
In the Run box type: cmd and press enter
In the command prompt, type: echo %username% and hit enter
Windows Vista:
Click on Start
In the Start Search bar type: cmd and press enter
In the command prompt, type: echo %username% and press enter
This will display the username that you are currently logged in with.
What do I do if I do not know the password?
Unfortunately, Windows does not allow anyone to actually view passwords. If you do not know the current Windows password, you will need to change it. To do so:
Right click on the My Computer (Computer in Vista) Option in the Start Menu, and choose Manage
Under System Tools, expand the Users and Groups folder, then highlight Users.
On the right are the usernames on the computer, right click on yours, and choose Reset Password to change the password without needing to know the old one.
If you enter your Windows username and password or access code incorrectly too many times, your IP address will be locked out. In order to clear an IP lockout, you need to have physical access to the computer that you were trying to access.
Please right-click on the LogMeIn systray icon, located in the bottom right-hand corner of your computer and click Open LogMeIn.
Click the Options button on the left-hand side of the Toolkit window.
Click the Preferences button under Preferences and Security.
Click the Security Settings tab at the top of the Toolkit window.
Click the Show Details button under Authentication Attack Filter.
Click the “X” to the right of the IP Address you would like to delete from the lockout.
Note:
If you are unable to physically get to the Host computer, the lockout will remain in effect for 30 minutes. After 30 minutes, the IP lockout will automatically clear.
