|
Kinsky, MinimServer, and QNAP
|
|
19-09-2014, 19:30
Post: #21
|
|||
|
|||
RE: Kinsky, MinimServer, and QNAP
(19-09-2014 18:07)gnomus Wrote: Yes, I should have included this. The Kinsky PC is upstairs connected by Ethernet cable to the router. The Synology is also upstairs connected to the router by an ethernet cable. OK, so the missing multicast messages would have followed this route: Kinsky[PC] -> Ethernet cable > upstairs router -> Airport Extreme -> Airport Express -> downstairs switch -> MinimServer[QNAP] I will look at the log file to see what it reveals. What are the IP addresses of the Kinsky PC and the QNAP? |
|||
|
19-09-2014, 19:48
(This post was last modified: 19-09-2014 19:52 by gnomus.)
Post: #22
|
|||
|
|||
RE: Kinsky, MinimServer, and QNAP
(19-09-2014 19:30)simoncn Wrote:(19-09-2014 18:07)gnomus Wrote: Yes, I should have included this. The Kinsky PC is upstairs connected by Ethernet cable to the router. The Synology is also upstairs connected to the router by an ethernet cable. I can find out the IP address of the QNAP quite easily. How do I find the IP of the PC? And ... is it OK to post these numbers publicly here? (Excuse my ignorance) UPDATE: OK found a way of getting my PC IP - I have sent these to the support e-mail address |
|||
|
20-09-2014, 15:59
Post: #23
|
|||
|
|||
RE: Kinsky, MinimServer, and QNAP
(19-09-2014 19:48)gnomus Wrote:(19-09-2014 19:30)simoncn Wrote:(19-09-2014 18:07)gnomus Wrote: Yes, I should have included this. The Kinsky PC is upstairs connected by Ethernet cable to the router. The Synology is also upstairs connected to the router by an ethernet cable. Disabling OpenVPN - as suggested by Simon - seems to have cured this issue. |
|||
|
20-09-2014, 17:30
Post: #24
|
|||
|
|||
RE: Kinsky, MinimServer, and QNAP
(20-09-2014 15:59)gnomus Wrote: Disabling OpenVPN - as suggested by Simon - seems to have cured this issue. In slightly more detail: It looks like the problem was caused by having the QNAP VPN Service (OpenVPN server) enabled. This adds a second "virtual" network adapter for the VPN, which causes MinimServer to send UPnP discovery announcements over the VPN adapter as well as the regular adapter. Depending on how the network routing tables are set up, the duplicate announcements might be received by the control point and the control point might get confused by the duplicates and attempt to contact MinimServer on the wrong IP address. If anyone is seeing problems with discovery of MinimServer being unreliable, it would be a good idea to check whether a VPN server is enabled on the NAS that is running MinimServer. If a VPN server is running, you have two options: 1) If you don't need to run a VPN server, disable it and then restart MinimServer. 2) If you need to run a VPN server, set the ohnet.subnet property on the System tab of the MinimServer Properties window (not the "Options>Properties(watch)" window) to the correct subnet for the non-VPN adapter and then restart MinimServer. See this section for more information. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



