Sage Tv Client network question/troubleshooting.

[toricred]

What do you have your Default Gateways and Subnet Masks set to on the client and the server. Also what is the internal IP address of the Router?

Another way to check would be if you have a simple switch rather than the router. It eliminates a lot of things just for testing.

[LuDaCrIs]

Originally Posted by toricred

What do you have your Default Gateways and Subnet Masks set to on the client and the server. Also what is the internal IP address of the Router?

Another way to check would be if you have a simple switch rather than the router. It eliminates a lot of things just for testing.

I'm guessing you mean what are the gateways and masks of the computers that have the cleint and server software on it, right?

Server:

Default Gateway: 192.168.1.1
Subnet Mask: 255.255.255.0

Client:

Default Gateway: 192.168.1.1
Subnet Mask: 255.255.255.0

Internal IP address of the router is: 192.168.1.1


I am not sure I want to spend money on a switch just to troubleshoot some software.

[toricred]

I was thinking more along the lines of using one you already have. If both the network cards in the PCs are gigabit you could also just use a regular Cat 5 or Cat 6 cable between them as the gigabit spec deals with any need of a crossover cable automatically. That way you completely eliminate any possible router configuration issues.

[sainswor99]

One more thing you can verify; on the PC (server), run the Sage UI, and click Setup --> Help --> System Information. In the system status section, check the IP Address (you may have to scroll to see it). Is it the same as the ip address reported by ipconfig?

It almost sounds as if the SageTV service is trying to bind to an improperly configured network card (based on the error log you posted earlier). You're probably going to have to get tech support involved, but this is another stab in the dark at it.

[koan00]

Originally Posted by LuDaCrIs

Anyone know if this helps in the troubleshooting at all? It's a log of Sagetv while I tried to run the client on the other PC.

×ò 12/31 17:12:11.066 Error (will retry) in MediaServer:java.net.BindException: Address already in use: bind
×ò 12/31 17:12:11.066 java.net.BindException: Address already in use: bind
×ò 12/31 17:12:11.066 at sun.nio.ch.Net.bind(Native Method)
×ò 12/31 17:12:11.066 at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
×ò 12/31 17:12:11.066 at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
×ò 12/31 17:12:11.066 at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
×ò 12/31 17:12:11.067 at sage.MediaServer.run(Unknown Source)
×ò 12/31 17:12:11.067 at java.lang.Thread.run(Unknown Source)
×ò 12/31 17:12:11.577 Error creating server socket:java.net.SocketException: Permission denied: listen failed
×ò 12/31 17:12:11.578 Waiting to retry to open SageTV Server socket...

This is good output. It means that for whatever reason, SageTV server could not start to listen to network traffic on a specific IP:Port combination on the server machine. Given what you said and the information from the SageTV FAQ, the problem combination should be 192.168.1.4:42024 (or 0.0.0.0:42024 for globally bound ports)

There could be a couple of issues that would create a failure scenario:
1) Some other software is already listening on the port, and did not enable socket reuse
2) Another copy of Sage is running, and has already bound the port
3) Permission to open the port is denied by firewall/anti spyware/ OS software (did you check anti spyware software is disabled?)

For number 1+2, what I would suggest first is to get on the server machine, and shutdown the sage server. Then look to see if the port is in use. To do this, open a (dos) command prompt as administrator: Start->All Programs->Accessories-> RIGHT CLICK on command prompt, and choose "Run as Administrator".

In the DOS window, issue the following command: "netstat -b -a -p TCP". In the "Local Address" column, look for any local address ending in ":42024" - If you find an entry, look at the last column and see what executable has the port open. If you don't find the port, open SageTV again, let it fully start up, and issue the same command. You should now see the port and the process as SageTV.exe

Please let us know the results of this test(s)

For number 3, it looks like we have beaten the dead horse regarding firewall. I would also check an anti-spyware/virus software is disabled, and failing that, try running SageTV as administrator.

[LuDaCrIs]

Okay, went into cmd as admin and typed what you suggested (netstat -b -a -p TCP) and got a bunch of apps and their addresses.

One thing I noticed: When SageTV is NOT running there is no app that is using port or address 42024. But, when I run SageTv and re-run the command it lists SageTv using port or address 3651. I am not sure why it's not using 42024.

Doesn't this complicate things further? Man, I gotta say, given how my trial is going to run out shortly, I am very disappointed in Sagetv. This isn't really directed at someone, but maybe someone can recommend another software package that offers the same thing: the ability to watch your tv with a server and client somewhere else on your network.

