What is going on...

[Bwangster12]

So where it stands now... tomorrow at work I will try to do a cmd netstat -b and exit/close a program that I don't need and try using that port. All the ports on my work computer are stealthed. 80, 8080... do not work. Maybe disabling/exiting a program I have running will free up the port that it was using?

[jim08127]

When you click on the launch button a file is generated and sent to your PC by EWA that tells the player (VLC or WMP) where the stream can be found. That is why that works.

When you try to open that stream file you are trying to connect to VLC but since you only have one port open and both VLC and EWA are tyring to use it you can not get the stream.

UncleJohn, this doesn't make sense to me.

I would think EWA is just a web page it doesn't use the streamer port, only vlc on the server and client do. EWA on the client must send a launch command but that is received on the server and run via .net code. Then the server .net code launches vlc server passing the ip address and file information, protocol, port to use etc. Bottom line with EWA only one port is needed on the client since .net removes the need for http vlc control panel. Sorry if any of my thinking is in ignorance. Just tryin to help.

I still think he should try a different transport, and go back to default port as this can be changed from the office with EWA, but no indication this has been attempted.

Secondly open browser connection options and check if the browser at work is using a proxy server. Hence blocking outbound http on unusual ports.

[FirstTeamOPS]

Bottom line with EWA only one port is needed on the client since .net removes the need for http vlc control panel.

No. EWA needs one port, the VLC needs one port. They're two completely different services. You cannot have two different services running on the same port. Even running multiple instances of the same service on one port won't work. The programs will collide because neither knows what to because their expecting to be the only thing monitoring that port. Some programs are smart enough to see that the port is already opened (being monitored) and will error out. Ultimately, it will result in undesired and unexpected behavior... to keep it simple.

[UncleJohnsBand]

No. EWA needs one port, the VLC needs one port. They're two completely different services. You cannot have two different services running on the same port. Even running multiple instances of the same service on one port won't work. The programs will collide because neither knows what to because their expecting to be the only thing monitoring that port. Some programs are smart enough to see that the port is already opened (being monitored) and will error out. Ultimately, it will result in undesired and unexpected behavior... to keep it simple.

Exactly.

[jim08127]

No. EWA needs one port, the VLC needs one port. They're two completely different services. You cannot have two different services running on the same port. Even running multiple instances of the same service on one port won't work. The programs will collide because neither knows what to because their expecting to be the only thing monitoring that port. Some programs are smart enough to see that the port is already opened (being monitored) and will error out. Ultimately, it will result in undesired and unexpected behavior... to keep it simple.

Well ok. But I'm still confused. You must be talking about the server not the client?

[jim08127]

I guess I know what you mean that it is two ports. The server puts EWA on port 7647 by default. So the client gets the web page there, but he is obviously not having a problem doing that. Then he says he has tried port 443 and port 8080 for the streamer. Port 8080 is unavailable to stream on because vlc serves up a control panel there. That would be a conflict. 443 should be fine if its not blocked by a firewall.

I believe most firewalls do not block outbound http on any port unless the administrator is very anal or the company has super strict security. Thats the main point I am making, the stream is using http and gets routed to the right node on the private LAN automatically at my office therefore its not like the firewall at work has to be specially opened for all inbound traffic on a port. It is being preceded by an http outbound packet so the router knows where to send the inbound.

[jim08127]

So Bwangster, did you change the EWA port in the gbpvr config misc tab? If so what are you using there?

On the server side there are two ports you configure (or leave at defaults) and you have to set the home router to forward both to the server. defaults are 7647 for EWA and 7648 for streaming. Is the problem that you can't even open the EWA web page when it is left at 7647?

[FirstTeamOPS]

You must be talking about the server not the client?

Generally yes. The client PC doesn't care what ports are being used for the outgoing data. When you run into problems is when you run into an active firewall (blocks data in both directions as are on most corp networks). The server does care what port the data comes in as.

What I think you're trying to say (correct me if I'm wrong) is that with one open port at work, you can use that one port to direct all communications to the server. In other words:
[Work PC (EWA/VLC 1 port)] <---internet---> [Server PC (EWA/VLC many ports)]
You cannot do this.

I can see what (I think) you're saying and to some extent how that can be reasoned out. However, on the server they're running as different services so the client will use different ports for the outgoing connection to the server.

[jim08127]

Generally yes. The client PC doesn't care what ports are being used for the outgoing data. When you run into problems is when you run into an active firewall (blocks data in both directions as are on most corp networks). The server does care what port the data comes in as.

What I think you're trying to say (correct me if I'm wrong) is that with one open port at work, you can use that one port to direct all communications to the server. In other words:
[Work PC (EWA/VLC 1 port)] <---internet---> [Server PC (EWA/VLC many ports)]
You cannot do this.

I can see what (I think) you're saying and to some extent how that can be reasoned out. However, they're different services so they will use different ports for the outgoing connection to the server.

I was talking about what ports need to be specially configured at a router on the client side. Answer: none.

I know you can't have the web page served up on the same port as the streamed video.

I didn't connect his problem as not even being able to open EWA in a browser at the default setting. Thats a very strict router if thats the case. And when he was describing the ports as EWA and VLC I thought he was changing the vlc server control panel port from the 8080 setting somehow (I don't know where that could be configured) and was describing the streaming port as EWA. I guess I had a brain fart.

I've seen a strict outgoing network, they used a proxy server and blocked all outgoing traffic that didn't go through the proxy. If thats not what he has at work, then routers generally allow outgoing http which should let him open EWA on the default port 7647.

[FirstTeamOPS]

Got it.

I've seen a strict outgoing network, they used a proxy server and blocked all outgoing traffic that didn't go through the proxy.

Yea, mine does at work but we have tight regulations, the government, and customer data to worry about. We have a similar setup. Basically everything that isn't http web data is blocked on our network. No streaming media, pinging, remote sessions... you name it.