Please report UPnP port forwarding results

[cmaffia]

Do I need to open port 31099 AND 443??

Originally Posted by gplasky

But did you open port 31099 in your router's firewall? Not forward the port, but open it in your firewall on your router? You don't have to touch the Placeshifter configuration. I configure nothing for Placeshifter except a user name and password. You router has a firewall configuration, correct?

Gerry

[cmaffia]

After configuring Placeshifter successfully (for the 100th time )..and testing it successfully,
I just rebooted my server.. and I can't placeshift again.
Went into setup and it tells me that although a UPNP device was set previously it can not find the previous settings.. I have to setup from scratch.. this is the OTHER problem.. it is either that it can't find a UPNP device OR it loses the configuration whenever I reboot or exit sage.
This happends when I use Sage Service and even happends when I am not using Sage Service.
It seems that the problem only happends if I deviate from port 31099... stray from that and I get these problems
Bug report??

[Opus4]

You should file a bug report regarding the UPnP results; there may be something in the code that can be done to better handle the router you are using.

For manual port forwarding: You can't simply forward port 443 to the server PC. When you configure a custom port (443), you are configuring the _external_ port that will be forwarded to port 31099 on the server PC. There is a property that can be set to change the 31099 value (search the property file), but if you have an MVP, it will no longer be able to connect to SageTV.

If your router cannot be set to manually forward external port 443 to 31099 at the server PC's IP address, then yes, you have to use UPnP... and follow up on that bug report.

- Andy

[cmaffia]

Thanks Andy. And for the record I am using the very popular WRT54G by Linksys

Originally Posted by Opus4

You should file a bug report regarding the UPnP results; there may be something in the code that can be done to better handle the router you are using.

For manual port forwarding: You can't simply forward port 443 to the server PC. When you configure a custom port (443), you are configuring the _external_ port that will be forwarded to port 31099 on the server PC. There is a property that can be set to change the 31099 value (search the property file), but if you have an MVP, it will no longer be able to connect to SageTV.

If your router cannot be set to manually forward external port 443 to 31099 at the server PC's IP address, then yes, you have to use UPnP... and follow up on that bug report.

- Andy

[gplasky]

Originally Posted by cmaffia

Thanks Andy. And for the record I am using the very popular WRT54G by Linksys

By default your router firewall is configured to Block your ports.

The Security Tab - Firewall
Block WAN Requests. Enable the Block WAN Request feature by checking the box beside Block Anonymous Internet Requests and you can prevent your network from being “pinged,” or detected, by other Internet users.
The Block WAN Request feature also reinforces your network security by hiding your network ports. Bothfunctions of the Block WAN Request feature make it more difficult for outside users to work their way into your
network. This feature is enabled by default.

Gerry

[cmaffia]

I am allowing specific ports through my router and forwarding to various workstations that are configured with static IP's correctly. The only device that has a problem is Sage/Placeshifting Configuration. I am filing a bug report on this issue as I believe the problem is sage and the way it implements UpNp (when deviating from port 31099) I also do not use any firewall software on my sage servers

Originally Posted by gplasky

By default your router firewall is configured to Block your ports.


Gerry

[fastoy]

Originally Posted by Opus4

You should file a bug report regarding the UPnP results; there may be something in the code that can be done to better handle the router you are using.

For manual port forwarding: You can't simply forward port 443 to the server PC. When you configure a custom port (443), you are configuring the _external_ port that will be forwarded to port 31099 on the server PC. There is a property that can be set to change the 31099 value (search the property file), but if you have an MVP, it will no longer be able to connect to SageTV.

If your router cannot be set to manually forward external port 443 to 31099 at the server PC's IP address, then yes, you have to use UPnP... and follow up on that bug report.

- Andy

What is port 443 needed for relative to PlaceShifter? I thought that was just for SSL.