[koan00]

Hmm that is weird. Just to see if I have your situation correct, you already had a working SageTV installation, and wanted to test only the client on a trial basis?

Have you tried updating the server to SageTV version 6.6.2? It looks like you are running 6.5.9 on the server (based on the screen shot) It may correct what ever issue you are having when you update.

The only thing else I can suggest is that you can use a Placeshifter trial to see if you can get that working once the client trial runs out. If it does work you can be pretty sure you can get the full client working.

[tonysathre]

Did you try reinstalling the JRE?

Look in the Task Manager and see if SageTVService.exe is running under the Processes tab.

Try booting into Safe Mode with Networking, start the SageTV Service, then try connecting, to make sure nothing is binding that socket. Some rootkits will bind a socket, but running a simple nbtstat or netstat won't show it.

Check your Event Viewer for errors. Start > Run > eventvwr

It looks like SageTV listens on several ports. Run a netstat -ban and see if it's listening on the following ports:

7818
31099
42024
1028
1029

Make sure nothing else is listening on any of those ports.

Tony

[LuDaCrIs]

Just to be clear, sage service is different than the application itself, right? I notice that in the Sagetv installation folder there is a sagetv.exe and sageservice.exe. These are the two different things we are talking about, right?

I will try out the booting in safe mode and running the app in a second and will get back to you, shortly.

Again, I want to thank you for taking the time--very much appreciated. Same to Koan00 and everyone else.

[GKusnick]

SageTV.exe and SageTVService.exe aren't completely different; they're two different ways of accomplishing the same thing. If you just run SageTV.exe you can do everything that Sage does, but you need to be logged into Windows with the Sage app running to do it. So for instance if you have scheduled recordings, or want to connect from a client, the Sage app would have to be running on the server to do those things if you want to use the Sage app in this self-contained mode without the service.

If you opt to use the SageTV service, it's a bit more complicated to set up, but gives you greater flexibility, because the service can run in the background and make recordings, serve clients, and so on from the moment Windows boots up, without having to log in to Windows or start the Sage app. In this mode you can still run the Sage app on the server, but then it's just like any other client and connects to the service running in the background to do the actual work.

I gather from your question that you're not currently using the service, which simplifies troubleshooting somewhat for now. In the long run, though, you'll probably want to switch over to running in service mode so that recordings and client connections don't get interrupted if you close the Sage UI on the server.

[LuDaCrIs]

Originally Posted by tonysathre

Tony

