Helix/Real Player IPv6 DNSIssues

---

From: filesystem-dev-bounceshelixcommunity.org [mailto:filesystem-dev-bounceshelixcommunity.org] On Behalf Of Test Drive
Sent: Thursday, September 21, 2006 3:22 AM Ping
To: Jamie Gordon
Cc: filesystem-devhelixcommunity.org
Subject: Re: [Filesystem-dev] Re: [Player-users] Helix/Real Player IPv6 DNSIssues

Hi Gordon,

I have RealPlayer (win32) Version 10.5 helix Powered
Build: 6.0.12.1698

I thought real player 10 supported Ipv6

Thanks

On 9/20/06, Jamie Gordon <real.com" target=_blank>jgordonreal.com&gt; wrote:

It's not clear what player version you are using, but it probably
does not support IPv6. So the client would try to resolve the hostname
because it does not recognize "[2001:db8:100:f101::2]" as an IPv4
address.

In order to use ramgen with IPv6 browsers and IPv4 players, you need
to set the ramgen hostname in your server config to either a hostname
that can be resolved by the client as IPv4 if it does not support IPv6,
or set it to an IPv4 address to ensure backwards compatibility.

Jamie

Daniel Yek wrote:
>; I suppose this is a question for filesystem-dev mailing list.
> Forwarding...and BCC player-users.
>
&gt; At 06:07 AM 9/18/2006, Test Drive wrote:
>;
>> Hi List,
>>
>&gt; I am testing Helix Universal Player with IPv6 support. Everything is
>>; good on the server side.I have tested my setup with IPv4. Everything
>> works perfectly well. ; However I have issues on the client side when
>&gt; using IPv6. I have tested both windows/linux clients. I put the ipv6
>&gt; address of my Helix server in /etc/hosts and equivalent on windows.
>> From browsers the navigation works good by using the hostname which
>> gets resolved from /etc/hosts and equivalents. However when i try to
>>; play
>&gt; < http://myhelixserver:80/ramgen//timeradio.rm>http://myhelixserver:80/ramgen//timeradio.rm ,
>>; realplayer/helixplayer gives me an error regarding the resolution of
>> the name.
>> "
>> Unable to locate server. This server doesnot have a DNS entry. Please
>;> check the server name in the URL and try again.
>;> rtsp://[myserverip]/etc......
>> "
>> I downloaded the timeradio.rm on client side and try peek into it. The
>&gt; intersting part is that timeradio.rm already contains the IP address
&gt;> of the server. The entry in the timeradio.rm looks like this.
>>
>&gt; "rtsp://[2001:db8:100:f101::2]:554//timeradio.rm?cloakport=80,554"
>>
>> Even though I am using a global scope IPv6 address, I am on an
>>; isolated network in VMware Machines.
>> Why would the player try to go to DNS server when it already has the
>&gt; IP address?
&gt;>
>;> I am unable to work it out. Am I missing something?
>>
>> Thanks In Advance
&gt;
>
>;
> _______________________________________________
> Filesystem-dev mailing list
> helixcommunity.org" target=_blank>Filesystem-devhelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/filesystem-dev