MP 1.0 Multiseat REALLY slow? PLEASE HELP! (1 Viewer)

[naich]

Hi BurnumBurnum! (What a nick )

Which firewall do you use?

I use zonealarm on each HTPC and the Server. Do you open those TCP ports also for internet traffic or only for the "saftey zone", maybe this is only a zonealarm typical setting option)?

thx

cu

 

[BurnumBurnum]

I use the MS Windows Firewall that comes with Vista.
I've added the ports not only for intranet but also for internet access. I could try just opening the ports for internal access.. will check this out later...

 

[Raytestrak]

I did. Added tcp ports 554, 31456 and 49567 to the server firewall... et voilá

Thanks! UDP or TCP? I'll try it tonight.

TCP
Pls report back if it works for you!

Didn't work for me ... I don't know if MP uses the same ports al the time or a range of ports. What did you use to monitor the firewall?

 

[BurnumBurnum]

Jepp, the ports seem to change. Now its 49297 instead of 49567. I used a free trial of nsauditor.

 

[Raytestrak]

Jepp, the ports seem to change. Now its 49297 instead of 49567. I used a free trial of nsauditor.

Calling all devs

What port ranges does MP use to connect to a TV server? I don't wanna turn my firewall off, there are some services running on my TV server that are constantly connected to internet.

 

[grubi]

Jepp, the ports seem to change. Now its 49297 instead of 49567. I used a free trial of nsauditor.

Calling all devs

What port ranges does MP use to connect to a TV server? I don't wanna turn my firewall off, there are some services running on my TV server that are constantly connected to internet.

Did you try to enable the "Remote Management" exception in the Windows firewall?
Did you check if the MP server is listening to any of the ports in question by default?
You can verify with "netstat -a -n".
If not then maybe this is a dynamically negotiated port (e.g. if DCOM is involved in this process or maybe RTSP is using dynamic port negotiation).
This is just a wild guess. I don't know if DCOM is even involved.
If nothing else helps maybe using WireShark is the only way to shed some light on the problem.