Okay, here is what I get when I run Sagetv in windows and then run the command netstat -ban. It's kinda long, but i figure this is easier than writing a description:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\user>netstat -ban

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       1604
  [Skype.exe]

  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       496
  c:\windows\system32\WS2_32.dll
  C:\WINDOWS\system32\RPCRT4.dll
  c:\windows\system32\rpcss.dll
  C:\WINDOWS\system32\svchost.exe
  C:\WINDOWS\system32\ADVAPI32.dll
  [svchost.exe]

  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING       1604
  [Skype.exe]

  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
  [System]

  TCP    0.0.0.0:1031           0.0.0.0:0              LISTENING       2092
  [java.exe]

  TCP    0.0.0.0:1099           0.0.0.0:0              LISTENING       2092
  [java.exe]

  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       400
  -- unknown component(s) --
  [svchost.exe]

  TCP    0.0.0.0:25902          0.0.0.0:0              LISTENING       2092
  [java.exe]

  TCP    0.0.0.0:55110          0.0.0.0:0              LISTENING       1604
  [Skype.exe]

  TCP    127.0.0.1:1040         0.0.0.0:0              LISTENING       2268
  [alg.exe]

  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING       816
  [mDNSResponder.exe]

  TCP    127.0.0.1:8079         0.0.0.0:0              LISTENING       2092
  [java.exe]

  TCP    127.0.0.1:12346        0.0.0.0:0              LISTENING       932
  [CLMLService.exe]

  TCP    127.0.0.1:27015        0.0.0.0:0              LISTENING       260
  [AppleMobileDeviceService.exe]

  TCP    127.0.0.1:32000        0.0.0.0:0              LISTENING       1956
  [Wrapper.exe]

  TCP    127.0.0.1:49152        0.0.0.0:0              LISTENING       276
  [AskService.exe]

  TCP    192.168.1.4:139        0.0.0.0:0              LISTENING       4
  [System]

  TCP    127.0.0.1:1029         127.0.0.1:32000        ESTABLISHED     2092
  [java.exe]

  TCP    127.0.0.1:2165         127.0.0.1:2166         ESTABLISHED     3824
  [firefox.exe]

  TCP    127.0.0.1:2166         127.0.0.1:2165         ESTABLISHED     3824
  [firefox.exe]

  TCP    127.0.0.1:2167         127.0.0.1:2168         ESTABLISHED     3824
  [firefox.exe]

  TCP    127.0.0.1:2168         127.0.0.1:2167         ESTABLISHED     3824
  [firefox.exe]

  TCP    127.0.0.1:32000        127.0.0.1:1029         ESTABLISHED     1956
  [Wrapper.exe]

  TCP    192.168.1.4:1474       173.35.95.183:54421    ESTABLISHED     1604
  [Skype.exe]

  TCP    192.168.1.4:1548       64.233.169.147:80      ESTABLISHED     3824
  [firefox.exe]

  TCP    192.168.1.4:1551       74.125.93.100:80       ESTABLISHED     3824
  [firefox.exe]

  TCP    192.168.1.4:1552       74.125.93.100:80       ESTABLISHED     3824
  [firefox.exe]

  TCP    192.168.1.4:1553       74.125.19.101:80       ESTABLISHED     3824
  [firefox.exe]

  TCP    192.168.1.4:1571       74.125.113.101:80      ESTABLISHED     3824
  [firefox.exe]

  TCP    192.168.1.4:1606       64.239.246.136:80      ESTABLISHED     3824
  [firefox.exe]

  TCP    192.168.1.4:2529       64.239.246.135:4510    ESTABLISHED     3824
  [firefox.exe]

  TCP    192.168.1.4:3378       67.195.186.111:5050    ESTABLISHED     3824
  [firefox.exe]

  TCP    192.168.1.4:4357       74.125.93.101:80       CLOSE_WAIT      3824
  [firefox.exe]

  TCP    192.168.1.4:1579       209.216.209.49:80      LAST_ACK        3824
  [firefox.exe]

  TCP    192.168.1.4:1580       209.216.209.49:80      LAST_ACK        3824
  [firefox.exe]

  TCP    192.168.1.4:1581       209.216.209.49:80      LAST_ACK        3824
  [firefox.exe]

  TCP    192.168.1.4:1582       209.216.209.49:80      LAST_ACK        3824
  [firefox.exe]

  TCP    192.168.1.4:1583       209.216.209.49:80      LAST_ACK        3824
  [firefox.exe]

  TCP    192.168.1.4:1589       209.216.209.49:80      LAST_ACK        3824
  [firefox.exe]

  TCP    127.0.0.1:1608         127.0.0.1:1609         TIME_WAIT       0
  TCP    192.168.1.4:1617       192.168.1.3:139        TIME_WAIT       0
  TCP    192.168.1.4:1619       192.168.1.3:139        TIME_WAIT       0
  UDP    0.0.0.0:445            *:*                                    4
  [System]

  UDP    0.0.0.0:55110          *:*                                    1604
  [Skype.exe]

  UDP    0.0.0.0:443            *:*                                    1604
  [Skype.exe]

  UDP    0.0.0.0:8270           *:*                                    2536
  [SageTV.exe]

  UDP    0.0.0.0:61535          *:*                                    816
  [mDNSResponder.exe]

  UDP    0.0.0.0:1026           *:*                                    816
  [mDNSResponder.exe]

  UDP    127.0.0.1:123          *:*                                    964
  c:\windows\system32\WS2_32.dll
  c:\windows\system32\w32time.dll
  ntdll.dll
  -- unknown component(s) --
  [svchost.exe]

  UDP    127.0.0.1:3060         *:*                                    964
  c:\windows\system32\WS2_32.dll
  C:\WINDOWS\system32\WINHTTP.dll
  C:\WINDOWS\system32\upnp.dll
  C:\WINDOWS\system32\RPCRT4.dll
  C:\WINDOWS\system32\ole32.dll
  [svchost.exe]

  UDP    127.0.0.1:1900         *:*                                    1556
  c:\windows\system32\WS2_32.dll
  c:\windows\system32\ssdpsrv.dll
  C:\WINDOWS\system32\ADVAPI32.dll
  C:\WINDOWS\system32\kernel32.dll
  [svchost.exe]

  UDP    127.0.0.1:1028         *:*                                    932
  [CLMLService.exe]

  UDP    127.0.0.1:1063         *:*                                    1604
  [Skype.exe]

  UDP    192.168.1.4:1900       *:*                                    1556
  c:\windows\system32\WS2_32.dll
  c:\windows\system32\ssdpsrv.dll
  C:\WINDOWS\system32\ADVAPI32.dll
  C:\WINDOWS\system32\kernel32.dll
  [svchost.exe]

  UDP    192.168.1.4:138        *:*                                    4
  [System]

  UDP    192.168.1.4:137        *:*                                    4
  [System]

  UDP    192.168.1.4:123        *:*                                    964
  c:\windows\system32\WS2_32.dll
  c:\windows\system32\w32time.dll
  ntdll.dll
  C:\WINDOWS\system32\kernel32.dll
  [svchost.exe]

  UDP    192.168.1.4:5353       *:*                                    816
  [mDNSResponder.exe]

