Page 1 of 4
Server not found via remote connection.
Posted: Sat Dec 31, 2022 5:47 pm
by Lukes
Hi,
I have a movie server running on my PC, and I'm trying to access it from another network remotely, but it's not working.
I have already forwarded port 5001 on the router, but it only works for a few minutes and then the server cannot be found remotely. It just reappears again after restarting the router,
What could be happening?
Re: Server not found via remote connection.
Posted: Sat Dec 31, 2022 9:20 pm
by rhayy
for security purposes, you should not allow the access to the service outside your network.
try and set up a VPN instead.
Re: Server not found via remote connection.
Posted: Sun Jan 01, 2023 2:40 am
by Lukes
That's true.
But actually, I have two routers connected on the same local network, and I want to access the server on the other router.
I'm trying to forward ports on Router 2, but Internet access would actually be access through Router 1.
I don't know how to explain it well.
Here is a picture of the topology of the network.
Re: Server not found via remote connection.
Posted: Sun Jan 01, 2023 4:07 pm
by mik_s
Accessing UMS from outside the local network is not it's intended function, I have heard it is possible but have no idea how to do it.
From what I remember it needs more than port forwarding to work as there are other protocols used for DLNA and UPnP that need to be shared between routers too, but that is my limit on networking knowledge.
It may work if both routers were on the same subnet, with all devices using 192.168.0.x instead of being split 192.168.0.x and 192.168.1.x
Re: Server not found via remote connection.
Posted: Sun Jan 01, 2023 4:59 pm
by Lukes
It seems to be really complicated.
I noticed that the remote port of the UMS process is not fixed, it alternates a lot between 30,000 and 45,000 randomly.
Do you know how to better stabilize the remote port of this javaw.exe process?
I think the problem must be related to this.
Re: Server not found via remote connection.
Posted: Sun Jan 01, 2023 7:10 pm
by mik_s
Sorry I have no idea. I don't think UMS uses a fixed remote port and it may be assigned by the router or OS.
The ports I know of that UMS uses by default is 9001 for the web interface, 9002 for the web player and 5001 for the server.
Re: Server not found via remote connection.
Posted: Mon Jan 02, 2023 12:53 am
by Lukes
This is very confusing.
I will try to open all these ports on Router 2 as well. UDP port 1900 is also used isn't it?
I'll try to capture the events in the trace log, so I'll post them here. Maybe it helps.
Re: Server not found via remote connection.
Posted: Mon Jan 02, 2023 1:13 pm
by Lukes
This message appears in the trace log:
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:10:37 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
What is UPC??
Re: Server not found via remote connection.
Posted: Mon Jan 02, 2023 1:53 pm
by Lukes
The log continue:
22:50:20 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:50:35 WARN UPnP specification violation: Not producing <retval> element to be compatible with WMP12: [(ActionArgument, OUT) ConnectionIDs]
22:50:35 WARN UPnP specification violation: Not producing <retval> element to be compatible with WMP12: [(ActionArgument, OUT) AuthorizationGrantedUpdateID]
22:50:35 WARN UPnP specification violation: Not producing <retval> element to be compatible with WMP12: [(ActionArgument, OUT) Result]
22:50:35 WARN UPnP specification violation: Not producing <retval> element to be compatible with WMP12: [(ActionArgument, OUT) ValidationSucceededUpdateID]
22:50:35 WARN UPnP specification violation: Not producing <retval> element to be compatible with WMP12: [(ActionArgument, OUT) AuthorizationDeniedUpdateID]
22:50:35 WARN UPnP specification violation: Not producing <retval> element to be compatible with WMP12: [(ActionArgument, OUT) ValidationRevokedUpdateID]
22:50:35 WARN UPnP specification violation: Not producing <retval> element to be compatible with WMP12: [(ActionArgument, OUT) Result]
22:50:35 WARN UPnP specification violation: Not producing <retval> element to be compatible with WMP12: [(ActionArgument, OUT) RegistrationRespMsg]
22:50:41 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
22:50:41 WARN UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'Wireless Router TL-WR740N'
Re: Server not found via remote connection.
Posted: Mon Jan 02, 2023 2:45 pm
by boss
@Lukes
Is there a reason why "router 2" is set to a different IP range than "router 1"
It looks as if you have "Router 1" connected to the WAN port of "router 2" and "router 2 supplying DHCP services on a different IP range.
Your system would then be getting double NAT which is not good.
Cannot you connect "Router 1" to a LAN port on "Router 2" and then turn off DHCP on "router 2". In effect "router 2" would just be acting as a switch.
That way, all DHCP would be controlled by "Router 1" and the PC IP would be in the 192.168.0.x range.
Then port forwarding would just have to be done on "router 1".
