2007-03-16, 10:05 AM
jim08127 Wrote: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 Wrote: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?
jim08127 Wrote: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 Wrote:Got it.
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.
My understanding is that Bwangster has EWA and VLC on 443....thus the conflict.
You can block ports on local machines, my office does this for some known high trojan use ports, so it is very easy to have issues from work even if you have any number of ports at home to configure EWA and VLC on.
Bottom line is you need two ports......the client pc will be communication to EWA anb VLC on two different ports......one for the EWA traffic and one for the VLC traffic.
Intel Core i7 @ 4.00GHz Skylake 14nm
ASUSTeK COMPUTER INC. Z170-DELUXE
Windows 10 Pro x64
PVR Software: NPVR 5.1.1
SiliconDust HDHomeRun HDHR5-4US Connect Quatro 4 Channel Tuner
Roku Ultra
2 PCH A-100's
ASUSTeK COMPUTER INC. Z170-DELUXE
Windows 10 Pro x64
PVR Software: NPVR 5.1.1
SiliconDust HDHomeRun HDHR5-4US Connect Quatro 4 Channel Tuner
Roku Ultra
2 PCH A-100's