Reply to thread

Message

<blockquote data-quote="Prospero" data-source="post: 768972" data-attributes="member: 113194">Thanks for quick reply Mike. I figured as much, and tried stopping the TV4Home service, when the GMAWebservice then started working on 4321.However, I'm not quite sure why you needed to change this. My Windows XP box doesn't seem to support two services listening on the same port, and in any case the client-server architecture of Mediaportal means that the server and client aren't necessarily running on the same machine. When they are running on different machines behind a firewall, the user will have configured port forwarding for ports 4321 and 44321 to the different respective machines.After installing the new release the above configuration will be broken, and the user will have to either reprogram the firewall port forwarding to translate incoming port 44321 to port 4321 on the destination machine, or else edit the .config file for GMAWebService (as I have done) so that the service runs on 44321 as before.In any case, I think the change needs to be flagged up in the documentation with instructions for changing the port, as I can imagine there will be a lot of users who have spent a while setting up a finely tuned system only to find it broken by this update.</blockquote>

[QUOTE="Prospero, post: 768972, member: 113194"] Thanks for quick reply Mike. I figured as much, and tried stopping the TV4Home service, when the GMAWebservice then started working on 4321. However, I'm not quite sure why you needed to change this. My Windows XP box doesn't seem to support two services listening on the same port, and in any case the client-server architecture of Mediaportal means that the server and client aren't necessarily running on the same machine. When they are running on different machines behind a firewall, the user will have configured port forwarding for ports 4321 and 44321 to the different respective machines. After installing the new release the above configuration will be broken, and the user will have to either reprogram the firewall port forwarding to translate incoming port 44321 to port 4321 on the destination machine, or else edit the .config file for GMAWebService (as I have done) so that the service runs on 44321 as before. In any case, I think the change needs to be flagged up in the documentation with instructions for changing the port, as I can imagine there will be a lot of users who have spent a while setting up a finely tuned system only to find it broken by this update. [/QUOTE]

Verification