Upgraded Server - Client Wont Connect

[nwboater]

I just added an additional hard drive to our WHS machine and our SageClient (previously working fine) wont connect. I can get to setup on the client and it doesn't see the server.

Our HD100 and HD200 are working fine with the same server. The Client HTPC sees the Internet and JRiver Media Center15 sees the server so don't think it's a networking problem.

When I added the new drive it forced me to re-activate the WHS license with Microsoft. They had me enter a bunch of new code numbers that may have changed the server license. (Ridiculous of MS to put us through that just adding a HD!) Might this have something to do with the Client license not seeing the same WHS license?

I'm at a loss what to do and would sure like to get our Client Back.

Any ideas are very appreciated.

Thanks,
Rod

[gplasky]

Neber had to reactivate my WHS license and I have added drives 4 or 5 times on the same machine. That being said double check and make sure the IP address hasn't changed on the WHS server. Make sure you know the IP address of WHS and then co to the client, open a command prompt and type ping xxx.xxx.xxx.xxx being the IP address if the WHS and see if it responds.

Gerry

[nwboater]

Originally Posted by gplasky

Neber had to reactivate my WHS license and I have added drives 4 or 5 times on the same machine. That being said double check and make sure the IP address hasn't changed on the WHS server. Make sure you know the IP address of WHS and then co to the client, open a command prompt and type ping xxx.xxx.xxx.xxx being the IP address if the WHS and see if it responds.

Gerry

Gerry,

Thanks for the response. Some ?

1. I don't know the 'Old' IP address. Any way to find it out?

2. How do I find out the new address? When I run JRiver MC15 (which runs fine connected to the server) it shows an IP address at the top of the screen. Perhaps that is the servers address.

When I first turned on WHS after the new HD install it didn't show the drive. So I went into the BIOS and it did show it there. Perhaps entering and saving the BIOS triggered something MS doesn't like. Whatever it's sure a bad on them to have to do this reactivation and deal with any problems it may cause.

Thanks for your help.

Rod

[SomeWhatLost]

there may be an easier/more gui way to find the IP address, but the one way I remember is just open a command prompt on the PC in question (hit "run" tab/button thingy, type cmd<enter>) and type ipconfig...

[nwboater]

Originally Posted by SomeWhatLost

there may be an easier/more gui way to find the IP address, but the one way I remember is just open a command prompt on the PC in question (hit "run" tab/button thingy, type cmd<enter>) and type ipconfig...

Thanks for the tip.

ipconfig on the server returns an IP address, but I still don't know if this has changed from the 'Old' one.

Rod

[nwboater]

From the Client I pinged the server and it gave 4 good replies.

Rod

[SomeWhatLost]

did widows turn off the sagetv server bits? ie on the server setup/server/SageTV server = enabled?

on the client, in the sage shortcut properties do it have something like "C:\Program Files (x86)\SageTV\SageTV\SageTV.exe" -client -connect 192.168.1.xxx ?
does the 192.168.1.xxx part match whatever address your server is at?
(do clients actually do this bit? or is that just for when running the 'full sage' in client mode?)

on real sageTV clients is there a way to search for active sage servers? that could be fun/helpful?

are the proper ports on the servers firewall open?

[gplasky]

Go into Detailed Settings-General and turn off the Automaticall Connect to Server. Quit the Sage client and restart. It should automatically try to find the server and come back with an IP address of the server. Once connected renable the Automatically connect.

Gerry

[nwboater]

Originally Posted by SomeWhatLost

did widows turn off the sagetv server bits? ie on the server setup/server/SageTV server = enabled?

on the client, in the sage shortcut properties do it have something like "C:\Program Files (x86)\SageTV\SageTV\SageTV.exe" -client -connect 192.168.1.xxx ?
does the 192.168.1.xxx part match whatever address your server is at?
(do clients actually do this bit? or is that just for when running the 'full sage' in client mode?)

on real sageTV clients is there a way to search for active sage servers? that could be fun/helpful?

are the proper ports on the servers firewall open?

When I looked at setup/general/automatically connect to server it showed what I assume is the old IP address. I could not change it to the new address. Clicking on it would only change it to "No" or the old address.

I would never have thought to do as Gerry suggested, leaving it at "No" and restarting. To me that's counter-intuitive. But the main thing is it is working! And thank to you to for your help.

Rod

[nwboater]

Originally Posted by gplasky

Go into Detailed Settings-General and turn off the Automaticall Connect to Server. Quit the Sage client and restart. It should automatically try to find the server and come back with an IP address of the server. Once connected renable the Automatically connect.

Gerry

Gerry - For some reason the post I made thanking you for solving it was removed when I made the above post to Somewhat Lost.

