MP Client not responding when putting in TV Server hostname (Vista) (1 Viewer)

[greminn]

TV-Server Version: 1 RC2
MediaPortal Version: Latest 1 RC2 snapshot (as of Today)
MediaPortal Skin:
Windows Version: Vista PS1
CPU Type:
HDD:
Memory:
Motherboard:
Video Card: 7600GS
Video Card Driver:
Sound Card:
Sound Card AC3:
Sound Card Driver:
1. TV Card:
1. TV Card Type:
1. TV Card Driver:
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote:
TV:
TV - HTPC Connection:

I have installed 1 RC2 tv server on a windows XP with SP3 and this is running fine and has found all channels etc. I then installed MP 1 RC2 with the tv client plugin on a Vista SP1 box. When i run the config it works fine until i put in the hostname (in this case "mediaserver"), then the application freezes and after a while i get the "program not responding" option box... I have updated MP on the client to the lastest snapshot as well.

Any ideas here?

Simon

Note: This is the same when putting in the tv server hosting via MP rather than the Config tool

 

[chemelli]

Hi greminn,

to try help you we need logs

Simone

 

[greminn]

I sorted this out. I turned off the firewall on the tv server and it worked stright away.

Simon

 

[chemelli]

Guess you dind't install it using RC2 installer: if so windows inbuilt firewall would have been configured to handle this situation.

Simone

 

[greminn]

Actually i did, used it for both the TV-Server and the Client.

Simon

 

[Domarkas]

I also have the feeling that firewall is not completely set for MP. I also had to switch it total off.

BTW: in TV-Server Manual is written which ports have be free. But how can I manage setting fre port 6999 - 8000 for example? Has anyone an idea to open ports from to?

 

[robby3]

Had the same problem as the configuration menu crashed after entering the correct server name. The problem seems to be that the configuration finds the server by name but cannot access it somehow. I then deactivated the firewall on the server (Vista 64) and the problem went away. I'm sure that the firwewall an both sides the client and server must be configurated or deactivated like in my case (I'm behind a NAT so no problem).

IMHO the config tool should not crash but give an appropriate message to the user.

- Roger, Switzerland