Don't use just "lfsworld.net/remote" use the entire "www.lfsworld.net/remote". For some reason without the www., there's relay errors, but the instant you change the URL, it works.
That's a native Flash security feature I believe. It may be possible to capture the error and correct for it in ActionScript, I can't remember. Definitely can be done in the PHP wrapper though.
Assuming you are running Windows XP, try to delete the Flash cache from \Documents and settings\<your user name here>\Application Data\Macromedia\Flash Player
could the people with that error #2024 problem make a screenshot of when the error is displayed?
What the flash documentation states as the cause for a #2024 error isn't possible for as far as I can see, so i'm curious when it happens and where you see the error (in the top-left messages log or in a popup or maybe somewhere else)
Vic, I seem to only get errors on my laptop in very small cases. It doesn't happen if I use my iMac as a router and connect through that (rather than properly to my router), and the Remote.app doesn't do it but site does (Just threw me a 2048 this time.)
need - as a matter of fact, that's what does pop into my mind as triggering it. I only started getting that error after Safari (in OSX) decided that I didn't have flash installed, so I installed it again. Especially because in Windows where I'm using an older version, it works...
For the interested ones : You cannot supply policy files via the webserver anymore _to create a Socket_. You need to run a special policy server on port 843 (so you have to be root!) that serves them. I've made this server now, but need to test it a bit more and make it fork as non root etc. But just so you know, the solution is underway.
ok, policy server running - you can use the remote with the latest flash player again. If you still get the message, make sure you do a ctrl-f5 to re-load the remote (otherwise caching may happen)