I have FMS 2.0.4 and XAMMP 1.6 installed on my computer
locally.
i use the following code to test a connection to the FMS:
conn = new NetConnection();
conn.connect(''rtmp:/localhost/my_app'');
conn.onStatus = function(info) {
trace (''Level: ''+info.level+'' Code: ''+info.code);
};
but it seems it cannot establish a connection to the FMS
server and
returned the following errors:
Level: error Code: NetConnection.Connect.Rejected
Level: status Code: NetConnection.Connect.Closed
tried these other codes too on the connect function:
conn.connect(''rtmp://localhost/my_app'');
conn.connect(''rtmp://127.0.0.1/my_app'');
conn.connect(''rtmp:/127.0.0.1/my_app'');
conn.connect(''rtmp:/my_app'');
but still no luck.
What seems to be the problem in my configuration?
By the way, I tried to disable the XAMMP but stll it cannot
establish a connection?
Tried to run it in macromedia flash 8 using alt+enter and
through the
webserver using the publish html and swf files but still the
same.
Ive been working on this for days.
Im desperate,i need to start working on the application
already.
Somebody please help..
tnx..NetConnection.Connec...
i had this problem too, in fact i had this problem right
after a clean install of the product. i did some research online
and found that this is not uncommon. unfortunately, the solution,
while easy, is hard to find.
Basically you'll want to use the following syntax:
conn.connect(''rtmpt://localhost/my_app'');
conn.connect(''rtmpt:/my_app'');
If these do not work, which it did not for me, i found
success when i also included the port number as:
conn.connect(''rtmpt://localhost:1935/my_app'');
I have no idea what the extra t at the end means, but my
understanding is that this is the protocol used when behind a
firewall. apparently a variety of services like mcafee, norton,
windows firewall, etc. all block these requests unless you are
using rtmpt.
also note that the single slash is used when the
domain/server is the localserver. e.g. rtmpt:/my_app is the same as
rtmpt://localhost/my_app. however, if these don't work as i
mentioned above you and must include the port number, then only
rtmpt://localhost:1935/my_app can be used.
let me know if this works for you as i'm curious how
successful this solution is.NetConnection.Connec...
To clarify... the extra ''t'' means ''tunneling''. When
tunneling, the rtmp packets are wrapped in http headers. When
tunneling, speed and performance suffer a bit.
Typically, when tunneling, you'd use port 80. In most cases
the firewall is simply blocking port 1935, in which case it
wouldn't matter if you use rtmp or rtmpt over port 80.
also be sure to check your log files (or you can go in
through the admin console and view the server log).
with this particular error, i personally had:
''Asynchronous I/O operation failed (Failed to attach to
completion port: The parameter is incorrect.''
if you do a search on this error you will find not so much
information. i was able to get my application working using the
rtmpt protocol, but now, after coming back to work and booting my
machine, it's not working again and i have the same error.
things i've tried:
1) i shut down all anti-virus and firewall applications and
services
2) run netstat -a to see what is running and what ports are
being used
3) try specifying a different port for FMS to run on (default
= 1935). this can be changed via $InstallDirectory$\conf\fms.ini
(in windows). Inside the file search for ADAPTOR.HOSTPORT and
change the value to whatever port you want to try.
4) try variations of the url e.g. rtmp:/ rtmpt:/
rtmpt://localhost rtmpt://localhost:1935 etc.
5) make sure you don't have programs like netlimiter
installed as this is a known app that can cause problems w/ FMS by
intercepting system calls on the machine.
If you do find something that works, please contribute to
this thread as it could become valuable for others having these
issues.
Finallyyyy! Whewww
got it to work on con = (''rtmpt://localhost:1935/app_name'');
thanks to all you guys. ^_^.
Guess something is blocking my port 1935.
glad you got it working.
for other people who stumble upon this issue and find
themselves here, i found some more information regarding particular
software that creates issues with FMS.
I had NOD32 (by ESET) on my machine. Fantastic anti-virus
software. I read that someone w/ this same software was having
issues. They said they uninstalled it and it worked.
I thought, ''Well, uninstalling isn't necessary. I'll just
shut it down and disable it.'' So i did this, restart (just for
thoroughness), and tried again. It didn't work. I reluctantly
uninstalled the application, restarted again, and this time? FMS
worked.
It's clear that somehow NOD32 creates a problem for FMS. How?
When it's not running? I have no idea. I hope this helps.
I have created a application using media server. It is
working properly in our intranet. We are trying to access from out
side out network. The http link is accessible. But the server
connection is failed. It is not happening while running through
internet.
Please can any one explain what are the settings needs to be
done for external access?
Advance Thanks!
ANANTH
It was the nod32 i guess.. thanks chapel21.
All is working now with ''rtmp:/app_name''
since i removed my nod32.
it is now working in the network too.
thanks u all guyz . ^_-
Flash_Ananth,
Did you ever get an answer to your question about accessing
FMS outside your network? I'm experiencing the same problem.
Cheers!
Your network admin probably needs to allow access to port
1935 to the 'outside world.' I don't know what the technical jargon
is for this, since I am not a network admin myself. I just told
ours to open up port 1935, and it worked.
Sorry i didn't check this post thread for awhile.
Flash_Ananth:
Have you checked the FMS log files to see if it is rejecting
the connection? If there is no errors related to attempted
connections, then chances are the firewall in the network or on the
machine is preventing the connection as HITdrumHARD suggested. I
would also try opening port 1935, provided that you haven't changed
the default configuration of which port FMS listens on (to
determine this see the configuration file in the root). Once this
is opened continue to look in the FMS log files to see if you're
receiving connections. If you are, but it is still rejecting the
connection, please submit the error message in this thread.
Hi, I've very green to Flash Media Server and I've only
worked servers a little bit. But I'm trying my first program just
to get started by streaming a video and I've been having a lot of
difficulty. The documentation I can find is little help, so I've
been looking through forums. My computer is not the flash media
server but the FMS is on the same network. I've tried different
netconn.connect() combinations and all four give me this error:
NetConnection.Connect.Failed. But when I open up the management
console for the FMS, it says that it connected to every combination
except rtmpt without the port (rtmp with the port and without and
rtmpt with the port all say they connected to the server).
The server increments the number of connects and disconnects
simultaneously, I think because the client doesn't think it's
connected. Am I missing something? Please help. Thanks.
Help with this pls
Connecting to the video server...
%26gt;%26gt;The client does not have permission to connect to the
application, or the application expected different parameters from
those that were passed.
%26gt;%26gt;The connection was closed successfully
I have a similar problem. I will get the Connect.Rejected
after ~10 minutes of streaming from a server. Everything is fine
until ~10min into the streaming, my client receives the reject
packet and the server terminates the tcp connection. I do not have
any trace log of the server since it is a third party server. Are
there anything I can do on the client side to inform the server to
do the streaming indefinitely or until the client stop? Any
pointers would be greatly appreciated. Thanks.
THANK YOU FOR THIS POST!!!聽聽 I WAS HAVING THE SAME PROBLEM AND JUST FIXED IT BY CHANGING TO ''rtmp:/app_name''!!!
Ben
No comments:
Post a Comment