INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: )p( on January 24, 2013, 09:45:04 am
-
This is probably a weird coincidence but today I could not connect to the library server on our local network from a client. I checked the forum it was down. As soon as I could connect again to the jriver forum I also could connect to the server again. All other internet connectivity was fine and the client and server are on the same home network. Weird ;)
-
This is probably a weird coincidence but today I could not connect to the library server on our local network from a client. I checked the forum it was down. As soon as I could connect again to the jriver forum I also could connect to the server again. All other internet connectivity was fine and the client and server are on the same home network. Weird ;)
No coincidence same hear. Internet was fine but could not connect to library server.
Why is Media Center connecting to your JRiver domain? This seems very odd.
The JRiver website was also down during the same time.
-
I would presume that the client connects to the jriver domain to fetch information about the server access key (IP & Port) if you don't want your client to do this simply connect to the server using the IP:Port format instead 8)
-
And how would you do that?
-
(http://i47.tinypic.com/34nii6q.jpg)
-
Oh.... my.... god! When did this happen? :D
-
Not sure tbh, has it not always been there ?
-
Just as a sidethought, wouldn't it make sense for the client to 'cache' the access key information unless it is unable to connect? preventing the behaviour the OP saw.
(this would only make sense if I was correct earlier?)
-
Just as a sidethought, wouldn't it make sense for the client to 'cache' the access key information unless it is unable to connect?
I've had the impression that this was the case. I do not know what could have broken this though. Requests for adding IP and port to those settings have been a repeating issue up until a very few months ago. So I believe it's been added in the latest 50 builds or so. Tried the IP and port connection to my library server now, and it worked very well.
Thanks to JRiver for adding this!
-
I've had the impression that this was the case. I do not know what could have broken this though. Requests for adding IP and port to those settings have been a repeating issue up until a very few months ago. So I believe it's been added in the latest 50 builds or so. Tried the IP and port connection to my library server now, and it worked very well.
Thanks to JRiver for adding this!
No, I've NEVER used the access key. You've been able to specify an address/port since the beginning of MC17 at least, if not MC16...
-
Indeed. Just need the same ability from within Gizmo and all bases would be covered.
-
Just a reminder that you only get Wake-on-LAN if you use an Access Key.
-
Indeed. Just need the same ability from within Gizmo and all bases would be covered.
THAT'S what I remember :) It's the access from Gizmo! You can't specify an IP and port there.
-
Just a reminder that you only get Wake-on-LAN if you use an Access Key.
But if you use an access key, you lose the ability to connect when either your internet is down or JRiver is down for some reason. Cable out, no problem I will just watch MC - but wait no Cable = no internet = no MC. Seems odd that WOL would require a phone home to the mothership, but since my library is up 24/7 (unless doing maintenance to that VM) I don't currently have that need.