Anyway thanks very much, your solution worked perfectly!

For some reason the WHS address got changed, I guess when MS did the reactivation. I'm still bummed that adding one hard drive put me through all this!

Rod

[SomeWhatLost]

the one thing I am confused on (well, the one thing related to this, if we open up the scope a bit, there is plenty I am confused about, but that's for another thread, or maybe even a psychiatrist or something...) is why is the client using an IP address for connecting with the server? wouldn't a name be better? or a mac address or something that wont change if you are using DHCP?

to the OP, the address changed because you are using DHCP on your server for its ip address, when you added the new HDD you probably had it turned off for a while.... this can and probably will happen to you again... you may want to consider setting a static IP (preferably outside the DHCP range) just so you never have to deal with this again...

[nwboater]

Originally Posted by SomeWhatLost

the one thing I am confused on (well, the one thing related to this, if we open up the scope a bit, there is plenty I am confused about, but that's for another thread, or maybe even a psychiatrist or something...) is why is the client using an IP address for connecting with the server? wouldn't a name be better? or a mac address or something that wont change if you are using DHCP?

to the OP, the address changed because you are using DHCP on your server for its ip address, when you added the new HDD you probably had it turned off for a while.... this can and probably will happen to you again... you may want to consider setting a static IP (preferably outside the DHCP range) just so you never have to deal with this again...

Thanks for your comments and suggestions here. Must admit I had heard the terms dynamic and static IP addressing before but had no clue what they referred to. After some Googling I think I now have a basic understaning.


Some comments and questions come to mind:

1. I too must question why SageTV Client uses IPaddressing. On our HD100 & HD200 extenders they appear to use the server name.

2. I'm surprised that I haven't had this Client problem before using dynamic IP addressing on the server. I do on rare occasion restart it.

3. Why doesn't Sage do something on the Client like it's done on the extender, ie show the server it's connecting to at startup? At least give a 'search for' option if it doesn't find the server.

4. I think I will change the server to a static address. Is there any downside to this?

Thanks,
Rod

[gplasky]

Answers below in blue

Originally Posted by nwboater

Thanks for your comments and suggestions here. Must admit I had heard the terms dynamic and static IP addressing before but had no clue what they referred to. After some Googling I think I now have a basic understaning.


Some comments and questions come to mind:

1. I too must question why SageTV Client uses IPaddressing. On our HD100 & HD200 extenders they appear to use the server name.
It all depends on your home network and how well you have DNS working. Servers names should resolve to an IP address but this is not always the case on home networks and how "well" they have been set up.

2. I'm surprised that I haven't had this Client problem before using dynamic IP addressing on the server. I do on rare occasion restart it.
The issue usually won't happen on a restart. It can happen depending on how long the server remains down and if it is down for awhile.

3. Why doesn't Sage do something on the Client like it's done on the extender, ie show the server it's connecting to at startup? At least give a 'search for' option if it doesn't find the server.
It does. If you don't have it set to automatically connect in the Detailed Settings.

4. I think I will change the server to a static address. Is there any downside to this?
None. Just make sure you reserve that IP to the MAC address of NIC card so DHCP doesn't try to hand out that IP address again.

Thanks,
Rod

Gerry

[GKusnick]

Originally Posted by gplasky

4. I think I will change the server to a static address. Is there any downside to this?
None. Just make sure you reserve that IP to the MAC address of NIC card so DHCP doesn't try to hand out that IP address again.

Instead of configuring a static IP on the server itself, and then also configuring the router to exclude that IP from DHCP, a better option is to just leave the server set for DHCP, and configure the router to give out a specific fixed IP to the server's MAC address. That way all the configuration is in one place and there's no possibility of conflict.

[nick_l]

The downside to this approach is that if your dhcp server dies (and considering it's probably a $50 Linksys or D-Link, it probably will) you will have to recreate all of that info again.

Im not saying that either approach is bad. I just wonder which would be easier for the average non-tech inclined user.

[GKusnick]

Most routers have a configuration backup/restore feature. At worst you can take a screenshot of the DHCP config page and save it somewhere in case of disaster.

[nwboater]

Gerry, Greg and nick_l,

Thanks for all the good information here.

I just tried setting Automatically Connect to NO. It does bring up the server Name and address at startup, which is what Gerry had me do when it originally failed to connect. If it would only auto connect after 5 seconds with a cancel button like the Extenders have I think I would leave it this way. For WAF I don't like to have an extra button press when everything is working normally.

In our case we have the WHS connected to a Cisco/Linksys SG-100-08 switch which is connected to a Linksys WRT 54GS Router.

Think I'll wait a little bit to fully understand the 'expert' suggestions before making any changes.

Thanks again.
Rod