Jump to content



Photo

Can't connect to VLC media player video stream from remote PC


  • Please log in to reply
16 replies to this topic

#1 Elliot B.

Elliot B.

    Over 13 years on Neowin

  • Tech Issues Solved: 4
  • Joined: 16-August 01
  • Location: West Midlands, UK
  • OS: Windows 8.1
  • Phone: Samsung Galaxy S5

Posted 21 August 2014 - 08:19

I've set it correctly up VLC media player on primary PC (I've followed many guides, this part seems hard to go wrong).

 

When I go to the second PC, Media > Open network stream > and enter my IP (which I found on my primary PC using www.whatismyipaddress.com) followed by :8080, I instantly get:

 

"Your input can't be opened:
VLC is unable to open the MRL '<IP>:8080'. Check the log for details."

 

I have no firewall enabled on my PC or router.

 

Any ideas?




#2 +BudMan

BudMan

    Neowinian Senior

  • Tech Issues Solved: 106
  • Joined: 04-July 02
  • Location: Schaumburg, IL
  • OS: Win7, Vista, 2k3, 2k8, XP, Linux, FreeBSD, OSX, etc. etc.

Posted 21 August 2014 - 11:24

"and enter my IP (which I found on my primary PC using www.whatismyipaddress.com)"

 

Why would you use your public IP when I have to assume these computers are on the same local network when you say go to the second PC.

 

From a cmd prompt do an ipconfig this will show you your local IP address.   If you are trying to actually do this over the internet, then you would have to forward ports on your router.

 

ipaddress.png

 

You should see an address that starts with 192.168.x.x or 10.x.x.x or 172.16-31.x.x -- this would be your private IP address that your router hands out..  Only when you go too the internet do all of your machines share that public IP address you see when you go to whatsmyip.com



#3 OP Elliot B.

Elliot B.

    Over 13 years on Neowin

  • Tech Issues Solved: 4
  • Joined: 16-August 01
  • Location: West Midlands, UK
  • OS: Windows 8.1
  • Phone: Samsung Galaxy S5

Posted 21 August 2014 - 11:29

"and enter my IP (which I found on my primary PC using www.whatismyipaddress.com)"

 

Why would you use your public IP when I have to assume these computers are on the same local network when you say go to the second PC.

 

From a cmd prompt do an ipconfig this will show you your local IP address.   If you are trying to actually do this over the internet, then you would have to forward ports on your router.

 

attachicon.gifipaddress.png

 

You should see an address that starts with 192.168.x.x or 10.x.x.x or 172.16-31.x.x -- this would be your private IP address that your router hands out..  Only when you go too the internet do all of your machines share that public IP address you see when you go to whatsmyip.com

You presumed.

 

I'm in a different city.

 

Also, the PC's IP is in DMZ mode on the router.



#4 +BudMan

BudMan

    Neowinian Senior

  • Tech Issues Solved: 106
  • Joined: 04-July 02
  • Location: Schaumburg, IL
  • OS: Win7, Vista, 2k3, 2k8, XP, Linux, FreeBSD, OSX, etc. etc.

Posted 21 August 2014 - 11:38

You should make mention of that then - well if your in the DMZ mode, then its quite possible your isp blocking that port, 8080 is a common proxy port and quiet often blocked.

 

Quite simple to do a sniff on your machine to see if you even see the traffic get there - wireshark for example.  Check it with canyouseeme.org - if your listening and its not block then you should see it

 

canyouseeme.png

 

I listen on 443 for vpn connection, so as you can see that shows open

 

You put your box in the dmz and don't run a firewall on it?  That is not a good idea!!  Do a scan say here https://www.grc.com/shieldsup What do you see for open on your whatsmyip.com IP address?

scan.png

 

That is the common ports test - what does your show - if dmz, anything listening on your box showing with netstat -an should be there.

 

exmaple

 

netstat.png

 

Do you see your 8080 there?



#5 OP Elliot B.

