Then you most likely are in his home!
So i removed the share from my friend, updated the FW on my QNAP, rebooted, put the latest version of PMS on QNAP, rebooted. At that point the looking for server just kept spinning. So, I ran ClaimIT and now Iām stuck at this: 
That indicates that your QNAP is already claimedā¦
You need to look in your Preferences.xml file then to see to whom itās claimed towards
See this post: PMS auf Qnap lƤuft nur als Client
Hereās what the file contains:
<?xml version="1.0" encoding="utf-8"?><Preferences OldestPreviousVersion="1.13.5.5291-6fa5e50a8
MachineIdentifier="95d64196-b60b-4007-90f0-d9ccb2ade4b3
ProcessedMachineIdentifier="f2351840c4749896a9d1b0a6e4216f17f6b53da6
AnonymousMachineIdentifier="b60e42b0-b428-41b5-848f-3e1718eb1a2e
GracenoteUser="WEcxA5V/9dyZkAQurGsOaGi0GI/JAbKdvb0jQEcHxA3+OOdVBAgyhGWww3K6NpNk8O3ej7YJSZeeWO9CSG+H3RGVdXs+n1pL7ADEN9LobMMHW41E7zgwla5PynC8GO847xr0Wf8FBkYrsa/lPOvkpt+JIV5TRaJEfDrbpqzIeENME5TvSYPUU5GSRs12Tn/FNHDT2w==
MetricsEpoch=ā1ā CloudSyncNeedsUpdate=ā0ā/>
So Iām not really sure where to make an adjustment.
Correct, so other option is that you are not using private address space?
If so, copy the bash script to your QNAP, and run it via putty, as well as use 127.0.0.1 when prompted for an IP address
which bach script? (sorry I should probably know but I dont)
claimpms.sh
so i ran the shell script as instructed on the qnap via putty and it all came back fine. It asked me to close the browser and reopen to http://127.0.0.1:32400. Well being that my server is not actually at that address it wouldnt work. so i substituted my address for the 127 address and I have the same problem. So, I ran the script again and got this:
I also tried rebooting the QNAP. Then stopping and starting the PMS. Unfortunately, I still cant find the PMS server on my QNAP and attach it to my account. Still get the endless āLooking for serversā spinner.
Sadly, I havenāt been looking at your logs until now 
Log says: Mar 21, 2019 22:36:34.902 [0x7f3a9d791740] DEBUG - Detected primary interface: 30.30.5.38
It should have worked using 127.0.0.1 but seems like it doesnāt anymore
Please see Qnap faq.....read me first! Q22, and change your IP Address, as well as make sure, that it after that can reach internet and DNS.
Then run the bash script again
Ok, so i have to reconfigure my networkās address space for this? Goody. One quick question, while i go through thisā¦Is there a known good way to confirm the qnap can get to the internet and dns? A utility or something?
Use SSH or putty, then ping ping-test.net
ok. thanks. let you know how she goes.
1 Like
ok. so i used an ip address schema from the list in the faq.
successfully pinged several IPs from the qnap via putty. all good.
ran bash script using new IP address on QNAP. Fail, status 401
ran bash script using IP address 127.0.0.1. Fail, status 401
tried launching PMS from QNAP. Opened tab in browser and did the āLooking for serversā death spin for about 10-20 minutes before i gave up.
what now?
Scratching head hereā¦
To confirm PMS is running fine, please from your workstation, browse to:
http://<IP_OF_QNAP>:32400/identity
Does that returns an xml?
by the way im cool with starting over if it means getting it working. its basically a brick on my desk right now and iām on the verge of sending it back, honestly.
the supplied directions are not accurate and do not work as described. So, if there is a known way or document to get this box setup and working properly id like to do that. more important to get it working than anything else.
Getting close to run out of ideas here, and due to aboveā¦
Try this:
In QNAP AppCenter, disable PMS
Then using like WinSCP, rename your Preferences.xml file to Preferences.xml.old
Then start PMS again from the AppCenter, and wait 5 min.
Then try to browse to http://<IP_Of_QNAP>:32400/web
With above, the whole identity of PMS is gone, and the prefs file should be repopulated
When browsing towards it, please use a browser in Incognito mode, to make sure we are not tricked by a browser as well
ok will do.
And FYI: Bedtime here, so TTYL 
right ok. what timezone are you in? (for future reference)
