Re: trouble with RealPlayer files on iPaq 1940

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Daniel Rosenzweig (danr_18_at_yahoo.com)
Date: 09/05/04 

Date: 4 Sep 2004 18:53:23 -0700

Thanks...

I've gone through all this before... I used a packet sniffer to see
what ports are being used... Each time a tranfer is started, an rtsp
conversation goes on and the client tells the server which ports to
use. The ports you mention are only for the rtsp negotiation, not the
actual data stream. Real's site explains what goes on -- but it was
pretty obvious looking at the RTSP packets themselves(they're plain
english text) even before I found the info on Real's site.
Using a packet sniffer on my PC, I could see that the port ranges were
radically different (the PPCs ports were about 10x higher than the
PCs)...
even though the PCs range, according to Real's website, does include
those higher ports.... If you want to forward all the ports for
RealPlayer, you're
fowarding a VERY large range of ports!

I even got a hold of someone who had access to the Real PocketPC
client's sourcecode. He told me what registry settings to change...to
specify which ports to use (the PC version has a UI screen to do it)
it didn't work. I confirmed with him that I did it correctly. The
problem is that he didn't have an actual PPC to test with.

I can't get a new router... as the router which is causing the problem
is a VOIP router... the only one supported by my VOIP provider. Thus,
if I change routers, I lose phone service... I could technically turn
off the router /DHCP in the VOIP box... but speaking to the router's
tech support - that could
open up vulnerabilites in the VOIP part of the box. I've spoken to
different levels of both tech support (provider/router) to no avail --
other than to keep my eye out for new firmware... but they don't have
port ranges on their future feature list yet.

I don't remember the page I had before, but this lists which
ports need to be opened in firewalls (PC version - at least)
http://service.real.com/firewall/proxycfg.html

I can't find the RTSP URL right now.
====
Click on the first RealAudio in the list and click Edit. Initial
connection should be on port 554, type should be set to TCP out bound.
Highlight and remove all entries in the "Port ranges for subsequent
connections."
Click Add, then add UDP 6970-32000 inbound and select OK.
Clid Add, then add TCP 6970-32000 inbound and select OK.
Click on the only remaining RealAudio in the list and click Edit.
Initial connection should be on Port 7070 outbound, Type should be set
to TCP.
Highlight and remove all entries in the "Port ranges for subsequent
connections."
Click Add, then add TCP 6970-7170 inbound and select OK.
Click Add again, then add UDP 6970-7170 inbound and select OK.
====
"Neil Smith [MVP Digital Media]" <neil@nospam.com> wrote in message news:<clfbj09pj94e82n8vuvgl22vns0kgddiou@4ax.com>...
> I'm not sure to suggest. What port range are you seeing the PPC trying
> to connect on ? It only does rtsp streams, so that should be ports 554
> and 7070 which need to be passed through to your PPC.
>
> What may be happening is your router is forwarding those ports but for
> *TCP only*. RTSP used by real player generally uses UDP ports
> (connectionless) for streaming.
>
> So you need to check your routers manual and ensure that you allow
> both those ports through over UDP and TCP protocols.
>
> Given that your router is unnecessarily restrictive in allowing 10
> port ranges to be used, you need a new device. I use freesco
> http://www.freesco.org on an old 486/33 with 2 network cards for this,
> and it works very well. (I can also do PPTP private network over the
> internet to where I work, and I use IRC and netmeeting on it too ;-)
>
> You can probably get a 486 PC with 32 meg free from any PC junk shop.
>
> Hope that helps (probably not !) Cheers - Neil
>
> On 31 Aug 2004 18:21:04 -0700, danr_18@yahoo.com (Daniel Rosenzweig)
> wrote:
>
> > My new wirelessrouter
> >doesn't open up the ports used by the PocketPC client. The PocketPC
> >client documented port range overlaps with the Windows one... but in
> >reality, they choose wildly different ports. My PC's player has no
> >problem going through the
> >router, while my PPC can't with this router. Worse, that this router
> >doesn't allow for forwarding ranges of ports only 10 individual ports.
> > So, I can no longer listen to RealAudio on my PPC, due to the new
> >W-router.

Relevant Pages

  • Re: 2 pc network - cant see host files from pc 2 on pc 1
    ... Assuming that you have firewall protection via your internet router try ... workgroup because it will be needed for the network to work correctly. ... see if you can access TCP ports 139 and 445 on computer one of which at ... permissions. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Do I need these services listening?
    ... > first computer that has the modem & router, so I call the second one ... Your Netgear router should connect to the internet. ... Your Netgear router should have the public IP address. ... that if the ports look closed even ...
    (comp.security.firewalls)
  • [VulnWatch] 3Com OfficeConnect Remote 812 ADSL router exposes internal LAN computers ports during ou
    ... ports during outbound and inbound TCP and UDP sessions. ... The 3Com 812 is a widely-deployed router, found in many ISPs ADSL lines. ... for internet access. ...
    (VulnWatch)
  • Re: ISA 2004 - How to allow Guest and Client access from wireless
    ... peace and quiet here are great for working; it's just the darn internet ... access and now wireless that are a pain in the rear. ... That could plug into another port on the router. ... The router has 4 "internal" ports; one is taken up by the cable ...
    (microsoft.public.windows.server.sbs)
  • Re: ATTN Tony Whitmore please
    ... I've not used your router before, but I've just been looking up ... that the router is configured with ports 80 and 23 open on the public ... log into your router using the ARM interface. ... telnet and http access to just your local network. ...
    (comp.security.firewalls)