Why do I get a TCP/IP error message when attempting to enable TCP/IP incoming access?
If you attempt to enable TCP/IP incoming access on one operating system while it is enabled on the other, you might receive the following error message: Timbuktu Pro could not enable incoming TCP/IP access. Please check the TCP/IP configuration. After restarting, switch incoming access o On o Off (avoids this alert) Because one operating system is attempting to listen in on UDP port 407, enabling the other Timbuktu Pro will cause this error message since the port is in use. This issue within Timbuktu Pro is directly due to a problem in the classic environment within OS X. The issue is that when a classic application on Mac OS X closes a UDP port, the classic environment doesn’t release it for other applications to use. Forcing the classic process to stop, frees up the port. Note: If you are running OS 10.1 and v6.0, you will also get this error message. This problem has been resolved in Timbuktu Pro v6.0.1. The workaround is to disable TCP/IP incoming access on the other version of Tim
Related Questions
- When attempting to access the Internet I get this error message: "Forbidden you were denied access because: Access denied by access control list." What is wrong?
- Why do I get the error message "Specified class not registered in registry" when attempting to connect to an Oracle database?
- Why do I get a TCP/IP error message when attempting to enable TCP/IP incoming access?
