INTERACT FORUM
More => Old Versions => JRiver Media Center 26 for Windows => Topic started by: Manfred on June 26, 2020, 04:43:54 am
-
I did change on my network. I can access the MC server through MS-RDP as well as through Asus iKVM. Also I see all the drives from my remote PC on the server . Fine! The server has now a new IP-Adr. *.*.*.xx Server is connected through a WLAN Stick with 866 Mbit/s to my Router. The MC Server has a different IP-Adr*.*.*.xy
If the MC client wants to connect to the server MC tries the IP-Adr. *.*.*.xy. Then it did not find it and suggest to load the local main lib. I can also not reach the IP-Adr. *.*.*.xy. via ping from my PC. If I login to the server I can ping *.*.*.xy.
DHCP is configured in my Fritzbox. The Fritzbox also sees the server. But it seems one comopnent can not do the route PC-> server (IP-Adr*.*.*.xx)->MC server (IP-Adr*.*.*.xy)
Any Idea?
-
I assume *.*.* are the same for all your components. Otherwise, your componemts sit on different subnets ... and router needs to be configured for that
without knowing more details its hard to help (also servers shoukd have static IP addresses )
i can try think of one scenario. is your cinnection like this?
client -> router -(wireless)-> Server -(LAN)-> MC server
aka ... your MC Server is directly connected to your Server
if it is then your router dont see MC Server ... and hence your client too
need to bridge LAN to wireless on Server
-
I have the following connections
PC (MC CLient)->Router->WLAN Stick->Server (MC Server)
and
Media Renderer (MC Client)->Server (MC Server)
-
Sounds like the firewall on the server is blocking incoming connections, which is the default on Win10. Try these:
- check that the network interface on the server is not marked as "public", switch it to "private network"
- Go to the firewall settings and add an exception for port 52199, or for "Media Center 26.exe"
- for Ping to work, go to "advanced sharing settings" and turn on Network Discovery for the Private profile.
Do NOT enable discovery and do NOT disable firewall on Public profile!
-
- check that the network interface on the server is not marked as "public", switch it to "private network"
That's already the case
- Go to the firewall settings and add an exception for port 52199, or for "Media Center 26.exe" (ftp://- Go to the firewall settings and add an exception for port 52199, or for "Media Center 26.exe")
That's already the case
I know the problem: The WLAN stick has an IP-Adress given through DHCP. That's fine but the WLAN Stick and so also the router then does not see the IP-Adress of MC server???
I found that strange because when I use Remote Desktop to connect to the server - I can work with MC on the server.
-
If the WLAN stick is connected to the server, then whatever IP it's getting IS the server's IP. If the server has additional network cards, they should have IPs in a different range, or the routing table would be messed up.
Please paste here the result of "ipconfig /all" and "route print" commands on your server.
Also, do you have any other security suite/antivirus/firewall on the server? If so, also check if they're not blocking network connections.
-
Thank you very much for all your help!
I decided to go back to my old solution with switch and WLAN Repeater in the living room and full DHCP. I did not thought about the complexity with the fixed IP-Adresses and the routing tables. I am not so firm with the network stuff and I must administrate that in the future, so I decided to go back to the DHCP solution and live with the switch and ethernet cables in the living room.
-
Good that it's working for you.
You may be overcomplicating the WLAN solution. If you want to try again with no cables:
- plug the USB WLAN dongle to the Server, leave it as DHCP. Whatever IP it receives, it's the server/MC IP address.
- unplug other LAN cables from the server - leave all other LAN interfaces as DHCP too. The server needs to have a single IP, not multiple. You can't have 2 links to the same router (well, you can, but that's advanced stuff, let's not go there).
- if you want you can assign a fixed IP to the server, you can do so in 1 of 2 ways:
> instead of DHCP, assign the fixed IP on the WLAN configuration
> alternatively, on your Fritz router, add a MAC-address reservation for that WLAN card so that it always gets the same IP via DHCP.
Anyway, cabled is always better/faster/more stable than WLAN, regardless of the advertised WLAN speed.