Broadcaster, Darwin Streaming Server, IP problem?

Question

Level 1

0 points

Broadcaster, Darwin Streaming Server, IP problem?

I'm pretty sure this is a DNS issue. Hopefully someone has some simple advice out there.

I'm using an MacBookPro, Broadcaster and Darwin Streaming Server.
Attempting to create a .mov file that will deliver a live stream.

1) I created a new QT player and assigned the movie rtsp://192.168.0.105/my teststream
2) Then I saved the movie as whatever.mov
3) I then uploaded whatever.mov to a remote server.

Now if I call on this file from my local network "http://www.mydomain/whatever.mov" (using any comp here - Mac, PC) I can view the streaming movie with no problem.

However, anyone else is unable to view it. They get a broken QT error. (10060)

I'm thinking that the "192.168.0.105" IP is incorrect. (local?)

iMac, Mac OS X (10.4.6)

Posted on Aug 6, 2006 10:13 AM

Reply

Answer 1

Niel

Community+ 2026

Level 10

742,619 points

Aug 6, 2006 8:56 PM in response to ketokmagic

I'm thinking that the "192.168.0.105" IP is incorrect. (local?)

That is a local IP address, and it will only work for someone within your network. To find the correct IP address, go to this page from any computer on the LAN and note down what it reports.

You may also need to open ports used by RTSP on the firewall if you have one, and configure port forwarding on the router so that those ports are forwarded to the local IP of the computer hosting the stream.

(15006)

Reply

Answer 2

osXwookie

Level 1

145 points

Aug 31, 2006 10:00 AM in response to Niel

Keep in mind that if you are doing this off of dsl or cable, and you are getting a DHCP assigned address, you may consistenly get the same IP, but eventually you will get a different ip, and therefore the IP you got from the site mentioned above will be incorrect. You may look into using dynamic dns. Most newer routers have built in dynamic dns clients that will work with alot of free dynamic dns services. I find they are sometimes inconsistent, but that is more because of issues with the clients on the routers. If your server/computer is on the router/firewall there are os x clients out there that I hear do a better job of sending the proper info when the IP changes.

Reply