Moved Server to Windows 7 - no longer visible to client

[Robert Wise]

I moved my server to Windows 7 to support some other hardware and now the client cannot see the server. I thought it was the Firewall on the server, but I killed it and I still can't see the server. I can ping the server with the firewall off.

Any suggestions?

[davephan]

Does your new Windows 7 SageTV computer have the same IP as the old computer? If not, you may need to set the Windows 7 IP or change the client's configuration. It sounds like the client is a SageTV client computer instead of a media extender, since you pinged the Windows 7 SageTV computer. If the SageTV client is a computer, then you may need to modify the host file if a different IP is being used. You might also need to reconfigure the Windows 7 SageTV computer's workgroup to match the SageTV client computer's workgroup. You might need to make changes in your router if the ports are being blocked there. Is there any other firewall software running on the Windows 7 SageTV computer or the SageTV client computer?

Dave

[Robert Wise]

Originally Posted by davephan

Does your new Windows 7 SageTV computer have the same IP as the old computer? If not, you may need to set the Windows 7 IP or change the client's configuration. It sounds like the client is a SageTV client computer instead of a media extender, since you pinged the Windows 7 SageTV computer. If the SageTV client is a computer, then you may need to modify the host file if a different IP is being used. You might also need to reconfigure the Windows 7 SageTV computer's workgroup to match the SageTV client computer's workgroup. You might need to make changes in your router if the ports are being blocked there. Is there any other firewall software running on the Windows 7 SageTV computer or the SageTV client computer?

Dave

Yes, the IP is the same. Yes Client is a PC, but the extender can't see the Server either (one problem at a time ) I did join the Client's workgroup, but I will look at the name. Nothing on the router has changed.

Thanks.

[Robert Wise]

Checked the workgroup name and it is the same.

[Robert Wise]

Still no joy with this, I opened a ticket but no response yet.

I tried to connect the extender, but it says the Server is sleeping and a WOL request has been sent. I turned off Power Saving temporarily, but it did not make a difference.

