Problem scheduling recordings from client

[petek]

I'm having problems trying to schedule a recording from the client. When I select a program to record, the client will highlight the program in red in the guide, and the program appears in Pending Recordings as expected. The server also highlights the program in red and shows the program in Pending Recordings, so it looks as though the program is actually scheduled to be recorded. However, the recording does not take place and the program is still listed in Pending Recordings long after the recording should have finished.

In the attached log files, I used the client to schedule "Shopper's Showcase" to record from 11:00 - 11:30 AM, then exited the client PVRX2. A few minutes later, I used the client PVRX2 to schedule "Word World" from 11:30 - 12:00 PM. I checked the Server, and both programs were listed in Pending Recordings.

At 11:45, I checked the server and noticed that "Shopper's Showcase" did not record and both capture sources were sleeping, indicating that "Word World" was not being recorded either. Then I rebooted the server to install a Windows update. Later I noticed that when the server came back up, it did record the last 6 minutes of "Word World". "Shopper's Showcase" was not recorded.

I think I have ports 7967-7968 setup correctly, but don't know how to test them to make sure. Both client and server are running WinXP and PVRX2 1.2.9.

Thanks for any ideas,
Pete

[sub]

2008-04-15 10:55:08.046 VERBOSE [1] System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.254.5:7968

It looks like it failed to communicate with the recording service to tell it to reload its recording schedule. I'm guessing it is something you'vr missed with the firewall setup.

[petek]

Thanks, Sub. I think I have it sorted out. My server firewall allows me to specify both a local and remote port range. I had set both to 7967-7968. I set the remote port range to ALL, and now I can schedule a recording successfully. Is there a specific port or range that I should set for the remote ports, or should I just leave it at ALL?

[petek]

I should mention that I found a port scanner tool to be very helpful in debugging this problem. I used PortQueryUI from Microsoft http://support.microsoft.com/kb/310099/ but I'm sure others would work fine too. From the client and server computers, scan the other machine for ports 7967 and 7968 and make sure that they are open ("Listening" as reported by PortQueryUI). If they are open on each computer, then you should be set. If not, you need to adjust the firewall settings to open the ports.

Hope this helps someone,
Pete

[SLR_65]

This is the exact same problem I'm having, except that I've found an interesting twist . . . If the server is running and I boot up the client I have the problem. if I go to the server and exit GBPVR, then restart the recording service, and then restart GBPVR the problem goes away - I can schedule and record just fine. I can even exit GBPVR on the client and start it back up and it works fine, it's just when I completely reboot the client the problem surfaces and I have to leave it running and reboot the server. Interesting, huh? I hate intermittant things, you think you got it fixed and then you miss a recording . . . :mad:

Anyway, it looks like I need to open some ports on the firewall. I am using the stock XP firewall and reading the M$ page on how to open ports it looks like there's a choice I don't know the answer to (I'm not home right now or I'd just experiment to find the answer).

From the M$ web page on opening ports:

"Click either TCP or UDP, and then click OK."

Which do I need to click on, TCP or UDP?

Thanks,

Steve

[sub]

Anyway, it looks like I need to open some ports on the firewall. I am using the stock XP firewall and reading the M$ page on how to open ports it looks like there's a choice I don't know the answer to (I'm not home right now or I'd just experiment to find the answer).

From the M$ web page on opening ports:

"Click either TCP or UDP, and then click OK."

Which do I need to click on, TCP or UDP?

GB-PVR uses TCP

[SLR_65]

OK, I'm using the PortQryUI referenced above. with both the server and client firewalls down ports 7967 and 7968 report as listening when I'm on the client and checking the server. With both firewalls up it reports the same thing so it looks like we're good to go in that direction.

Now the problem . . . with both firewalls down and checking my client from the server it's reported as not listening. It's also reported as not listening with both firewalls up. I have opened those ports on both firewalls.

Where do I go from here? The problem is evidently with the client, but with the firewall down nothing should be blocking those ports, should it? How do I find out what's keeping those ports closed?

Thanks!

Steve

[SLR_65]

A little more info . . .

When I use PortQryUI to query the client ports from the client it shows them as listening, but again - if I query the client ports from the server it shows not listening.

Maybe the router is getting in the way? But then why would it not get in the way of the server?

[SLR_65]

Just a follow up . . . I gave up on trying to solve this. I'm just not that good with such issues and I don't have the time to get good right now.

I can turn the firewalls off and still have the issue which leads me to believe it's not a firewall issue.

I've suspected the router but then why would it allow it one way and not the other and why wouldn't it always be an issue? Right now if I reboot the client I have the problem, if I reboot the server after rebooting the client then it works fine until the client is rebooted again.

I'm wondering about Service Pack 3 and if it introduced any bugs for clients.

Oh well, a project for when I have more time. For now if I reboot the client then I immeadiately go down and reboot the server and then all is well until the client is rebooted again.

/Steve