Did you get the message "Unable to communicate with recording service" at the last attempt? I don't see any sign of it, but I don't see any sign of trying to watch live-tv eigther in the last client logs. But I do see a message indicating that the required DirectX version possibly is not installed. Did you install the specific DirectX version mentioned in prerequisites?
"I'd rather have a bottle in front of me than a frontal lobotomy"
I had a similar problem, although I'm running a Windows 7 client and an XP server. I found that adding the NRecord.exe app to the list of Windows Firewall exceptions on the server solved the problem.
I tried using the client over wireless G, but it was so slow as to be useless. A wired connection works pretty well. I just installed the current beta on the client. I have one of the older betas on the server.
I also had the problem where the folder for the live TV buffer and recording folder on the server have to exist on the client, even though the server folders are being used. For example, when I had the recording folder on my D: drive on the server, I would get an error on the client that the location didn't exist, because I don't have a D: drive on the client. When I changed the recording folder to a location on the C: drive of the server, the client worked
Rich2 Wrote:I also had the problem where the folder for the live TV buffer and recording folder on the server have to exist on the client, even though the server folders are being used. For example, when I had the recording folder on my D: drive on the server, I would get an error on the client that the location didn't exist, because I don't have a D: drive on the client. When I changed the recording folder to a location on the C: drive of the server, the client worked
I seem to remember that this issue is solved in the 1.5.33.
"I'd rather have a bottle in front of me than a frontal lobotomy"
darkfires Wrote:I'm having this problem with 3.1.1, maybe a regression? Firewalls disabled.
I don't think so, otherwise we'd be seeing a hell of a lot more reports about it. I suspect it's just the same old firewall type problems some people have had in the past.
(this thread you posted on is 3 years old, so only really you reporting it recently)