How to test Red5 server externally - red5

I have installed red5 server on my localhost on which an xampp running. I can access port 80 externally so anyone knowing my id can access my web directory. However, an external computer cannot connect to my red5 I believe as I have a the videowhisper script installed and while I can connect to rtmp server locally, an external user cannot connect.
Is there a way to test the external connection to rtmp server from my computer? Or even there is and I cannot connect externally how can I fix it?

You cannot ping 1935, or so I have not found a way to. My best answer is the telnet from a remote device using 1935 as a port
that would be(in CL):
telnet ipaddress port
if it connects it will give you the output about the escape character. That means You are connected.
Though this may not be the recognized solution, it has worked for me, as a quick and dirty answer.

RTMP works on port 1935 not port 80 unless tunnelling is specified. Have you tried pinging 1935 from the external machine?
Pete

You must open ports 5080 and 1935 both on:
your RED5 web server and...
optionally (if any) network router, depending on your network topology;
If your web RED5 server stands behind a gateway you must open these two ports on your gateway as well in order to access RED5 from outside this network.

Related

SQL Server 2014 cannot connect to remote Server

Before I get flagged, I will say that I have tried everything that I could find, but I still cannot connect:
I have opened TCP Port (1433), Server is listening on ['any' < ipv4 > 1433].
I have enable the server browser service
I have enabled remote connections in my SQL server
I have also assigned the TCP port to the TCP protocol for sqlexpress here
I also tried tried to debug the connection using the NETSTAT.exe and it says the TCP 1433 is listening.
I have restarted the service several times when I try to connect from my local PC I get the following error
I can connect remotely to my server using IIS and url.
Question:
What can I do to debug the connection between the devices?
For people that are interested in the question.
I have fixed the issue, (by luck), so what I did I was playing around with the different kind of ports and I added a rule for range ports from
1430 to 1440
and that seemed to fix the problem.
Check it out here
Also for people that use Azure make sure to add a rule in the network security group.
Thanks for the help

Can't Port Forward To Ubuntu Web Server

I've set up an Ubuntu Web Server to host a game that uses port 25565.
I've set the router to port forward that port to the web server and gave the web server a static local IP. I've done this before using my own PC as the server.
When I try accessing the web server on that port using it's local IP I have no problem at all.
But, when I try accessing it from outside the network, I can't connect.
I've opened my router's list of DHCP clients and the web server is only listed there sometimes without a pattern I've been able to see.
Why I think the error is at my router:
I've installed Wireshark on the server to see if Apache was somehow blocking the web packets upon arrival. I tried opening all ports and I tried opening port 10000 which webmin uses (I'm able to connect to it locally). Neither has been successful.
Although I'm not experienced in the field, I don't think the packets get to Apache.
Please assist. Thank you!
Does your router hold the external IP address, or an internal one?
If it holds a private IP like 192.168.x.x, 10.x.x.x, or 172.16.x.x, then you would need to setup port forwarding on whatever device your router is connected to.
I've managed to fix it by changing the web interface of the port forwarding from atm1.1 to ppp1.1. It was just luck, as I understood it's web protocols but I don't know why it worked.
Thanks everyone for the help!

Access a system URL in the network

I am trying to access the url localhost:8088/openbravo from the network. The local IP of the system is 192.168.1.101/openbravo. But when i try it from other system in the network, it doesn't work. Is there any setting that i need to do.
i added the ip address in the hosts file of the local system. But it didn't work too.
System is windows 2008 server 64bit.
--
Thanks
With it being Server 2008, have you disabled the Windows Firewall to see if it will work. It may be blocking incoming connections from that port from the other local networked machine. After the test, then you can reenable and add a firewall exception for the tomcat port of 8088.
http://technet.microsoft.com/en-us/library/cc766337(v=ws.10).aspx
try with this 192.168.1.101:8088/openbravo.

Access wamp server outside, not only inside

I configured my wamp server to access it online. I add the port 80 in my router, I clicked on the online button in the wamp tray icon. I changed the information from the httd.conf file, but I can only access it from inside my network. For example, with my iphone, I can access it only when it's connected on my wi-fi. With the 3G, an outside network, the server just time out and doesn't respond.
Please can you help me, I need that quick please,
Thank you,
Cedric
Are you accessing via a public IP address (not a LAN IP)?
Did you also configure Windows Firewall to unblock incoming port 80 requests?
If so, and everything else is correct, your ISP/provider might be blocking incoming port 80 requests.

simple question about port 80 on ec2 virtual Windows Server

I set up a Windows 2008 Server virtual machine on Amazon ec2. I gave it a "security group" that includes HTTP 80.
I installed GlassFish server and have it listening on port 80.
I can Remote Desktop to the machine (ec2-174-129-128-105.compute-1.amazonaws.com), open a browser, and browse to "http://localhost:80" and see the GlassFish welcome page.
However, when I attempt to browse to the machine from my local laptop like so ...
http://ec2-174-129-128-105.compute-1.amazonaws.com:80
... it just times out.
Any idea what I have to do to open the machine to browsing from the internet? Or what I'm doing wrong?
Thanks,
rob
Answering my own question. I had to open port 80 on the windows firewall. It turns out Windows Server 2008 is locked down excessively tightly out of the box.
try to give the ip address of the machine instead of
http://{your ip address}:80
and see if it works