Timbuktu now makes default contact via TCP rather than UDP. In previous versions of Timbuktu, contact was made on UPD port 407. In Timbuktu Pro 5.2.x and higher, the contact port has been changed to TCP port 407, though for backward compatibility, Timbuktu hosts still listen for connections on UDP port 407 as well as TCP Port 407.
Now the TCP contact port for incoming TCP/IP connections can be changed from the default TCP Port 407. This may be useful if you need to use Timbuktu through a firewall or through a router running Network Address Translation (NAT). There is no interface within Timbuktu to change the port. In order to change the port, you'll need to use AppleScript. A sample script for changing the port to TCP Port 1843 is provided below.
tell application "Timbuktu Pro" set the contact port of its internet transport to 1843 end tell
Open your Script Editor (in Apple Extras:AppleScript), paste the script into the Untitled window, and click 'Run'. If desired, you can save the script to use later or on other machines.
Note: Timbuktu Pro will reflect its new port after deselecting and reselecting TCP/IP incoming access (Setup:Preferences).
If you're not sure which ports are available for use, you may want to check the current reference for assigned ports at: http://www.iana.org/assignments/port-numbers
There are unused ports in the Registered range (1024 through 49151) which are currently safe to use, but could collide with something else in the future. The Dynamic/Private range (49152 through 65535) should be safe to use and are the ports we recommend. We don't recommend that you use the well-known ports (1 through 1023) to avoid conflicts with other applications. If you specify port 0 (zero), it will switch to the default, TCP Port 407.
Changing the contact port used by Timbuktu affects the host side only. The host will continue to accept connections on UDP 407 and UDP 1419, in addition to the TCP port specified so that PCs and Macs running older versions of Timbuktu will still be able to connect.
Changing the contact port used by the host doesn't affect the configuration on the guest, so the guest can continue to make connections to users over either TCP Port 407 or over a changed contact port. However, when a 5.2.x and higher guest connects to a host with the changed contact port, the alternate port must be specified along with the host's address in the New Connection window as follows:
Connecting over a changed TCP Port currently only works from a 5.2.x guest and higher to a 5.2.x host and higher. Previous versions of Timbuktu Pro for Mac or Windows can still connect to the host, but not over the changed TCP Contact Port. They will continue to connect over UDP 407 or UDP 1419. For purposes of backwards compatibility, Timbuktu will continue to listen on TCP port 407 (as well as UDP port 407) even if the primary contact port has been changed.
Machines with changed TCP ports will show up in red text in the TCP/IP Scanner window so network administrators can quickly identify them. The Timbuktu Pro Info and Incoming Access windows will also show you if your local machine is using a non-standard port.
Users no longer have to open the additional TCP Ports on their firewalls for the Timbuktu services, since the specified port is used for contact as well as the Timbuktu services. Intercom still requires an additional, dynamic UDP port, though.
If you want to reach multiple users behind a router running Network Address Translation (NAT) you should give each host its own port number and configure the router to "export" each of the host addresses with the host's port number. Guests do not need to change their contact ports, but must specify the router's external address along with the port number of the desired host. The IP Locator can help, but only if the router has a static address (or keeps the same address for a long time). Each host can override the registered IP address in the advanced IP Locator preferences, specifying the router's external address.
You should not specify the changed TCP port if you are connecting using the IP Locator, because the IP Locator stores the host's contact port on the findme.netopia.com server and the guest automatically uses it.
After you've run the AppleScript changing the TCP Contact Port once, the new setting is stored in the Netopia Preferences file, so you won't need to run it again, unless you trash your Netopia Preferences.
Note: When running the script, one may receive the following error message "Timbuktu Pro got an error: A privilege violation occurred."
-This error is caused by the fact you have a master password set up in your Timbuktu Preferences. You will need to go to Setup:Preferences:Master Password and remove it while running the AppleScript. Then you can re-enter your Master Password.
Timbuktu Pro version 7.0, and higher, now has the ability to change the TCP Contact Port within the Timbuktu Pro User Interface. To change the contact port, go to Setup:Preferences:TCP Contact Port. Enter the contact port number you wish to use and hit the Save button.
Note: It is our suggestion that you choose a port number that is higher than 1024.