How to move Sage client license from server?

[jominor]

I purchased Sage client and server back during the 1.4 days. The client was put on a machine with ip address 100. I've recently changed my router to a wireless version and changed my IPs. However, my Sage server is still looking for my client license on 100 instead of the new ip of 200.

How can I reset the SERVER or remove this IP from the Server's list and reuse my license on the same box, but with a different IP?

[stanger89]

I believe, restarting SageTV on the server should do the trick.

[jominor]

Originally Posted by stanger89

I believe, restarting SageTV on the server should do the trick.

I've actually restarted Sage on the server several times(that FF lock up problem) since doing this.

No joy, I'm afraid.

[stanger89]

You can try this:

From the FAQ:

If you are using the SageTVClient on more than one PC and accidentally entered the same license key from another PC you will get an error message - "Unable to connect to the SageTV Server".
To enter the correct license key, open your SageTV folder, right-click on the SageTVClient.exe file and create a new shortcut. Then right-click on the shortcut and go to Properties. Then enter in the Target line at the end after the quotes a space and then the word REGISTER. The correct entry will look like this: " C:\Program Files\Frey Technologies\SageTV\SageTVClient.exe" REGISTER. Then you will be prompted to enter the new license key and after your correct license key is accepted, and you can delete the shortcut you just created.

[jominor]

Originally Posted by stanger89

You can try this:

From the FAQ:

Unfortunately, that was the first thing I tried. The problem is that this allows you to set a new key for a client, but doesn't allow you to use the same key on the same machine if you've just re-IPed the machine.

In essence, if you want to put a move a client to a different machine or you need to, for whatever reason, change the IP, the Sage server bind the license to an IP.

I guess I'll have to send the support group an email.

[Opus4]

I suppose things might have changed in the last version that was released, but you used to be able to simply restart the server to get it to refresh the client connections, since it only remembered where the connections are currently coming from, not where they came from the last time the server was run.

Are you using service mode? If so, did you restart that too?

- Andy

[jominor]

Originally Posted by Opus4

I suppose things might have changed in the last version that was released, but you used to be able to simply restart the server to get it to refresh the client connections, since it only remembered where the connections are currently coming from, not where they came from the last time the server was run.

Are you using service mode? If so, did you restart that too?

- Andy

I'm running version 2.0, the pre-service version.

[Opus4]

Have you made sure that the new addresses aren't being blocked by a firewall or some such thing? My memory could easily be faulty, but I don't remember anyone having a problem restarting SageTV to be able to connect to a moved client in v2.0.

- Andy

[jominor]

Originally Posted by Opus4

Have you made sure that the new addresses aren't being blocked by a firewall or some such thing? My memory could easily be faulty, but I don't remember anyone having a problem restarting SageTV to be able to connect to a moved client in v2.0.

- Andy

I was able to ping it using the host name. Also, my other two Sage clients can reach it. I'm getting the IOException error that mentioned the client license specifically.

[nielm]

As you have multiple clients, try this:
Shutdown Server
Shutdown all clients
Startup server
Startup problematic client only...

If it works, (and another client then starts having problems) then you may be using the same licence key on another client.

IIRC, the client does not know that the failure to connect is due to the reuse of a licence, and the error message given is a 'generic' connection failed error message.

[jominor]

Originally Posted by nielm

As you have multiple clients, try this:
Shutdown Server
Shutdown all clients
Startup server
Startup problematic client only...

If it works, (and another client then starts having problems) then you may be using the same licence key on another client.

IIRC, the client does not know that the failure to connect is due to the reuse of a licence, and the error message given is a 'generic' connection failed error message.

I actually went in, using the REGISTER command and confirmed that the other client licenses are correct. Also, my problem client was the only one running at the time.

[Opus4]

Originally Posted by jominor

I was able to ping it using the host name. Also, my other two Sage clients can reach it.

Does that mean you were checking whether the client could contact the server, vice versa, or both?

I meant that since the client has a new address, the server may be blocked from talking to it. It isn't clear to me from what you wrote, but it looks like perhaps you were checking to see if the client could talk to the server due to the reference to the other 2 clients.

- Andy

[jominor]

Originally Posted by Opus4

