InOut Tracker FAQ

Frequently Asked Questions

Q. Mac OS X Server (10.3+) doesn't work as a QC/IOT server
A. As of Panther (10.3), Mac OS X Server blocks the TCP/UDP ports for Classic applications. To clarify, this is a problem with the OS X server operating system, not just the Xserve hardware, so if you have OS X Server running on an iMac you will still experience the problem.

back to top

Q. Remote users and NAT issues:
A. The current version of InOut Tracker does not support NAT (Network Address Translation). If this remote user is connecting via his ISP, the chances are good that they will not be able to use InOut since the vast majority of ISPs are using NAT. If they are dialing into your network via your router there shouldn't be a problem. InOut uses the TCP port #51026.

back to top

Q. Getting InOut Tracker to run on Windows XP:
A. If you are Administrator on this machine login and go to the Control Panel/User Accounts and assign Computer Administrator privileges to the User on this machine.
Log off system.
Login as that User and setup InOut Tracker for that User.
Log out of InOut Tracker.
Log off system.
Log back in as Administrator and go back to Control Panel/User Accounts and set the privileges for this User back to being a User.

back to top

Q. Windows 2000 Terminal Server:
A. The current version of InOut Tracker is not designed to work in the Windows Terminal environment. It is designed to be used per user with the data stored locally.

back to top

Q. InOut Tracker and Mac OS X:
A. InOut Tracker does not work on systems set up for multi-homing. If you create more than one connection in System Preferences:Network pane, InOut Tracker will not work. This sort of configuration is most common to find on laptops which are carried between home and workplace networks.

back to top