About debugging a NetConnection.Connect.Failed message

If a NetConnection.connect() command returns an information object with a code value of NetConnection.Connect.Failed, you cannot establish a connection with the server. Every time you receive this error, ask yourself some standard troubleshooting questions:

Are you connecting to the correct server?
Is the server running?
Are you specifying the protocol (rtmp:) for connecting to the server?
If you are connecting from behind a firewall, are you specifying the correct protocol (rtmpt:)?

Attempts to connect to the server can also fail if the permissible number of socket connections on either the client or the server computer is at its limit. This limit is dependent on how much physical memory your server has, and how busy the connections are. On Windows systems, the memory for socket connections is allocated out of the non-paged memory, so it cannot be swapped out to a page file. You may see that you reach the maximum limit at different values from time to time as other running programs (such as core operating-system services) are competing with your program for space in the non-paged memory pool.

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/fms/2/docs/00000098.html