Re: WME --> Windows Media Player - URLs that function/don't from home/work

http://forums.ricknmiasworld.net/5100b/conncfg.htm

See bottom:

A very limited number of applications require that the public IP address assigned to the
modem be used by the local LAN device.

Mine WAS set to "no" use private IP address. I have changed it to "yes".

JL

"Jim Lewandowski" <jlewand@xxxxxxxxxxxxxxxxxxx> wrote in message
news:9vAEf.16156$_S7.3260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
At home, I got WME to successfully work with my webcam (a miracle). At home, to TEST, I
used Windows Media Player and used the "Copy Internet URL"/"Copy LAN URL" both are the
SAME (one is uppercase, one is lowercase). This URL looks like the "machine name" as
far as Windows is concerned. All OK.

At work, semi-obviously, using this internal "Lan-ish" URL does NOT work. From work I
had to use the actual IP address of my home PC.

Since, I want to make this easier, I signed up for a no-ip.com "domain". All good, up
and running. However, I can not get it to work. To summarize:

At Home

Fire up WME - set to "pull" to port 8080

http://machine-name:8080 works in Windows Media Player
http://IPaddressofmyPC:8080 does NOT work (C00D11B3) in WMP
http://myname.no-ip.info:8080 does NOT work (C00D11B3) in WMP


At work

http://machine-name:8080 does not work (11B3??) in WMP
http://IPaddressofmyPC:8080 works in WMP
haven't tried the no-ip URL yet but will Fri AM.


Can someone explain not only WHY the above combos work/don't work but HOW this really
works (no-ip has no doc., WME has no doc, I've scoured the internet newsgroups and
regular webpages for almost 2 full days with nothing remotely close to explaining HOW
this works).

IOW, what is REALLY happening when you put in the no-ip address - is it a URL redirect
just like when you have "URL forwarding" for a domain name?

What is happening to "port 8080" when WME is running?

When WMP gets either a HARD IP address of the new funky no-ip URL, what happens behind
the scenes to get it all hooked up to work?

JL




.

Relevant Pages

  • Windows Media Encoder Behaving Like a Service?
    ... WMP sat there saying "Waiting" in its status bar while ... WME reported that there was still a client connected to it on port 8080. ... still nothing listening on port 8080. ...
    (microsoft.public.windowsmedia.encoder)
  • Re: WME --> Windows Media Player - URLs that function/dont from home/work
    ... Telnet jlpupcam.no-ip.info 8080 gets "Connect failed". ... Fire up WME - set to "pull" to port 8080 ... http://IPaddressofmyPC:8080 does NOT work in WMP ... When WMP gets either a HARD IP address of the new funky no-ip URL, ...
    (microsoft.public.windowsmedia.encoder)
  • Re: WME --> Windows Media Player - URLs that function/dont from home/work
    ... redirects. ... They strip off any port appended to the URL. ... http://IPaddressofmyPC:8080 does NOT work in WMP ... When WMP gets either a HARD IP address of the new funky no-ip URL, ...
    (microsoft.public.windowsmedia.encoder)
  • Re: WME --> Windows Media Player - URLs that function/dont from home/work
    ... For example, this WHOLE time I've been hearing the term "port forwarding", I had no idea ... Another possibility is that port 8080 is being blocked by your firewall. ... http://IPaddressofmyPC:8080 does NOT work in WMP ... When WMP gets either a HARD IP address of the new funky no-ip URL, ...
    (microsoft.public.windowsmedia.encoder)
  • Re: WMP settings
    ... where the WME and WMP run on different PC's. ... WMP is set to port 8080 and the received stream in the WMP is fine. ...
    (microsoft.public.windowsmedia.sdk)
Loading