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


"Mike Lowery" <selfspam@xxxxxxxxxxxxxxxx> wrote in message
news:uR1SbZALGHA.3460@xxxxxxxxxxxxxxxxxxxxxxx
Networks are far from basic.

***
I'm saying basic from the standpoint of a flowchart or how stuff gets from point A to B
conceptually.

For example, this WHOLE time I've been hearing the term "port forwarding", I had no idea
WHICH direction. IOW, it seems that port forward means take a port INCOMING request from
the internet and FORWARD it to "inside the LAN/WAN/behind router".



If that failed, there are a few possible reasons. Do a "ping jlpupcam.no-ip.info" and
see if you get a response and see what IP is returned by DNS (note: sometimes firewalls
block ping requests.)

***
Ping worked. <1 ms on all 4 packets.


Once you have the IP,
try "telnet <ipadd> 8080" and see what you get. That should fail as well.

***
Connect failed.

Now
verify that the IP you got from your ping is the actual Internet IP your computer is
using (try http://www.whatsmyip.org/). If it's not the same, then the Internet DNS does
not have the correct IP address for your host name.

***
The DNS does have the new (today's) dynamic IP address of my machine as seen "outside the
router"??


Another possibility is that port 8080 is being blocked by your firewall. From within
your LAN (behind your firewall) do a "telnet <privateIP> 8080" and see if you get a
response.

***
"Response?"

Telnet screen went blank implying the telnet 192.168.1.64 8080 worked. What does that
mean?


If yes, then it's likely a firewall issue. That's where
you'll probably need to investigate NAT port forwarding.

***
This still isn't remotely clear and I've been researching for upwards of 2 days now.

Further re: my PC environment.

Dynamic IP (TCPIP configured to obtain IP and DNS addresses automatically).
Speedstream 5100b modem with a single-port?? router INSIDE.

I played with XP firewall yesterday and put all the TCP/UDP port 80 AND port 8080 stuff
everywhere and now can't see the stream from work (but used to be able to).

From what I've read, one CAN access the my modem's internal router via http://192.168.1.1
(modem itself is 192.168.0.1). But, evidently ONLY if you have a STATIC IP address
configured. SO, I guess I should change TCPIP for my Network LAN connection to Static,
and try the 1.1 address in IE and hopefully pull up router stuff.

I appreciate everyone's efforts in all this but I'm still far away from getting this to
work (and understanding networks). Why is it that NO newsgroup nor website nor even tech.
support at the dynip providers can figure out this SIMPLE problem?

JL



"Jim Lewandowski" <jlewand@xxxxxxxxxxxxxxxxxxx> wrote in message
news:a9UFf.27798$F_3.15095@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Telnet jlpupcam.no-ip.info 8080 gets "Connect failed". What does that tell us?

This stuff seems SO basic, but I can't find any doc. that REALLY explains all this.
The bookstore is the last hope.

JL


"Mike Lowery" <selfspam@xxxxxxxxxxxxxxxx> wrote in message
news:%234oXGezKGHA.3352@xxxxxxxxxxxxxxxxxxxxxxx
machine name = Internet host name including DNS suffix (mysite.no-ip.com)

The "funky LAN-ish name" is not visible on the Internet.

"Jim Lewandowski" <jlewand@xxxxxxxxxxxxxxxxxxx> wrote in message
news:c6SEf.22062$Jd.12290@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ticket opened at no-ip and no response yet. I made it clear I'm using port 8080.

What is "machine name" in the line below? Is that the funky "LAN-ish" name that's
mnemonic? Please clarify, you can't assume I know what you mean.

JL


"Mike Lowery" <selfspam@xxxxxxxxxxxxxxxx> wrote in message
news:%23VnWL%23NKGHA.2012@xxxxxxxxxxxxxxxxxxxxxxx
I think some of these free DNS sites will only work for HTTP (port 80) redirects.
They strip off any port appended to the URL. As a test, go to your work PC and type
"telnet machine-name 8080" and see if you get a connection. It should work, which
means the service is truncating the URLs it's sent.

"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