More > JRiver Media Center 32 for Windows
Media Server question
Mr Swordfish:
And strike most of that. I was testing the client laptop via a wifi hotspot on my cel phone to connect via an external network instead of the LAN. For whatever reason, the client laptop reverted back to using the LAN which is why it seemed to work.
The good news is that the router UI is now showing that the library PC is handling traffic on port 52199. Using https://canyouseeme.org/ I can verify that port 52199 is visible. The bad news is that it still won't connect.
There's a sentence in the documentation that says "If a large library is failing, create a new smaller library and share that. You must load the smaller library on the Server machine before connecting from the client. " So maybe this is the failure point?
craigmcg:
In my experience, if I want anyone outside my home network to be able to access my JRiver media server I have to set a static IP for the network connection for my server pc so that I can tell my ISP modem/router to forward any traffic on port 52199 to the static IP address of my server. The static IP has to have the same first 3 sets of numbers as the internal IP of your ISP modem/router; in my case the router is 192.168.250.1 and my JRiver media server pc IP is 192.168.250.4.
Once this is done, I can use the library server functionality on any client/playback pc using the access key and tell Windows Firewall to allow traffic when it asks on both the server and client/playback pcs.
I don't have an AT&T modem but I found these links which might help
https://www.att.com/support/article/u-verse-high-speed-internet/KM1010280/
https://www.att.com/support/article/u-verse-high-speed-internet/KM1215101/
https://www.att.com/support/article/u-verse-high-speed-internet/KM1053197
Good luck because it's great to be able to share your library as desired!
JimH:
Your internal server needs to be at a static address, but most DHCP servers on routers handle that. It's an internal address, assigned by the DHCP Server, usually running on your router.
If the outside address changes because your ISP changes it, the Access Key will still work, after a few minutes.
Mr Swordfish:
--- Quote from: craigmcg on July 29, 2024, 07:16:17 pm ---
I don't have an AT&T modem but I found these links which might help
https://www.att.com/support/article/u-verse-high-speed-internet/KM1010280/
https://www.att.com/support/article/u-verse-high-speed-internet/KM1215101/
https://www.att.com/support/article/u-verse-high-speed-internet/KM1053197
Good luck because it's great to be able to share your library as desired!
--- End quote ---
Thanks for the links. I'll take a look when I get back to my main PC is a week or so.
Mr Swordfish:
It took me a while to get back to this, but I'm still unable to get it to work.
One issue seems to be that when the client tries to connect to the instance with the library, the ip address it's trying is different than the ip address that is displayed at https://www.whatsmyip.org/
Is the access key looking up the wrong ip address? If that's wrong noting is every going to work...
Navigation
[0] Message Index
[*] Previous page
Go to full version