Computer becomes very slow if iTALC-master is running
- Especially if you have a lot of clients open you need to increase the update-interval in the configuration-workspace.
- if it does not help take a look at Tuning_iTALC-installation
Clients are not reachable although iTALC-client is running
- Are all the settings correct (IP-address etc.)?
- On windows clients the keys should NOT be in the italc folder in "Program Files" they should be in c:\italc\keys\public\ (at least on my system.) check the italc_client.log as mentioned below.
- Can you ping the host?
- Did you disable the firewall or configured an exception for ica.exe (especially under Windows)?
- Did you make sure that no other VNC-software is running on clients? If so, disable it. You can make ICA and existing VNC-software cooperate by running ICA on another port than 5900.
- Can you access port 5900 of the host using telnet?
- Are authentication-keys setup properly, e.g. (correct) public key is readable by ICA on client and private key readable by ICA and IMA on master?
- Are there any warnings or critical messages in /tmp/italc_client.log (Linux) or %TEMP%\italc_client.log (e.g C:\temp\italc_client.log or C:\windows\temp\italc_client.log) (Windows)?
I can't start iTALC Master Application
- Process all steps mentioned at "Clients are not reachable although iTALC-client is running"
- Have you launched the client (ica) in your system? You NEED ica running to start the master (italc)!
- On the master-computer can you access port 5800 at localhost?
Everything is working quite well except the demo-mode
- Your demo-mode-interface settings probably are wrong. Open configuration-workspace and check them.
Under Windows XP SP2 or SP3 I can only connect to a limited number of clients
If you are using the master on a Windows XP SP 2 or SP3 machine you need to modify your TCP connectivity limit. SP2 and SP3 have introduced a feature that limits concurrent TCP connection attempts that are possible to 10 per seconds which doesn't work very well with iTALC. After changing the limit, the Master becomes way more responsive and users have confirmed a huge improvement in performance.
One can use [this tool|http://www.lvllord.de/?lang=en&url=downloads] to update the tcp connection limit to 100. It reports as a Virus with McAffee since it modifies windows TCP.sys file but I can assure you it isn't. Use at your own risk in any case.
I have found a reasonable work around for some virus software reporting that modifying the tcpip.sys settings is a virus. Boot into safe mode WITHOUT networking and then run the program mentioned above. We are running eTrust and it didn't give any problems running the fix in safe mode and didn't report any errors after reboot - even with a direct scan of the tcpip.sys file. I can't comment on other virus software, but hopefully others could try this out and post back here.
Problems after updating old iTALC-installations to 1.0.4 or higher
iTALC >= 1.0.4 uses Qt 4.3 which has a changed main-window-architecture (compared to Qt 4.2 which is shipped with older iTALC releases). Thus personal configuration-files are not compatible with this version. This is no big problem, as you can simply remove your old personal configuration (not the global configuration with all clients and so on!). Make sure no iTALC Master Application is runnung. Then under Linux remove ~/.italc/personalconfig.xml while under Windows you have to remove C:\Documents and Settings\<your user-name>\Application Data\iTALC\personalconfig.xml (if it isn't there, search for personalconfig.xml on C:\). Afterwards start iTALC Master Application and everything should be well now (except client-window-positions and so on which you have to re-arrange).
Someone xx.xx.xx.xx tried to connect to this computer and failed to authenticate themselves correctly
A previous public key wasn't deleted properly. The best way to fix this is to thoroughly uninstall iTalc, then reinstall it using the latest keys. Instructions to uninstall iTalc are found towards the end of the Installation instructions http://italc.sourceforge.net/wiki/index.php?title=Installation#Uninstallation
Remote power on (Wake on LAN) doesn't work although I've verified the client machines support it
This is because the Wake on LAN magic packets are sent to a broadcast address of 255.255.255.255, and that's apparently being routed out the wrong ethernet adapter. This happens if you have two or more ethernet devices in the computer running the master, for instance if that machine is also performing network address translation for your client computers. I'm not sure if it's possible to correct this within iTALC currently, but you can specify the broadcast address using the `wakeonlan` utility (e.g. 172.16.0.255) or the ethernet device using the `etherwake` utility, and create a script to power up your machines.