Elliot B.

    Over 13 years on Neowin

  • Tech Issues Solved: 4
  • Joined: 16-August 01
  • Location: West Midlands, UK
  • OS: Windows 8.1
  • Phone: Samsung Galaxy S5

Posted 21 August 2014 - 13:25

ShieldsUP shows, "THE EQUIPMENT AT THE TARGET IP ADDRESS DID NOT RESPOND TO OUR UPnP PROBES! (That's good news!)"
 
CanYouSeeMe.org shows, "Error: I could not see your service on 87.115.<edit> on port (8080). Reason: Connection refused"
 
netstat -an shows (I'm not sure how best to format this on the forum and it's too long for a screenshot):

C:\Windows\system32>netstat -an Active Connections  Proto  Local Address          Foreign Address        State  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING  TCP    0.0.0.0:554            0.0.0.0:0              LISTENING  TCP    0.0.0.0:1991           0.0.0.0:0              LISTENING  TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING  TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING  TCP    0.0.0.0:9001           0.0.0.0:0              LISTENING  TCP    0.0.0.0:10243          0.0.0.0:0              LISTENING  TCP    0.0.0.0:10245          0.0.0.0:0              LISTENING  TCP    0.0.0.0:32400          0.0.0.0:0              LISTENING  TCP    0.0.0.0:32401          0.0.0.0:0              LISTENING  TCP    0.0.0.0:32469          0.0.0.0:0              LISTENING  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING  TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING  TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING  TCP    0.0.0.0:49201          0.0.0.0:0              LISTENING  TCP    0.0.0.0:49239          0.0.0.0:0              LISTENING  TCP    0.0.0.0:49395          0.0.0.0:0              LISTENING  TCP    127.0.0.1:5939         0.0.0.0:0              LISTENING  TCP    127.0.0.1:5939         127.0.0.1:49178        ESTABLISHED  TCP    127.0.0.1:5939         127.0.0.1:54641        TIME_WAIT  TCP    127.0.0.1:5939         127.0.0.1:55306        ESTABLISHED  TCP    127.0.0.1:49178        127.0.0.1:5939         ESTABLISHED  TCP    127.0.0.1:49202        0.0.0.0:0              LISTENING  TCP    127.0.0.1:49217        127.0.0.1:49218        ESTABLISHED  TCP    127.0.0.1:49218        127.0.0.1:49217        ESTABLISHED  TCP    127.0.0.1:49219        127.0.0.1:49220        ESTABLISHED  TCP    127.0.0.1:49220        127.0.0.1:49219        ESTABLISHED  TCP    127.0.0.1:49221        127.0.0.1:49222        ESTABLISHED  TCP    127.0.0.1:49222        127.0.0.1:49221        ESTABLISHED  TCP    127.0.0.1:49223        127.0.0.1:49224        ESTABLISHED  TCP    127.0.0.1:49224        127.0.0.1:49223        ESTABLISHED  TCP    127.0.0.1:49225        127.0.0.1:49226        ESTABLISHED  TCP    127.0.0.1:49226        127.0.0.1:49225        ESTABLISHED  TCP    127.0.0.1:49227        127.0.0.1:49228        ESTABLISHED  TCP    127.0.0.1:49228        127.0.0.1:49227        ESTABLISHED  TCP    127.0.0.1:49229        127.0.0.1:49230        ESTABLISHED  TCP    127.0.0.1:49230        127.0.0.1:49229        ESTABLISHED  TCP    127.0.0.1:49231        127.0.0.1:49232        ESTABLISHED  TCP    127.0.0.1:49232        127.0.0.1:49231        ESTABLISHED  TCP    127.0.0.1:49233        127.0.0.1:49234        ESTABLISHED  TCP    127.0.0.1:49234        127.0.0.1:49233        ESTABLISHED  TCP    127.0.0.1:49235        127.0.0.1:49236        ESTABLISHED  TCP    127.0.0.1:49236        127.0.0.1:49235        ESTABLISHED  TCP    127.0.0.1:49240        127.0.0.1:49241        ESTABLISHED  TCP    127.0.0.1:49241        127.0.0.1:49240        ESTABLISHED  TCP    127.0.0.1:49253        127.0.0.1:49254        ESTABLISHED  TCP    127.0.0.1:49254        127.0.0.1:49253        ESTABLISHED  TCP    127.0.0.1:49255        127.0.0.1:49256        ESTABLISHED  TCP    127.0.0.1:49256        127.0.0.1:49255        ESTABLISHED  TCP    127.0.0.1:49257        127.0.0.1:49258        ESTABLISHED  TCP    127.0.0.1:49258        127.0.0.1:49257        ESTABLISHED  TCP    127.0.0.1:49259        127.0.0.1:49260        ESTABLISHED  TCP    127.0.0.1:49260        127.0.0.1:49259        ESTABLISHED  TCP    127.0.0.1:49261        127.0.0.1:49262        ESTABLISHED  TCP    127.0.0.1:49262        127.0.0.1:49261        ESTABLISHED  TCP    127.0.0.1:49267        127.0.0.1:49268        ESTABLISHED  TCP    127.0.0.1:49268        127.0.0.1:49267        ESTABLISHED  TCP    127.0.0.1:49269        127.0.0.1:49270        ESTABLISHED  TCP    127.0.0.1:49270        127.0.0.1:49269        ESTABLISHED  TCP    127.0.0.1:49396        127.0.0.1:49397        ESTABLISHED  TCP    127.0.0.1:49397        127.0.0.1:49396        ESTABLISHED  TCP    127.0.0.1:54781        127.0.0.1:54780        TIME_WAIT  TCP    127.0.0.1:55163        127.0.0.1:55162        TIME_WAIT  TCP    127.0.0.1:55166        127.0.0.1:55165        TIME_WAIT  TCP    127.0.0.1:55169        127.0.0.1:55168        TIME_WAIT  TCP    127.0.0.1:55173        127.0.0.1:55172        TIME_WAIT  TCP    127.0.0.1:55175        127.0.0.1:55174        TIME_WAIT  TCP    127.0.0.1:55177        127.0.0.1:55176        TIME_WAIT  TCP    127.0.0.1:55179        127.0.0.1:55178        TIME_WAIT  TCP    127.0.0.1:55182        127.0.0.1:55181        TIME_WAIT  TCP    127.0.0.1:55186        127.0.0.1:55184        TIME_WAIT  TCP    127.0.0.1:55187        127.0.0.1:55185        TIME_WAIT  TCP    127.0.0.1:55190        127.0.0.1:55191        TIME_WAIT  TCP    127.0.0.1:55191        127.0.0.1:55190        TIME_WAIT  TCP    127.0.0.1:55192        127.0.0.1:55193        TIME_WAIT  TCP    127.0.0.1:55193        127.0.0.1:55192        TIME_WAIT  TCP    127.0.0.1:55194        127.0.0.1:55195        TIME_WAIT  TCP    127.0.0.1:55195        127.0.0.1:55194        TIME_WAIT  TCP    127.0.0.1:55197        127.0.0.1:55196        TIME_WAIT  TCP    127.0.0.1:55200        127.0.0.1:55199        TIME_WAIT  TCP    127.0.0.1:55201        127.0.0.1:55198        TIME_WAIT  TCP    127.0.0.1:55205        127.0.0.1:55204        TIME_WAIT  TCP    127.0.0.1:55210        127.0.0.1:55208        TIME_WAIT  TCP    127.0.0.1:55211        127.0.0.1:55209        TIME_WAIT  TCP    127.0.0.1:55215        127.0.0.1:55214        TIME_WAIT  TCP    127.0.0.1:55218        127.0.0.1:55217        TIME_WAIT  TCP    127.0.0.1:55221        127.0.0.1:55220        TIME_WAIT  TCP    127.0.0.1:55223        127.0.0.1:55222        TIME_WAIT  TCP    127.0.0.1:55225        127.0.0.1:55224        TIME_WAIT  TCP    127.0.0.1:55227        127.0.0.1:55226        TIME_WAIT  TCP    127.0.0.1:55229        127.0.0.1:55228        TIME_WAIT  TCP    127.0.0.1:55237        127.0.0.1:55236        TIME_WAIT  TCP    127.0.0.1:55239        127.0.0.1:55238        TIME_WAIT  TCP    127.0.0.1:55240        127.0.0.1:32400        TIME_WAIT  TCP    127.0.0.1:55242        127.0.0.1:55241        TIME_WAIT  TCP    127.0.0.1:55245        127.0.0.1:55244        TIME_WAIT  TCP    127.0.0.1:55249        127.0.0.1:55248        TIME_WAIT  TCP    127.0.0.1:55251        127.0.0.1:55250        TIME_WAIT  TCP    127.0.0.1:55253        127.0.0.1:55252        TIME_WAIT  TCP    127.0.0.1:55255        127.0.0.1:55254        TIME_WAIT  TCP    127.0.0.1:55256        127.0.0.1:55257        ESTABLISHED  TCP    127.0.0.1:55257        127.0.0.1:55256        ESTABLISHED  TCP    127.0.0.1:55261        127.0.0.1:55259        TIME_WAIT  TCP    127.0.0.1:55262        127.0.0.1:55260        TIME_WAIT  TCP    127.0.0.1:55266        127.0.0.1:55265        TIME_WAIT  TCP    127.0.0.1:55270        127.0.0.1:55268        TIME_WAIT  TCP    127.0.0.1:55271        127.0.0.1:55269        TIME_WAIT  TCP    127.0.0.1:55275        127.0.0.1:55274        TIME_WAIT  TCP    127.0.0.1:55277        127.0.0.1:55278        TIME_WAIT  TCP    127.0.0.1:55278        127.0.0.1:55277        TIME_WAIT  TCP    127.0.0.1:55280        127.0.0.1:55279        TIME_WAIT  TCP    127.0.0.1:55282        127.0.0.1:55281        TIME_WAIT  TCP    127.0.0.1:55284        127.0.0.1:55283        TIME_WAIT  TCP    127.0.0.1:55287        127.0.0.1:55285        TIME_WAIT  TCP    127.0.0.1:55288        127.0.0.1:55286        TIME_WAIT  TCP    127.0.0.1:55290        127.0.0.1:55292        TIME_WAIT  TCP    127.0.0.1:55291        127.0.0.1:55289        TIME_WAIT  TCP    127.0.0.1:55292        127.0.0.1:55290        TIME_WAIT  TCP    127.0.0.1:55294        127.0.0.1:55293        TIME_WAIT  TCP    127.0.0.1:55297        127.0.0.1:55296        TIME_WAIT  TCP    127.0.0.1:55301        127.0.0.1:55299        TIME_WAIT  TCP    127.0.0.1:55302        127.0.0.1:55300        TIME_WAIT  TCP    127.0.0.1:55306        127.0.0.1:5939         ESTABLISHED  TCP    127.0.0.1:55309        127.0.0.1:55308        TIME_WAIT  TCP    192.168.1.71:139       0.0.0.0:0              LISTENING  TCP    192.168.1.71:5001      0.0.0.0:0              LISTENING  TCP    192.168.1.71:49163     157.55.236.134:443     ESTABLISHED  TCP    192.168.1.71:49212     185.31.18.133:443      CLOSE_WAIT  TCP    192.168.1.71:54782     192.168.1.64:8008      TIME_WAIT  TCP    192.168.1.71:54930     92.51.156.76:5938      ESTABLISHED  TCP    192.168.1.71:54948     173.194.41.167:80      TIME_WAIT  TCP    192.168.1.71:55021     4.79.142.202:443       TIME_WAIT  TCP    192.168.1.71:55022     4.79.142.192:443       TIME_WAIT  TCP    192.168.1.71:55023     4.79.142.202:443       TIME_WAIT  TCP    192.168.1.71:55024     4.79.142.192:443       TIME_WAIT  TCP    192.168.1.71:55026     4.79.142.202:443       TIME_WAIT  TCP    192.168.1.71:55091     173.194.41.186:80      TIME_WAIT  TCP    192.168.1.71:55092     74.125.195.157:80      TIME_WAIT  TCP    192.168.1.71:55094     64.12.106.135:80       TIME_WAIT  TCP    192.168.1.71:55171     192.168.1.254:80       TIME_WAIT  TCP    192.168.1.71:55233     192.168.1.254:80       TIME_WAIT  TCP    192.168.1.71:55234     192.168.1.71:2869      TIME_WAIT  TCP    192.168.1.71:55235     192.168.1.71:32469     TIME_WAIT  TCP    192.168.1.71:55247     134.170.104.152:443    ESTABLISHED  TCP    192.168.1.71:55258     192.168.1.64:8008      ESTABLISHED  TCP    192.168.1.71:55305     37.252.232.5:5938      ESTABLISHED  TCP    192.168.1.71:55307     168.63.124.19:443      TIME_WAIT  TCP    [::]:135               [::]:0                 LISTENING  TCP    [::]:445               [::]:0                 LISTENING  TCP    [::]:554               [::]:0                 LISTENING  TCP    [::]:2869              [::]:0                 LISTENING  TCP    [::]:5357              [::]:0                 LISTENING  TCP    [::]:10243             [::]:0                 LISTENING  TCP    [::]:10245             [::]:0                 LISTENING  TCP    [::]:49152             [::]:0                 LISTENING  TCP    [::]:49153             [::]:0                 LISTENING  TCP    [::]:49154             [::]:0                 LISTENING  TCP    [::]:49155             [::]:0                 LISTENING  TCP    [::]:49156             [::]:0                 LISTENING  TCP    [::]:49157             [::]:0                 LISTENING  TCP    [::]:49201             [::]:0                 LISTENING  UDP    0.0.0.0:500            *:*  UDP    0.0.0.0:1900           *:*  UDP    0.0.0.0:1900           *:*  UDP    0.0.0.0:3702           *:*  UDP    0.0.0.0:3702           *:*  UDP    0.0.0.0:3702           *:*  UDP    0.0.0.0:3702           *:*  UDP    0.0.0.0:3702           *:*  UDP    0.0.0.0:3702           *:*  UDP    0.0.0.0:3964           *:*  UDP    0.0.0.0:4500           *:*  UDP    0.0.0.0:5004           *:*  UDP    0.0.0.0:5005           *:*  UDP    0.0.0.0:5355           *:*  UDP    0.0.0.0:12696          *:*  UDP    0.0.0.0:32410          *:*  UDP    0.0.0.0:32413          *:*  UDP    0.0.0.0:32414          *:*  UDP    0.0.0.0:51413          *:*  UDP    0.0.0.0:51414          *:*  UDP    0.0.0.0:56368          *:*  UDP    0.0.0.0:58213          *:*  UDP    0.0.0.0:60868          *:*  UDP    0.0.0.0:60874          *:*  UDP    0.0.0.0:61117          *:*  UDP    0.0.0.0:61122          *:*  UDP    127.0.0.1:1900         *:*  UDP    127.0.0.1:44301        *:*  UDP    127.0.0.1:60873        *:*  UDP    127.0.0.1:61110        *:*  UDP    127.0.0.1:61112        *:*  UDP    192.168.1.71:137       *:*  UDP    192.168.1.71:138       *:*  UDP    192.168.1.71:1900      *:*  UDP    192.168.1.71:60872     *:*  UDP    192.168.1.71:61111     *:*  UDP    192.168.1.71:61113     *:*  UDP    [::]:500               *:*  UDP    [::]:3702              *:*  UDP    [::]:3702              *:*  UDP    [::]:3702              *:*  UDP    [::]:3702              *:*  UDP    [::]:3702              *:*  UDP    [::]:3702              *:*  UDP    [::]:4500              *:*  UDP    [::]:5004              *:*  UDP    [::]:5005              *:*  UDP    [::]:5355              *:*  UDP    [::]:51415             *:*  UDP    [::]:51416             *:*  UDP    [::]:56369             *:*  UDP    [::]:60869             *:*  UDP    [::]:60875             *:*  UDP    [::1]:1900             *:*  UDP    [::1]:60871            *:*  UDP    [fe80::c96c:ce03:d38b:a54c%3]:546  *:*
  UDP    [fe80::c96c:ce03:d38b:a54c%3]:546  *:*
  UDP    [fe80::c96c:ce03:d38b:a54c%3]:1900  *:*
  UDP    [fe80::c96c:ce03:d38b:a54c%3]:60870  *:*
