With our set up we're running Darwin SS on Win 2000 with ABSOLUTELY NOTHING
else on the box. It's a powerful box, and I thought bandwidth wise it was
free of bottle necks but Joel may be right.
I will investigate further. It's EXTREMELY important I get this resolved
ASAP so any additional feedback/suggestions are more than welcome.
Doug Muir
Creative Director
UIM Creative Group Inc.
----------------------------------------------
email@hidden
www.userinmind.com
-----Original Message-----
From: email@hidden
[mailto:email@hidden]On Behalf Of Peter
Kerr
Sent: Thursday, February 13, 2003 4:27 PM
To: email@hidden
Subject: Re: Darwin streaming issue
"Doug Muir" <email@hidden> wrote Thu, 13 Feb 2003 14:16:38 -0500:
>We have Darwin set up here on a P4 2.4GHz box with 2GB of RAM running
>Windows 2000. When we try to stream our video content, it's incredibly
jerky
>and usually stops playing after a few frames. The actual movie continues to
>play but the video stops and the audio cuts in and out. If the user changes
>their quicktime settings to accept streaming content on HTTP port 80
instead
>of UDP, everything streams fine. What is the cause of this? I can't force
my
>users to go through their quicktime settings and switch to HTTP port 80
>instead of UDP. My media files seem fine and are hinted. But the video
plays
>horribly using UDP, regardless of how fast your connection is.
I have now seen this first hand. After all the chiding in this list
about setting up firewalls to allow thru ports 554, 6970-6999, 7070,
8000-8100, I now find it's not always that simple.
I have a shiny new XServe, and thought it might be a Good Idea (TM)
to use not only for its intended purpose of a fileserver for a small
audio lab, but also put our departmental QTSS there. Lab traffic is
firewalled by the XServe. "Inside" clients on the second NIC at
addresses 10.0.0.2 - 10.0.0.15 can receive the mp4 streams OK.
Outside clients get the first ~1 second, then chopped fragments.
/var/log/system.log shows the denied packets.
What is happenning is something I observed earlier, and seems to be a
"feature" of QTSS: ports in the range 6970 - 6999 are not released
when a client disconnects. They may be cleaned up at a later time, I
don't know when. But if a QT client asks on :554 for a stream, it
will by default ask for :6970,6971. If this is still in use (or
flagged in use) client/server are supposed to negotiate a higher pair
in this range. I have NAT operating with the "use same ports"
directive, but what is happenning is that the client, or the server,
or both, will usually agree to use a higher port from the range 4971x.
I could add this range to my firewall rules, or I could just go back
to my old beige G3 for QTSS, outside the firewall...
--
Peter Kerr tel +649 3737559x87562
Senior Technician fax +649 3737446
School of Music, University of Auckland, New Zealand
_______________________________________________
streaming-server-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/streaming-server-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
streaming-server-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/streaming-server-users
Do not post admin requests to the list. They will be ignored.
