NEWA not starting?

[Reddwarf]

Since building a new htpc I have not been able to connect to it using NEWA or the gadget. The strange thing is that I don't see a Web.log in the logs directory. I have downloaded the latest installer, copied database and config file from the old installation where it worked and even copied the whole .\web directory from my testrig where newa works just fine, but no joy. Am I missing something very basic here??

[Reddwarf]

Can someone else try to connect to http://127.0.0.1:8866 and report the result and if you have the latest installer?

[gEd]

yes working fine. Have you tried disabling windows firewall to check if it is a IP routing issue?
what account is the recording service running under, system or a specific user?
have to got interact with desktop ticked?
(just checking the basics!)

[Reddwarf]

I have opened port 8866 in both ends, even tried to turn off the firewall to no avail. Recording service is running as my own user as it has always done. The strange thing is that my testrig has the exact same setup and newa is working fine there. Only difference is that my htpc has a fresh win7 ultimate installation. What might I have overlooked?

[Reddwarf]

BTW, the clients runs fine against the htpc so it is not a general network issue.

[gEd]

run

C:\Users\htpc>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:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1033 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1047 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:5800 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5900 0.0.0.0:0 LISTENING
TCP 0.0.0.0:7969 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8866 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8968 0.0.0.0:0 LISTENING
TCP 0.0.0.0:52100 0.0.0.0:0 LISTENING


to check you have a listener running on 8866

[Reddwarf]

Yep, 8866 seems to be there:

Code:

C:\Users\npvr>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:2869 0.0.0.0:0 LISTENING TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING TCP 0.0.0.0:7969 0.0.0.0:0 LISTENING TCP 0.0.0.0:8866 0.0.0.0:0 LISTENING TCP 0.0.0.0:8968 0.0.0.0:0 LISTENING TCP 0.0.0.0:10243 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:49166 0.0.0.0:0 LISTENING TCP 0.0.0.0:49167 0.0.0.0:0 LISTENING TCP 0.0.0.0:49168 0.0.0.0:0 LISTENING TCP 0.0.0.0:50300 0.0.0.0:0 LISTENING TCP 10.5.5.18:139 0.0.0.0:0 LISTENING TCP 127.0.0.1:1337 0.0.0.0:0 LISTENING TCP 127.0.0.1:8968 127.0.0.1:54992 ESTABLISHED TCP 127.0.0.1:10393 0.0.0.0:0 LISTENING TCP 127.0.0.1:49155 127.0.0.1:50300 ESTABLISHED TCP 127.0.0.1:50300 127.0.0.1:49155 ESTABLISHED TCP 127.0.0.1:54992 127.0.0.1:8968 ESTABLISHED TCP 192.168.1.5:139 0.0.0.0:0 LISTENING TCP 192.168.1.5:8866 192.168.1.2:52096 ESTABLISHED TCP 192.168.1.5:8968 192.168.1.105:62967 ESTABLISHED TCP 192.168.1.5:55033 192.168.1.22:15300 ESTABLISHED TCP [::]:135 [::]:0 LISTENING TCP [::]:445 [::]:0 LISTENING TCP [::]:554 [::]:0 LISTENING TCP [::]:2869 [::]:0 LISTENING TCP [::]:3389 [::]:0 LISTENING TCP [::]:3587 [::]:0 LISTENING TCP [::]:5357 [::]:0 LISTENING TCP [::]:10243 [::]:0 LISTENING TCP [::]:49152 [::]:0 LISTENING TCP [::]:49153 [::]:0 LISTENING TCP [::]:49154 [::]:0 LISTENING TCP [::]:49166 [::]:0 LISTENING TCP [::]:49167 [::]:0 LISTENING

The htpc is 192.168.1.5

[gEd]

next logical test is to see if you can connect to the webserver and get a response.
(on server) you may need to install telnet client from programs, add / remove features.

telnet 127.0.0.1 8866
in blank screen type GET and return twice
it should respond with

HTTP/1.1 302 Found
Server: Microsoft-Cassini/1.0.0.0
Date: Sat, 11 Jul 2015 10:09:47 GMT
X-AspNet-Version: 4.0.30319
Location: /logon.aspx?ReturnUrl=%2fdefault.aspx
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 154
Connection: Close

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/logon.aspx?ReturnUrl=%2fdefault.aspx">here</a>.</h
2>
</body></html>


Connection to host lost.

Which is is a response back from the webserver confirming that it is listening on that port and responding.
If you get the same, the webserver is running fine and you most likely have some kind of networking issue. if it doesn't respond, the webserver is not starting correctly (for some reason).

1. you definitely have got enable web server ticked in the config?
2. (i cant see how it might be related) but did you install the required directX runtime as well? http://www.microsoft.com/en-us/download/...px?id=8109

[Reddwarf]

next logical test is to see if you can connect to the webserver and get a response.
(on server) you may need to install telnet client from programs, add / remove features.

telnet 127.0.0.1 8866
in blank screen type GET and return twice
it should respond with

HTTP/1.1 302 Found
Server: Microsoft-Cassini/1.0.0.0
Date: Sat, 11 Jul 2015 10:09:47 GMT
X-AspNet-Version: 4.0.30319
Location: /logon.aspx?ReturnUrl=%2fdefault.aspx
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 154
Connection: Close

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/logon.aspx?ReturnUrl=%2fdefault.aspx">here</a>.</h
2>
</body></html>


Connection to host lost.

Which is is a response back from the webserver confirming that it is listening on that port and responding.
If you get the same, the webserver is running fine and you most likely have some kind of networking issue. if it doesn't respond, the webserver is not starting correctly (for some reason).

1. you definitely have got enable web server ticked in the config?
2. (i cant see how it might be related) but did you install the required directX runtime as well? http://www.microsoft.com/en-us/download/...px?id=8109

The client(s) works against the htpc so it is not a general network issue, but there is no Web.log in the logs folder and that tells me that newa is not starting. Is there any logging option I can turn on to see what is happening?

[sub]

Maybe try running 'nrecord.exe RUN' from the command prompt, to see if it outputs any messages about the webserver failing to start.