Sage Tv Client network question/troubleshooting.

[tonysathre]

Do you have another system you could try it on? That would tell you on which system the problem lies.

[LuDaCrIs]

I only have a tv tuner card in one computer. So trying the main app on another computer is out of the question.

I have tried the client on other computers on the network and the same thing occurs. This tells me the problem is most definitely on the computer with the main app on it, no? Unless it's a network wide problem.

[korben_dallas]

On the client PC, run SageTVclient and leave up the connect message. Then do a plain netstat from the command line (on same client PC) and post the output here.

[LuDaCrIs]

Active Connections

  Proto  Local Address      Foreign Address        State
  TCP    laptop:2446        localhost:27015       ESTABLISHED
  TCP    laptop:2452        localhost:2453         ESTABLISHED
  TCP    laptop:2453        localhost:2452         ESTABLISHED
  TCP    laptop:2456        localhost:5354         ESTABLISHED
  TCP    laptop:2457        localhost:5354         ESTABLISHED
  TCP    laptop:2458        localhost:5354         ESTABLISHED
  TCP    laptop:2459        localhost:5354         ESTABLISHED
  TCP    laptop:2460        localhost:5354         ESTABLISHED
  TCP    laptop:2461        localhost:2462         ESTABLISHED
  TCP    laptop:2462        localhost:2461         ESTABLISHED
  TCP    laptop:3347        localhost:3363         ESTABLISHED
  TCP    laptop:3363        localhost:3347         ESTABLISHED
  TCP    laptop:5152        localhost:2454         CLOSE_WAIT
  TCP    laptop:5354        localhost:2456         ESTABLISHED
  TCP    laptop:5354        localhost:2457         ESTABLISHED
  TCP    laptop:5354        localhost:2458         ESTABLISHED
  TCP    laptop:5354        localhost:2459         ESTABLISHED
  TCP    laptop:5354        localhost:2460         ESTABLISHED
  TCP    laptop:27015       localhost:2446         ESTABLISHED
  TCP    laptop:2397        64.71.248.186:http     CLOSE_WAIT
  TCP    laptop:3059        cds36.iad9.msecn.net:http  CLOSE_WAIT
  TCP    laptop:3317        by2msg1010516.gateway.edge.messenger.live.com:18
63  ESTABLISHED
  TCP    laptop:3703        65.55.15.125:http      CLOSE_WAIT
  TCP    laptop:4075        lga15s04-in-f100.1e100.net:https  ESTABLISHED
  TCP    laptop:4076        lga15s04-in-f100.1e100.net:https  ESTABLISHED
  TCP    laptop:4077        lga15s01-in-f83.1e100.net:https  ESTABLISHED
  TCP    laptop:4078        lga15s01-in-f83.1e100.net:https  ESTABLISHED
  TCP    laptop:4081        192.168.1.4:microsoft-ds  ESTABLISHED
  TCP    laptop:4090        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4091        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4100        admin.freytechnologies.com:http  LAST_ACK
  TCP    laptop:4101        admin.freytechnologies.com:http  LAST_ACK
  TCP    laptop:4102        admin.freytechnologies.com:http  LAST_ACK
  TCP    laptop:4103        admin.freytechnologies.com:http  LAST_ACK
  TCP    laptop:4104        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4107        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4110        lga15s01-in-f100.1e100.net:http  ESTABLISHED
  TCP    laptop:4112        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4114        72-165-61-145.dia.static.qwest.net:27039  CLOSE_
WAIT
  TCP    laptop:4117        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4120        69.60.7.199:http       ESTABLISHED
  TCP    laptop:4121        199.239.136.200:http   ESTABLISHED
  TCP    laptop:4122        blog-win-cs-dtc02.evip.aol.com:http  TIME_WAIT
  TCP    laptop:4131        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4134        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4135        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4136        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4138        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4139        admin.freytechnologies.com:http  TIME_WAIT
  TCP    laptop:4140        blog-win-cs-dtc02.evip.aol.com:http  TIME_WAIT

[GKusnick]

Originally Posted by LuDaCrIs

I only have a tv tuner card in one computer. So trying the main app on another computer is out of the question.

Actually it's not out of the question. You can install the server software and test client connections without a tuner card. You won't be able to configure the EPG, but you don't need that to troubleshoot your connectivity problem.

[LuDaCrIs]

Originally Posted by GKusnick

Actually it's not out of the question. You can install the server software and test client connections without a tuner card. You won't be able to configure the EPG, but you don't need that to troubleshoot your connectivity problem.

Fair enough. I guess i was a little presumptuous there. Will give it a go.

[korben_dallas]

Is the server TimeZone, DST setting, and Time the same as the clients?

Do you have some special configuration or rules or static routes for the server on your router, using ip address or host name of the server? Is it designated as a DMZ on the router?

Can you do simple Windows file sharing on the server and verify that a Windows client can pull a file over the network from the server? And how about push a file to the server?

On the server, if you go to Network Connections > properties of Local Area Connection, what does it say under "This connection uses the following items:"

[LuDaCrIs]

Time to close the thread.

I figured out the issue and it's been resolved. Thanks everyone.

I've got vacation plans to work out and won't be back for a bit. See ya everyone.

P.s If your tv tuner card came with software, makes sure it's not installed or running any services because they conflict with Sagetv.