Hi, As mentioned could you try running a mBox trace on the page where the activity is running to confirm that users outside your internal IP addressed can indeed qualify for the test. Are you using a profile script with a regex condition to filter out your internal IP range? If so it could be that its too restrictive.
Are you using at.js or mbox.js for your implementation? A4T only works with at.js 0.9.6 or later, not with mbox.js. Also, have you looked in Target to see what numbers it is reporting? I would check Target to see what it is reporting and see if its more accurate than A4T.
If Target is correct, then most likely this is only a reporting issue, not an issue splitting traffic. In other words, its quite possible that your test is running correctly and splitting traffic correctly, but its just reporting wrong through A4T.