Does that mean you were checking whether the client could contact the server, vice versa, or both?

I meant that since the client has a new address, the server may be blocked from talking to it. It isn't clear to me from what you wrote, but it looks like perhaps you were checking to see if the client could talk to the server due to the reference to the other 2 clients.

- Andy

I first purchased Sage 1.4 + one client and that was installed on a Sage Server and 1 client. The client was on IP x.x.x.100.

I recently swapped out my wired router for a wireless version. I also purchased two additional Sage clients for two laptops.

The new IP range was x.x.x.200 and higher. Each laptop received a new client. The original client was unchanged.

Now, because I suspect of the new IP range, the original client no longer works. Nothing has changed but a new IP.

As you said, I think the server is looking for the original license bound to ip 100 and now the machine is ip 200, which is being interpreted as a different machine using the same license.

Now what do I do?

[Opus4]

Originally Posted by jominor

As you said, I think the server is looking for the original license bound to ip 100 and now the machine is ip 200, which is being interpreted as a different machine using the same license.

Actually, that's what you said. As I said above, I don't recall ever hearing about SageTV remembering a client's address between sessions & refusing to connect to its license after it was moved to a new location & after SageTV (server) was restarted or the PC was rebooted. Again: I could be wrong about the server not remembering a client's address between sessions, but as far as I know, people were able to move the client license to entirely new PCs at different addresses & connect them after restarting SageTV.

What I suggested was making sure there is no firewall blocking access (from the server PC to the client PC and from the client PC to the server PC). It _sounded_ like you checked access to the server PC from the client PC, but since the client's address changed, I was suggesting making sure that the server PC has access to that new client PC's address. You may have already done that, but I wasn't sure based on the wording.

- Andy

[jominor]

Originally Posted by Opus4

Actually, that's what you said. As I said above, I don't recall ever hearing about SageTV remembering a client's address between sessions & refusing to connect to its license after it was moved to a new location & after SageTV (server) was restarted or the PC was rebooted. Again: I could be wrong about the server not remembering a client's address between sessions, but as far as I know, people were able to move the client license to entirely new PCs at different addresses & connect them after restarting SageTV.

What I suggested was making sure there is no firewall blocking access (from the server PC to the client PC and from the client PC to the server PC). It _sounded_ like you checked access to the server PC from the client PC, but since the client's address changed, I was suggesting making sure that the server PC has access to that new client PC's address. You may have already done that, but I wasn't sure based on the wording.

- Andy

Done it. Everything can see everything else. Certainly a puzzle. I routinely copy things to the server from the problem client. This is machine that I use to divx movies.

[stanger89]

This might be a really simple answer, but are you sure you're running the same version client and server?

[glbrown]

Another data point...

Hardware is changing here at the temporary abode. I installed the sage client (the only license I have) on another machine to test it. Turns out a PII 300 is a bit too slow. Shut down that client and start up my usual client and get the connection error. Bounce the server and the original client works again.

Moral:
a) The server is remembering IP adresses.
b) I will need a couple more client licenses as more testing ensues

-gary-

[jominor]

Now this is weird. As I've said, I've restarted the server and reinstalled the client. However, I decided to shutdown the Sage server application, attempt to connect using the client, and after the inevitable failure, restart the server, then try to connect using client.

It work.

I've restarted that server several times, but this time it worked. Shrug.

[jominor]

Originally Posted by stanger89

This might be a really simple answer, but are you sure you're running the same version client and server?

Yes. 2.0.20. A weird restart combination worked!

[Opus4]

I was searching for client/server connection issues & I found an older thread that starts off with another problem & then turns into basic connection problems. About the only things I know of at the moment are: that SageTV must have the server enabled, the client/server versions must match, the client license can't be in use elsewhere, and the firewall has to be open.

BTW: here is a post from someone commenting about which port they had to open in their firewall: 42024. File copying & everything else worked, but the client wouldn't connect until this port was opened when using the XP SP2 firewall. Edit: Also open port 7818.

glbrown: your client was remembered only while SageTV was still running. What your example shows is that SageTV is not tracking the client's address between server restarts, so that says it really shouldn't be the issue for jominor.

- Andy