Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a MMO using a flash/flex (AS3) client that needs to make a raw socket connection to our server. I have tried several different methods of serving the xml policy file on port 843 as detailed by Adobe.

Now everything seems to work fine for most clients, but a large percentage (20% ?) of our clients cannot connect to this magic port (843) and get the xml policy file. Our clients are just random people out on the net, so we have no control and no real info about their environment.

I'm logging the success/fail of client connections by having the client send me an email via php, so either way these users have net access, but cannot get the magic policy file. So far it doesn't seem to matter what OS/browser or even flash version they are using...

Right now I'm just trying to determine if the problems are server side, client side or somewhere in between.

Has anyone else has similar experience with Flash's new socket policy stuff and what can/may cause clients not to connect to the magic 843 port ?

Is there an 'official' policy server that I can try to at least rule out my code as a potential problem ?

Thank-you very much !


share|improve this question

Maybe these users are behind a firewall which prevents them from connecting to the 843 port? For an 'offical' flashpolicyd see:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.