C:\Windows\system32>



#6 +Brando212

Brando212

    Neowinian Senior

  • Tech Issues Solved: 17
  • Joined: 15-April 10
  • Location: Omaha, NE
  • OS: Windows 8.1
  • Phone: Sony Xperia ZL, Nokia Lumia 925

Posted 21 August 2014 - 13:32

it does sound like 8080 might be blocked at ISP level then. try changing VLC to a higher port (the 10k or 20k range is usually the best for custom ports)



#7 OP Elliot B.

Elliot B.

    Over 13 years on Neowin

  • Tech Issues Solved: 4
  • Joined: 16-August 01
  • Location: West Midlands, UK
  • OS: Windows 8.1
  • Phone: Samsung Galaxy S5

Posted 21 August 2014 - 13:36

it does sound like 8080 might be blocked at ISP level then. try changing VLC to a higher port (the 10k or 20k range is usually the best for custom ports)

I tried 21234 but it also instantly came up with the error in the first post :(



#8 +Brando212

Brando212

    Neowinian Senior

  • Tech Issues Solved: 17
  • Joined: 15-April 10
  • Location: Omaha, NE
  • OS: Windows 8.1
  • Phone: Sony Xperia ZL, Nokia Lumia 925

Posted 21 August 2014 - 13:39

I tried 21234 but it also instantly came up with the error in the first post sad.png

and you're certain that your firewall isn't on? double check that the windows firewall didn't get turned back on

 

also even though the computer is set up DMZ on your router I'd try setting up a port forward rule on the router. i've seen dmz not work correctly before



#9 OP Elliot B.

Elliot B.

    Over 13 years on Neowin

  • Tech Issues Solved: 4
  • Joined: 16-August 01
  • Location: West Midlands, UK
  • OS: Windows 8.1
  • Phone: Samsung Galaxy S5

Posted 21 August 2014 - 13:43

and you're certain that your firewall isn't on? double check that the windows firewall didn't get turned back on

 

also even though the computer is set up DMZ on your router I'd try setting up a port forward rule on the router. i've seen dmz not work correctly before

Windows Firewall is disabled on the serving PC and on it's router.

 

I'll try and manually forward the port when I next get a chance, tomorrow :)



#10 +BudMan

BudMan

    Neowinian Senior

  • Tech Issues Solved: 106
  • Joined: 04-July 02
  • Location: Schaumburg, IL
  • OS: Win7, Vista, 2k3, 2k8, XP, Linux, FreeBSD, OSX, etc. etc.

Posted 21 August 2014 - 14:05

you don't do the UPnP check - you need to click one of the buttons on that page to scan either common ports, all ports below 1056 or custom ports

probe.png

But I don't even seeing you listening on 8080?

LISTENING TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING TCP 0.0.0.0:9001

It should be listed between there. I did a search and didn't see 8080 listed in your post. Impossible to connect to a port, even if your in the "dmz" if your not even listening on the port ;) Your sure VLC is listening on 8080, if so then it would be listed in netstat -an

streaming.png

if you use -anb the b will show you the exe listing

anb.png

#11 sc302

sc302

    Neowinian Senior

  • Tech Issues Solved: 35
  • Joined: 12-July 05
  • Location: NJ, USA

Posted 21 August 2014 - 14:09

use plex.  it is a much better solution and way easy to setup....just run the installer then point it to where you store your movies/media.

https://plex.tv/

 

It almost sounds like you are inside your network not outside. 



#12 OP Elliot B.

Elliot B.

    Over 13 years on Neowin

  • Tech Issues Solved: 4
  • Joined: 16-August 01
  • Location: West Midlands, UK
  • OS: Windows 8.1
  • Phone: Samsung Galaxy S5

Posted 21 August 2014 - 14:17

use plex.  it is a much better solution and way easy to setup....just run the installer then point it to where you store your movies/media.

https://plex.tv/

 

It almost sounds like you are inside your network not outside. 

The problem is, it's a work computer.

 

The boss doesn't mind me using extra software during my lunch breaks etc. (in this instance, I tried to stream TV shows from home using the zipped VLC media player package) but since I don't have admin, I can only use portable apps.



#13 +BudMan

BudMan

    Neowinian Senior

  • Tech Issues Solved: 106
  • Joined: 04-July 02
  • Location: Schaumburg, IL
  • OS: Win7, Vista, 2k3, 2k8, XP, Linux, FreeBSD, OSX, etc. etc.

Posted 21 August 2014 - 14:18

It almost sounds like you are inside your network not outside.

Thats what I thought - but he says he is trying to come from another city and his vlc box is in the router dmz, etc.

"but since I don't have admin, I can only use portable apps."

Huh??? So your vlc server serving up the files is at home, so what would that have to do with admin rights - I would assume you have admin rights at home.. Why don't you just bring you movies/media on a usb disk and plug it into your work computer to watch via sure a portable media player or even the built in media player

So home box is in the dmz of your home router, but don't show it listening on 8080 - was that output from your work or home vlc server box?

Work - is work just a home type router as well for their internet connection. Most work networks don't allow nonstandard outbound, ie for example 80, 443, 21 might be allowed but 8080 would be blocked outbound from the work network.

#14 sc302

sc302

    Neowinian Senior

  • Tech Issues Solved: 35
  • Joined: 12-July 05
  • Location: NJ, USA

Posted 21 August 2014 - 14:25

well there could be a couple of things that are blocking your way.  your home network is just one piece of the puzzle, but if your company is blocking outbound ports you are hosed.  In many situations they only block incoming, but to truly secure a site you would block most outgoing ports/protocols as well. 

 

I would test while at home with your phone as the remote site.  This will allow you to make changes on the fly until you get it right.  canyouseeme.org is a great way to see if your ports are in fact open at home, this is also a good one http://www.yougetsig...ols/open-ports/

 

also if your computer took a snooze, the ports will not be open.



#15 +BudMan

BudMan

    Neowinian Senior

  • Tech Issues Solved: 106
  • Joined: 04-July 02
  • Location: Schaumburg, IL
  • OS: Win7, Vista, 2k3, 2k8, XP, Linux, FreeBSD, OSX, etc. etc.

Posted 21 August 2014 - 14:37

"also if your computer took a snooze, the ports will not be open."

good point ;) Yeah if you setup your box before you leave for work, and 10 minutes latter it goes it to sleep your not going to be able to talk to it.

Lets be clear - the netstat you showed was from your "home" box? serving up the vlc stream you want to access from from work. If that is the case there is nothing listening on 8080, ie vlc is not streaming anything. So does not matter where you coming from, inside outside, ports blocked or not blocked you can not connect to something that is not listening.

Using your phone is a good test bed as suggested as a way to come from outside your network while your at home trying to setup the streaming. Another test to validate the streaming is working is access it via your local IP addresses from another computer on your local network. If that works - then you can work out why its not working from the public side.

Keeping in mind that 8080 normally a bad choice because its a common proxy port, and many isp will block this inbound and many work sites would block that outbound as its a simple way to circumvent say company browsing policies.