Client Fails to Launch

[taz]

I upgraded my previous GBPVR to v.98. Everything worked perfectly on the update (great job again Sub). I installed it on another PC and set it up as a client. It installed with no errors but when I try to run it nothing happens (it did run one time but I did not make any changes before or after). I have attached the log files.

Taz

[sub]

9/12/2006 8:41:02 PM.934 VERBOSE [1] getValue: /settings/ClientRemoteDirectory : \\pvr\gbpvr
9/12/2006 8:41:04 PM.036 ERROR [1] System.IO.IOException: Logon failure: unknown user name or bad password.

The machine is unable to access the \\pvr\gbpvr share you specified due to permissions.

[taz]

Thank you for the quick response. It asks for a password when I try to access it through explorer. After that GBPVR works fine. Thanks again Sub.

Taz

[dvasco]

How do you set up a client?

[sub]

Its pretty easy:

1) Install the new v0.98.8 release on the client machine.
2) On the capture source page, tick the client mode checkbox.
3) Key in the name of the server
4) Key in the UNC name of shared GB-PVR directory on the server (ie, \\server\gbpvr)

[dvasco]

I set up a 2nd computer as a client. When I try to watch a show the CPU goes to 99% and RAM goes up to 160 MB for gbpvr.exe. The video never plays.

[sub]

Even though initial feedback has been very good, this client stuff is obviously pretty new, so I'm not really aware yet of what problems some users might encounter, or work arounds for those problems.

Reproduce the problem, then zip and attach the logs for both the client and the server and I'll take a look.

[dvasco]

I hope I did this right.

[sub]

It looks like the request for the file never made it to the server. I'm guessing one of three things. (1) you keyed in the wrong server name. (2) the client isnt able to resolve the name. (3) your firewall on one of the two machines is getting in the way - we've already seen this a couple of times.

[dvasco]

It looks like the request for the file never made it to the server. I'm guessing one of three things. (1) you keyed in the wrong server name. (2) the client isnt able to resolve the name. (3) your firewall on one of the two machines is getting in the way - we've already seen this a couple of times.

Which port or ports do I need to open?