Is there a FAQ beyond the SageTV manual on how to setup PlaceShifter? I have followed the instructions but it will neither self-test nor work from the Internet. I have tried both manual port forwarding and UPnP with no success.

I am running an D-Link DI-624 and have the Windows XP SP2 firewall turned off on my SageTV box.

[Opus4]

Originally Posted by fastoy

What is port 443 needed for relative to PlaceShifter? I thought that was just for SSL.

That was just in response to someone trying to connect via that port from work, I believe. Port 443 has no significance for the placeshifter, as far as I know. I just meant that if that was the port forwarded to the SageTV server, it would have to be forwarded to the actual internal port (31099) or the internal port # would have to be changed, but that would prevent usage of the MVP on the local network.

Is there a FAQ beyond the SageTV manual on how to setup PlaceShifter? I have followed the instructions but it will neither self-test nor work from the Internet. I have tried both manual port forwarding and UPnP with no success.

I belive it is just what's in the manual + various posts as people have discussed any problems.

How are you doing the port forwarding? manually? UPnP? Either way, what ports are being used?

- Andy

[fastoy]

Originally Posted by Opus4

How are you doing the port forwarding? manually? UPnP? Either way, what ports are being used?

- Andy

I've tried both manual and UPnP. I used the defaults both ways.

Here're the screen shots from my efforts with manual port forwarding. I tried UPnP but my router kept resetting when I had that enabled. I had rather use manual port forwarding for security reasons anyway.

[Opus4]

For the test results, SageTV's locator server system can't connect to your SageTV server. Either it doesn't know the correct internet IP address for your network (but the latest versions should update it right away before doing such a test), or there is still some sort of firewall issue blocking access on you system. Well, I'm sure there could be some other reason, but that's all I can think of at the moment.

Oh -- have you restarted SageTV? Or, when you turned the Placeshifter server on, did you toggle the main server off & back on so that the PS server got restarted also?

- Andy

[fastoy]

Originally Posted by Opus4

For the test results, SageTV's locator server system can't connect to your SageTV server. Either it doesn't know the correct internet IP address for your network (but the latest versions should update it right away before doing such a test), or there is still some sort of firewall issue blocking access on you system. Well, I'm sure there could be some other reason, but that's all I can think of at the moment.

Oh -- have you restarted SageTV? Or, when you turned the Placeshifter server on, did you toggle the main server off & back on so that the PS server got restarted also?

- Andy

What does "toggle the main server off & back on" mean? Restarting the PC? Restarting the UI? Restarting the SageTV Windows service (I'm not running in service mode)? Disabling/enabling the SageTV Server under Setup/Detailed Setup/Advanced? Or something else?

[Opus4]

Originally Posted by fastoy

What does "toggle the main server off & back on" mean?

This one:

Disabling/enabling the SageTV Server under Setup/Detailed Setup/Advanced

If you've recently enabled the Placeshifter server, but didn't restart SageTV or restart the server option, then the PS server isn't really started. (In the future, the STV will ask about this, so it shouldn't be an accidental issue. It isn't done automatically because it will temporarily disconnect all clients... something you may not want to do immediately.)

- Andy

[fastoy]

Originally Posted by Opus4

This one:

If you've recently enabled the Placeshifter server, but didn't restart SageTV or restart the server option, then the PS server isn't really started. (In the future, the STV will ask about this, so it shouldn't be an accidental issue. It isn't done automatically because it will temporarily disconnect all clients... something you may not want to do immediately.)

- Andy

That would be a nice thing to put in Appendix N in the manual. I've been working with George in support on this for almost a week and he hasn't asked about this.

I'll try this tonight. Thanks.

[Opus4]

It is mentioned in the Detailed Setup -> Advanced section of the manual, which the appendix links to, but I'll make a note to include it in the appendix too.

However, if you've restarted SageTV during the past week, it isn't the issue.

- Andy

[MattHelm]

I installed 5.0.4 and all went perfect with my D-Link DGL-4100.