If you decide to disable ActionScript sockets, you may find that certain known legitimate SWF files stop working as intended. For example, SWF files deployed by your own organization no longer function as intended. If this happens, you can selectively reenable ActionScript socket functionality by configuring individual hosts to which Flash Player should allow ActionScript socket connections.
To selectively reenable ActionScript socket functionality (this assumes you have already followed the steps above for disabling sockets):
You can add this line as many times as you need. You can specify Intranet host names without periods, Intranet or Internet host names with periods, or IP addresses.
The hosts you specify are the target hosts to which socket connections are made, not the source hosts from which SWF files come. Connections to the hosts that you selectively reenable are permitted from all SWF files.
Flash Player will only permit socket connections when ActionScript specifies the exact host name or IP address that you have specified in an EnableSocketsTo directive. For example, if you maintain a host called host1.mycompany.com, it might also be reachable as just host1, or as anothername.mycompany.com, or as 192.168.1.15. If you specify only EnableSocketsTo=host1.mycompany.com in mms.cfg, then ActionScript will only be permitted to connect to this host when it explicitly specifies host1.mycompany.com, not when it specifies host1 or anothername.mycompany.com or 192.168.1.15. Likewise, if you specify only EnableSocketsTo=192.168.1.15, then ActionScript will only be permitted to connect to this host when it explicitly specifies 192.168.1.15, not when it specifies any other name. If you need a host to be reachable using multiple names, enter an EnableSocketsTo directive for each name.