When I boot in safe mode and run the SageTv Service control I get the following:

http://imgur.com/Lkfhv.jpg

There is a process running in the task manager though, called Sagetvservice....
I run the sagetv client on the laptop and it doesn't recognize the server anymore if i'm in safe mode and following the above instructions. I hope that was clear enough.

[tonysathre]

After I posted that, I kinda figured that the service wouldn't start in Safe Mode. Have you tried reinstalling the JRE? I think that would have been one of my first steps.

Tony

[LuDaCrIs]

Originally Posted by tonysathre

After I posted that, I kinda figured that the service wouldn't start in Safe Mode. Have you tried reinstalling the JRE? I think that would have been one of my first steps.

Tony

Before I do that, I just noticed something. The main app acting as the server is on a windows xp OS running service pack 2. The client is on a windows xp os running service pack 3. Do you think that could make a difference?

[toricred]

That shouldn't make any difference.

Just to be clear, you are running your server as a service right?

[LuDaCrIs]

Originally Posted by toricred

That shouldn't make any difference.

Just to be clear, you are running your server as a service right?

I am sorry for being an idiot here, but how would i do that? I might be doing it right, but I want to make sure. Can you give me a step by step so that I/we know this isn't the issue for sure.

[Opus4]

Originally Posted by koan00

Not entirely sure if this matters, but it looks like you have a version mismatch. Client is showing v6.6.2, while server is showing v6.5.9

I saw this comment a couple times above, but no response to it -- are the server & clients running the same version or not? If not, try installing the same version on both PCs.

Originally Posted by LuDaCrIs

I am sorry for being an idiot here, but how would i do that? I might be doing it right, but I want to make sure. Can you give me a step by step so that I/we know this isn't the issue for sure.

If you are asking about using SageTV in service mode: chapter 2 of the PDF manual covers getting started, including using service mode (pages 15-17).

- Andy

[tonysathre]

I just did it recently. This is how I did it, but I'm not sure if this is the 'correct' procedure.

Start > Run > appwiz.cpl

Uninstall the current Java

Go here: http://java.com/en/download/manual.jsp
and download the correct JRE for your OS.

Worked for me at least. You may need to reboot to finish the uninstall, but I don't remember if I did. It doesn't hurt to do so.

Tony

[GKusnick]

Originally Posted by LuDaCrIs

I am sorry for being an idiot here, but how would i do that? I might be doing it right, but I want to make sure. Can you give me a step by step so that I/we know this isn't the issue for sure.

If you haven't used service mode before, then trying to set it up now for the first time may just complicate your troubleshooting by introducing new things to go wrong. In my opinion there's no reason so far to think your networking troubles are related to service mode or lack of it. So if you don't have service mode enabled now, then I'd recommend leaving it that way until you get your other issues resolved.

That said, it would help us to know for sure whether you have it enabled or not. The way to find that out is by using the service control applet as described in Chapter 2, or by consulting the Services console under Control Panel > Administrative Tools, scrolling down to SageTV, and looking in the Status column.

[UgaData]

I don't use a client/server setup anymore but unless something has changed the client and server need to be the same version.

Check client and Server versions

[LuDaCrIs]

Okay, re-installed Java to the newest version.

The Sagetv service is listed as "disabled" in the administrative services.

And, as I mentioned on the first page of the thread, I've updated the main app to the latest version and the client is running the trial version, which I downloaded roughly 15 days ago, which would tell me it's likely the most recent version.