Client not connecting to the Server

[gregmo]

We can't get the client to connect to the server. We have it configured correctly, and we followed all the instructions, including the troubleshooting instructions. We made sure to put the correct key codes and still can't connect. We can ping the machines by both IP addresses and their names, so we know it's not a networking issue. It's an issue with Sage.

Please help. This needs to be fixed by the weekend or I'll have to go the Snapstream route. I'd prefer not to have to change after investing the time and money into Sage.

[dkardatzke]

Can you provide a little more information on what's happening and when. Include screen shots where you can.

[gregmo]

figured it out. The Sage client was version 1.3 and the server was on 1.4. It works now.

We haven't played with it much (just got the client working now), but can you configure it so the screen saver doesn't come on while it's playing? I hope so.

Also, this thing is utilizing up to 25% of bandwidth while the client is running. We are using a wireless G network. We have it on the highest possible encoder rate, so we'll play with the settings to see if we can get the utilization down. Looks like more than one client and you will probably need to go wired with your network.

[gplasky]

What I've done is disabled the Windows screensaver and any Power management for the monitor. Sage has it's own screensaver. Windows has a problem with any overlay-type video app. I've seen this with Windows Media Player 9 and WinDVD. Windows doesn't seem to know anything is going on when watching a video and the screensaver will kick in.


Gerry