inconsistant connect() response and session handling

Hello,

First off, thanks for a great module.

I've used this module successfully with previous Drupal versions, but am having weird issues with the D6 version.
I have a Flex 3 based custom application meant to interact with Drupal. (ie: Node creation, category listing and similar). For clarity purposes, I've managed to replicate the issue with a very simple app that calls system.connect() on loadCompleted and displays the username and userid of the retrieved user data in a text field. The app also has a button that calls system.connect() and compares the newly retrieved Drupal user with the existing app user. If there is change in the session, the app displays the new username and userid.

Simple enough right?

I login as admin, load the app and see "admin + 1" in the text field. I then switch drupal users in another window and click the button. my app detects the session change and displays the new active user data.

This works perfectly for me, but other people trying it always seem to get the wrong data from the connect() call. They consistantly get "admin" user data regardless of which actual user is logged into Drupal.
The only difference between me and the others is Location...and in fact Continent. We're all accessing a live server and the same Drupal install, and the app is within the Drupal structure.

If they trigger the connect() method through the Browse page of Services they get the right data. But if they use the app they always get Admin.
IE always returns "anonymous" and FF returns "admin" for them. But for me all works perfect.

I'm using Services in combination with the equally cool AMFPHP module.

Have you had this happen before or could you point out some hints as to what I should check for?

I can't think of reasons why a connect() call would differ from one computer to another.

Thanks a bunch for any hints,