using EWA on a machine configured as client?

[lazyslacker]

I have a server running 2.0.3 and the latest EWA, and I have a client machine connected to it, also running 2.0.3. The regular NPVR interface works fine and the EWA interface to the server also works fine. However, I'm not able to access the EWA server (http://localhost:8866/guide.aspx) on the client, only the server. Is the EWA automatically disabled regardless of any settings if it's in client mode? If so, why? and if not, how can I access EWA on my client machine? I'm wanting to do this because my client machine is a much faster computer, capable of transcoding for purposes of streaming over the web with little effort. My server on the other hand is an old machine. The only reason it is able to handle streaming the HD and SD content at all is because of the hardware decoders in my capture cards. It doesn't do transcoding to web-streamable data very well.

Hopefully this problem/question is easy enough to understand. The problem is just that I'm unable to access EWA on the client machine when client mode is turned on. It just never loads the page, instead constantly says "waiting for localhost". It never times out.

Thanks!!

[UncleJohnsBand]

I have a server running 2.0.3 and the latest EWA, and I have a client machine connected to it, also running 2.0.3. The regular NPVR interface works fine and the EWA interface to the server also works fine. However, I'm not able to access the EWA server (http://localhost:8866/guide.aspx) on the client, only the server. Is the EWA automatically disabled regardless of any settings if it's in client mode? If so, why? and if not, how can I access EWA on my client machine? I'm wanting to do this because my client machine is a much faster computer, capable of transcoding for purposes of streaming over the web with little effort. My server on the other hand is an old machine. The only reason it is able to handle streaming the HD and SD content at all is because of the hardware decoders in my capture cards. It doesn't do transcoding to web-streamable data very well.

Hopefully this problem/question is easy enough to understand. The problem is just that I'm unable to access EWA on the client machine when client mode is turned on. It just never loads the page, instead constantly says "waiting for localhost". It never times out.

Thanks!!

EWA/NEWA was never designed to be a client application....it is only available from the server.

[Sykor]

However, I'm not able to access the EWA server (http://localhost:8866/guide.aspx) on the client, only the server. [...] how can I access EWA on my client machine? [...]
Thanks!!

The "localhost" part, means the computer will try connecting to itself (using the loopback ip 127.0.0.1). Since the EWA is only meaningful on the server, it will not respond on a client. You have to open it on the server itself. Let's say your server's LAN ip is 192.168.0.150, you point your browser to http://192.168.0.150:8866/guide.aspx.

Although your second purpose, using the client for web-streaming, won't work. Over the internet, you would always have to forward it (router wise) to EWA on your server. So your client would never be called into action.

[UncleJohnsBand]

As stated above....you can reach NEWA from the client by using the IP address or the machine name of the server.....for example: http://your-server-name:8866/npvr/ or http://192.168.1.14:8866/npvr/