Any help appreciated. (Where's the TV withdrawal emoticon? )

[jorton]

Is the Client machine XP?

[Robert Wise]

Originally Posted by jorton

Is the Client machine XP?

No, both are Win 7 x64. The client worked before I moved the Server from XP to Win 7. I've turned the Firewall off on both machines and the IP of the Server has not changed. It must be a Homegroup/Workgroup issue.

[davenlr]

Share a folder on the server (using windows) and set its security to all users, then try to access that folder from your pc using the windows explorer, computer name folder (not library or homegroup folder), copy a file to the server, read the file back. If there are any issues they should show up there. Get that working, and Sage should work.

You did reenter your client and placeshifter licenses (if applicable) into the server right?

[Savage1701]

I think someone asked this - do all your computers have the same Workgroup name? That's a biggie. Do you have a spare laptop/desktop you could temporarily put into the mix and see how it "saw" the server/client shares?

Dave seems to have the best acid test - get one to copy one way then try and copy it back.

I've had this as well between Win 7 machine shares, with no apparently valid reason why they stopped seeing shares. I've had it be a 1-way street where one machine saw the other one's shares but not in reverse. I've had them not see shares but I can ping them, use Access Remote PC freely between them, etc., so I know that in some ways they surely "see" each other.

I agree that the easiest way is to allow everyone/anyone any and all permissions to the Sage Server.

I have not worked much with Homegroups, but you may want to google "Master Browser Windows 7" and make sure the computer that is on most, probably your Sage Server, is the master browser. That way when your client is on it will look to the Server first.

I don't want to get into a whole network thing here, but there are cases where 2 computers "duke it out" to be Master Browsers and everyone on the network loses. I run a mixed XP/Vista/Win 7 network of up to 8 computers at once. I went into the registry of each and told them to ALWAYS look to my Sage Server as the Master Browser since it is on all the time. I don't know how it is on Win 7 but I know it can take up to 30-40 minutes for the XP-based Master Browser computer to poll and publish a new CPU, but that seems to be rare. Such can be the price for peer-to-peer networking. But, again, I can't speak to whether or not its like that with Win 7, as I do not tinker with my system as long as it works.

You can try this: http://scottiestech.info/2009/02/14/...ows-workgroup/

[Robert Wise]

Originally Posted by davenlr

Share a folder on the server (using windows) and set its security to all users, then try to access that folder from your pc using the windows explorer, computer name folder (not library or homegroup folder), copy a file to the server, read the file back. If there are any issues they should show up there. Get that working, and Sage should work.

You did reenter your client and placeshifter licenses (if applicable) into the server right?

Sharing a folder was no problem, but did not solve my issue.

The Client License is installed with the Client as I recall? I reinstalled the Cleint, but did not get asked for the License Key, nor did it solve my problem.

[Robert Wise]

Originally Posted by Savage1701

I think someone asked this - do all your computers have the same Workgroup name? That's a biggie. Do you have a spare laptop/desktop you could temporarily put into the mix and see how it "saw" the server/client shares?

Dave seems to have the best acid test - get one to copy one way then try and copy it back.

I've had this as well between Win 7 machine shares, with no apparently valid reason why they stopped seeing shares. I've had it be a 1-way street where one machine saw the other one's shares but not in reverse. I've had them not see shares but I can ping them, use Access Remote PC freely between them, etc., so I know that in some ways they surely "see" each other.

I agree that the easiest way is to allow everyone/anyone any and all permissions to the Sage Server.

I have not worked much with Homegroups, but you may want to google "Master Browser Windows 7" and make sure the computer that is on most, probably your Sage Server, is the master browser. That way when your client is on it will look to the Server first.

I don't want to get into a whole network thing here, but there are cases where 2 computers "duke it out" to be Master Browsers and everyone on the network loses. I run a mixed XP/Vista/Win 7 network of up to 8 computers at once. I went into the registry of each and told them to ALWAYS look to my Sage Server as the Master Browser since it is on all the time. I don't know how it is on Win 7 but I know it can take up to 30-40 minutes for the XP-based Master Browser computer to poll and publish a new CPU, but that seems to be rare. Such can be the price for peer-to-peer networking. But, again, I can't speak to whether or not its like that with Win 7, as I do not tinker with my system as long as it works.

You can try this: http://scottiestech.info/2009/02/14/...ows-workgroup/

The Master Browser is actually my Linux File Server, which is on 24/7.

Sharing a folder was no problem.

[Fuzzy]

workgroups, master browsers, file shares and such won't make a difference. The sage client simply connects via a direct tcp connection to the server, doesn't use any folder sharing, etc. If it cannot find the server, then there is something blocking it. Either it is in a different subnet than the server, causing the server to be unreachable (unlikely, since folder sharing works), or the server is blocking access to the ports (some firewall, not necessarily the windows one), or the server isn't listening for the client (make sure the Server is enabled in Detailed Setup -> Server).

[Robert Wise]

OK, so now it sees the Server with the Server Firewall turned off, this did not work before. Other than playing with the file sharing, the only other thing I did was to reinstall the Client (No changes to License Key). Once I turn the Fiirewall back on the connection is lost.

Both SageTv and SageTv Service are being allowed through the Firewall as Private AND Public, what other advanced setting is causing this?

Thanks.

P.S. I will likely go to Avast at some point to get AV protection, so this might solve my issue too.

[Fuzzy]

My solution is to not run a firewall on systems on my private network... they really serve no purpose, but to complicate things.

[Savage1701]

I agree with Fuzzy. I don't run a firewall, other than what my HotBrick has on it to protect me from the outside, for my Sage network.

I have a second ISP with a Netgear wireless router that has Guest Access enabled to totally isolate anyone who brings over a virused-up PC from contaminating my system.

But my Sage stuff is pretty much closed loop and not used for casual browsing or email, just Sage and Mr. Softy updates and such.