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


"Jim Lewandowski" <jlewand@xxxxxxxxxxxxxxxxxxx> wrote in message
news:IG9Gf.28214$F_3.18662@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

"Mike Lowery" <selfspam@xxxxxxxxxxxxxxxx> wrote in message
news:uR1SbZALGHA.3460@xxxxxxxxxxxxxxxxxxxxxxx

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.

Good.

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

***
Connect failed.

Bad.

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"??

Good.


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?

It means you have a firewall blocking port 8080 from the outside, which is
exactly what I said below.

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.

It's pretty clear to me based on the steps you just performed above. If you
need more clarification, go to http://www.grc.com/ and run the ShieldsUp test.
I'm sure you'll find port 8080 (and probably all others) is not reachable.

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).

Just make an exception in the firewall for WME and call it good. Stop playing
around with port numbers. You shouldn't even have this firewall turned on until
AFTER you get things working correctly.

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?

Because it's YOUR "simple" network and only YOU know how it's been
misconfigured. Don't blame us for not knowing.



.

Relevant Pages

  • Website setup questions.
    ... Create firewall rule to direct HTTP port 80 to the SBS External NIC ... Create firewall rule to point DNS port 53 to the SBS External NIC ... NICS to get this request to not timeout or be refused. ...
    (microsoft.public.windows.server.sbs)
  • RE: strange traffic on UDP port 53
    ... Replies to DNS queries should be coming FROM port 53, ... > found a similar problem with packets being stopped by our firewall. ... The destination IP is our mail server (not ...
    (Incidents)
  • Re: WME --> Windows Media Player - URLs that function/dont from home/work
    ... sometimes firewalls block ping requests.) ... Another possibility is that port 8080 is being blocked by your firewall. ... Because it's YOUR "simple" network and only YOU know how it's been ...
    (microsoft.public.windowsmedia.encoder)
  • Re: WME --> Windows Media Player - URLs that function/dont from home/work
    ... see if you get a response and see what IP is returned by DNS (note: ... firewalls block ping requests.) ... Another possibility is that port 8080 is being blocked by your firewall. ...
    (microsoft.public.windowsmedia.encoder)
  • Re: port 53, please help!
    ... >> port 53 as blocked. ... >to folks with a Win98 connected thru a firewall to internet. ... find out the IP addresses of all your DNS servers. ...
    (comp.security.firewalls)
Loading