Here are some things to try (from the Producer Release Notes).  #4 is 
most relevant I think.

   1. If you are unable to establish a player connection to a live
      broadcast, and you want to determine whether the problem is a
      configuration problem in RealProducer, try the following:
         1. To confirm that the stream has reached the server, check
            that the stream appears in the Server Monitor's connections
            tab.  You should see an entry of Type 'encoder' along with
            the proper filename.
         2. If you are using the Legacy Server broadcast method, ensure
            that you have the correct Server mount point ("/encoder/" by
            default) in your player URL.  For example,
            rtsp://yourserver.yourcompany.com:554/encoder/live.rm
         3. If you are using any of the Server 9 Push broadcast methods,
            ensure that you have the correct Server mount point
            ("/broadcast/" by default) in your player URL.  For example,
            rtsp://yourserver.yourcompany.com:554/broadcast/live.rm
         4. If you are using the Pull broadcast method, ensure that you
            have the correct Server mount point ("/broadcast/pull/" by
            default) in your player URL.  For example,
            rtsp://yourserver.yourcompany.com:554/broadcast/pull/live.rm 
   2. You must use a password when using the Pull broadcast method from
      the command line application (-si).  If you wish to broadcast
      using the Pull broadcast method and not require a password, use a
      server file with the server definition option (-sd).
   3. When using the *Account-Based Push* broadcast method, be sure the
      username and password are added to the correct realm on the Helix
      Server. For the *Account-based Push* broadcast method, users
      should be added to the Helix Server *SecureRBSEncoder* realm.
   4. When using the *Account-based Push* broadcast method with Helix
      Server 9, you may experience problems making new Account-based
      Push connections if the Helix Server Administrator is used to
      reconfigure the Helix Server while existing Account-based Push
      encodes are running. To avoid this problem, do not reconfigure the
      Helix Server while Account-based Push encodes are active. You can
      identify Account-based Push encodes by looking for pairs of
      entries as follows in the Helix Server Monitor:
      IP ADDRESS 	TYPE 	DURATION 	FILENAME
        	encoder 	00:02:27 	live.rm
      172.23.104.111 	player 	00:02:27 	encfs/servvar.set

      Each of these entries represent a single Account-based Push
      broadcast session.


Note: I can't recall if the Helix Server monitor page 
(http://<SERVERIP>:<ADMIN_PORT>/monitor.html) is available thru the 
hc.org build.  If not, then I'm not sure how to do the equivalent w/o 
it.  Could do it via the registry but that's a little complicated.

Thx, Steve

On 2/16/2007 4:54 PM, on focus wrote:
> Hi, Sujeet,
>
> first thanks for the reply. A couple clarification based on your message:
>
> 1. I suppose your rmserver.cfg, is hlxserver.cfg in the current release.
> 2. I didn't find any section in *.cfg file that has those definitions in your email.
>
> Anyway, I made a little progress by using password only authentication (port number doesn't really matter here, i can specify 8080 which is my Helix http port, or not specify at all),
>  producer.exe -i c:\test.avi -o test.rm -sp :producerpassword at 192.168.1.3/live.rm
>
> It seems the authentication error is gone, but when I use a RealPlayer to try to play the live stream, realplayer rtsp://192.168.1.3/broadcast/live.rm,
>
> The player says the link doesn't exist. And I checked Helix server logs, both error.log and access.log,
>
> error.log:   16-Feb-2007 07:02:46.UNKNOWN tmplgpln(4607): 50: Error retrieving URL `broadcast/live.rm' \(Invalid path)
>
> access.log has the error:  "GET broadcast/live.rm RTSPT/1.0" 404 0 [Lin\ux_2.6_10.0.0.0_play32_RN01_EN_586] [512ae9b1-bdc7-11db-f665-4d97144fcbdb] [Stat3:187|0|ST\OP|;][Stat4:0 0 0 0|0|0| 0 2] 0 0 0 0 0 12
>
> I don't know what is going. I thought the /broadcast in Helix Server 11 is the default mount point which works with with Helix Producer 11's Push broadcasting. BTW, I also set the SecureRBSEncoder Realm and correpsonding user name/password.
>
> Any suggestion to diagnose the problem will greatly appreciated.
>
> Frank
>
>
> Sujeet Kharkar <skharkar at real.com> wrote: 
> In command line that you are using -sp
> username:password at ipaddress:port/streamname the port specified should be
> HTTP port of the server.
>
> Since default installation of server uses 50001-50050 as ports for receivers
> dynamically created by mount point encfs, my assumption is that is not the
> configured HTTP port.
>
> Example config entries in rmserver.cfg file specifying concerned ports.
>
>
>         
>         
>         
>
>
>
> You should be able to find more information in help file installed with
> producer (producer -m) in following chapters.
> Chapter 14: Using the Command-Line Application 
> Chapter 11: Running a Broadcast
>
> Thanks,
> Sujeet
>
>
>
>
>
> -----Original Message-----
> From: helix-producer-dev-bounces at helixcommunity.org
> [mailto:helix-producer-dev-bounces at helixcommunity.org] On Behalf Of on focus
> Sent: Friday, February 16, 2007 3:29 AM
> To: helix-producer-dev at helixcommunity.org
> Subject: [Helix-producer-dev] Live broadcasting issue
>
> Hi, 
>  
>  On Windows platform, I am using both Producer 11 and Sever 11_1 to do
> acount-based unicast broadcsting following the documention. After setup, I
> launched server and then  issue the commend
>  
>  producer.exe -i c:\test.avi -o test.rm -sp
> producer:producer at 192.168.1.3:50001/live.rm
>  
>  But the producer immediately outputs the error message:
>  
>  BroadcastDist: Unrecognized option config.
> BroadcastDistribution.Destinations.19216813.Authentication.StatsInterval
>  Error: Failed to establish a TCP connection with server 192.168.1.3 for
> authentication.
>  
>  Both my producer and server are on the same machine 192.168.1.3 and I
> turned off the firewall compeletely. I also tried this with server sitting
> on different machine, but it is same result. I don't know what is going on.
> And didn't find any documents that describe the problem either. 
>  
>  thanks for any suggestions.
>  
>  Frank
>  
> ---------------------------------
> Never miss an email again!
> Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
> _______________________________________________
> Helix-producer-dev mailing list
> Helix-producer-dev at helixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>
>
>
>   
> ---------------------------------
> Looking for earth-friendly autos? 
>  Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.  
>  
> ---------------------------------
> It's here! Your new message!
> Get new email alerts with the free Yahoo! Toolbar.
> _______________________________________________
> Helix-producer-dev mailing list
> Helix-producer-dev at helixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>
>