Keeps dropping from secondary Mac. Used to be fine

[DeepYogurt]

What Terminal commands did you use to verify the files were on the system or not?

-Bob

[mandos]

Hi Bob... agree esp when clients are requesting changes in between.

I'll reinstall on both machines and get back to you tomorrow.

Thanks for your assistance / patience.

[DeepYogurt]

I did a little more investigating of where teleport installs its files.

I removed everything to do with teleport on a Snow Leopard MacBook system and installed from scratch, and installed so that all users on the system could use it, but it didn't install it's files into the /Library directory but installed some in /Library and some in ~/Library - so now I'm not sure which one is correct. Despite the fact that I had these files installed in the /Library on the system before I removed them. No idea why it picked one location for one install and another location for another install. Seems pretty weird - maybe Jul knows something about why it would pick two different locations for two different installs.

In any event first look in both places (/Library and ~/Library) and make a copy of what it is on your system using some combination of one or the other sets of Terminal commands in the previous post.

Then remove everything except the copy you made in it's own folder (don't remove the install file that should be wherever you downloaded it to on your disk), then empty the trash and then reinstall and setup on both your systems.

If that fixes things then we should be able to tell if there is a difference between what you had installed when things were goofy and what is now installed when they are working. Depending on what is different will dictate what we can and can't look at in more detail. I'm hoping it's the Preferences file that got corrupted somehow, so make sure you pick the same setup parameters in the new install as you had in the old. May be a good idea to take a screen shot of the teleport setups (layout, security and options) before you remove anything so you can be sure of what you had.

If this reinstall does not fix the problem then not sure what to do, but no use in worrying about that for now.

So let us know how things go and good luck.

-Bob

[fulekia]

Any progress on this?  Teleport worked fine for me between two Leopard machines, but since upgrading the slave to Snow Leopard, control drops every few seconds.

[mandos]

Last week I performed a clean install on the two machine as highlighted by Bob, and esp after I made sure the two computers were shaking hands. But the issue is still (annoyingly) there.

There is nothing that triggers it, just all of a sudden my pointer / cursor will be teleported back to the master. Very annoying esp when typing...

At first i thought it could be an ethernet / airport setup issue as airport is my main source of connection... so I set up an ethernet and IP address(es) purely for this but the issue still persisted.

So I don't know for certain if the airport / ethernet set up would be an issue and whether it should be only airport or should only be ethernet but either way I need airport...

[mandos]

adding to the post above... the only thing I wasn't 100% on when reinstalling was if Bonjour was connected between the two computers... I am fairly certain this option is offered within airport setup so I'll check it out now.

[DeepYogurt]

So what do you have set for the meta-keys? Can you post an image of the teleport prefpanes? If not, just post the plist file - should be located in ~/Library/Preferences/com.abyssoft.teleport.plist

If you post the plist file - don't include the hex information for the TPHosts or TPTrustedHosts or CertificateIdentifier keys - just replace the info with "xxx" - not sure if this info would compromise any personal info or not, so just to be safe don't include it.

And just to be sure, does teleport die on either the slave or master (if so which one) when this behavior occurs?

And one more thing to post - the output of "lsof -i" both before and after the disconnect occurs on both the slave and master system.

-Bob

[mandos]

The meta-key is set to command.

Prefer to send the teleport prefpane images and plist to your email address - ok?

The behaviour is very simple. I'll be working on  the slave and then suddenly the control is whipped back to the master... nothing seems to trigger this.

I move the mouse back to the slave and then it whips back to the master. I move the mouse back etc...It does this three times successively before it settles down and I can work again... then it will happen again in approx 15mins to 20mins later. Not sure as I'm not timing it.

[CeeDubH]

Here's what I am currently going through with Teleport.

I use a Mac Pro at work, and I bring in my MacBook Pro to sit along side it. I use a Bluetooth Mac keyboard and Magic Mouse through an iOmega Bluetooth adapter in the Mac Pro. Teleport allows me to use my wireless keyboard and mouse through the Mac Pro to control the MacBook Pro.

Teleport worked great for almost three years, no issues whatsoever.

Within the last month or two months, at inconsistent times throughout the day when I am controlling the MacBook Pro, the connection will "skip". The mouse will move back to the Mac Pro, and for about 3-5 seconds, if I move the mouse over to the MacBook Pro, it will work for about .5-1 second, and then move back to the Mac Pro. After the 3-5 second "skip" time is over, Teleport will go back to working normally for a time.

At first I believed this to be a network issue. The network at the company I work for is very strong, but we also have a very busy network. I currently have a 5-port 1Gb/s switch, which both my Mac Pro and MacBook Pro are plugged into, being ran straight into our network backbone, a HP 5412. I began running continuous ping tests. No matter when the "skipping" occurs, ping tests are solid. I also move a lot of files back and forth via afp and had no issues with that. I run iStat Menu's, and never see a connection drop off for my network monitors.

Full removal and reinstallation of Teleport has not helped. I have deleted the following:

Users/~/Library/Caches/com.abyssoft.teleport
Users/~/Library/Preferences/com.abyssoft.teleport.plist
Library/PreferencePanes/teleport.prefpane (This was actually removed in System Preferences)

Eventually, about three weeks ago, fed up with Teleport not performing correctly, I attempted switching to Synergy. I removed Teleport completely, and installed Synergy. Synergy worked well for what it did, and confirmed that the issue is not network related. But the two features that make Teleport so much more useful (Copy & Paste, switch monitors with momentum) are glaring omissions from Synergy. After using Synergy for a week, I felt the need to try again with Teleport.

Complete uninstall of Synergy, double check that Teleport is completely uninstalled, reinstall Teleport. No issues for two days.

Now the issue is back, and I am turning to the forum's for help.

[CeeDubH]

Any response?

[CeeDubH]

Any response?

[Eccent]

Any response?

I've had that(random mouse jumping to other computer) happen before.  I think I had it caused by two things in two different scenarios.  

In one, it was caused because I had a USB mouse connected to (the computer the mouse pointer jumped to) and that mouse's optical laser wasn't fully on the desk or I had to unplug/replug the USB cable and the jumping stopped.

In another case, I had to disable some 3rd party software.  I can't recall which because I go through many.  If the wired mouse isn't the cause above, just try turning off 3rd party things.

[Philco]

Same here.
Worked fine for years and now jumping from one screen to the other and stopping working.
It's like we all caught a virus or something happened with a Mac update.
Shame, it really works well when it's working.

Time to look at Remote Desktop perhaps?

[jul]

If you have these issues, you can try:

Code: [Select]

defaults write com.abyssoft.teleport disconnectOnNetworkConfigChange 0

This way, teleport will not disconnect if it detects that something has changed in the network (this may happen too frequently).