inzombyac 69 Posted February 16, 2015 Share Posted February 16, 2015 I posted about this in the new beta thread, but wanted to post as a separate topic as it has been a new annoyance since updating to the 251 beta. I generally have my MBS machine sleep when not streaming and utilize the WOL feature to wake it up when a client connects. Since the beta, if the MBS server machine is asleep, I get the Connect pin prompt from MBC. If I back out of MBC and give my server enough time to wake up, it works fine. It seems that the client is not giving the server enough time to wake. I get this same exact behavior with the Roku client as well. Here's a link to a log of a session where this happened if this helps: https://dl.dropboxusercontent.com/u/9445055/MBClassic-7220156bd89371e3a841e0b2f23e1dadf83126.log I'm hoping that there can be an adjustment to give the server more time to wake up, or more intelligent processing in the client once the client has created a connection with the server. The current behavior is confusing to my family and is different than before. Previously, if the server took a long time to start, so did the client which was fine. For now, I am resorting to using a custom WOL script on the client when it is started to wake the server before going into MBC. This doesn't help other clients such as the Roku however. Link to comment Share on other sites More sharing options...
ebr 14949 Posted February 16, 2015 Share Posted February 16, 2015 Yeah, I'm not sure exactly how to deal with this without slowing down everyone necessarily and I haven't had time to do much investigation. Link to comment Share on other sites More sharing options...
Solution ebr 14949 Posted February 16, 2015 Solution Share Posted February 16, 2015 Okay, I tried something. Please try the dev version I just put up (253). Thx. 1 Link to comment Share on other sites More sharing options...
inzombyac 69 Posted February 17, 2015 Author Share Posted February 17, 2015 Just tried the dev version and it has the same effect. This was on a different client, but the client only gave the server about 6 seconds and then went to the pin screen. There is no timeout message in this log. MBClassic-16220154f5b85b3165d4f1fb4da4e567ebe67b3.log Link to comment Share on other sites More sharing options...
ebr 14949 Posted February 17, 2015 Share Posted February 17, 2015 Please try it on the same machine as before. That one is configured differently. It is configured to find the server automatically instead of to connect to a specific one. Link to comment Share on other sites More sharing options...
inzombyac 69 Posted February 17, 2015 Author Share Posted February 17, 2015 I tested the client remotely and it works now (and faster wake then before). Just need to confirm that the server machine is sleeping properly when I get back home. Link to comment Share on other sites More sharing options...
inzombyac 69 Posted February 18, 2015 Author Share Posted February 18, 2015 WOL works again. Thanks ebr. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now