• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About elitef

  • Rank
    Regular Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi All, I've been running Xpenology on a QNAP TS-1685. All in all the system runs well, but I'm using Surveillance Station within the VM as my primary source for recording all cams. It works well for the most part, but at times, it take a LONG time to connect to Surveillance Station, the camera's have been acting weird where the recordings are supposed to be 30 minutes, but instead, they sometimes are 12 min, or more, or less, so it looses connection for some reason. I am currently running a DS3617xs Xpenology build. I've allotted 16GB ram if that matters. Has anyone else experienced the loss of connection with Xpenology, whether on QNAP or not?
  2. Da ne, i xpenology tozje net, ono prosto timeout delayet i daeot tot msg. No obe sistemi, kynap i hrenology, oba vidni vsy darogy l, eto prosto kakayato hren s SS pochemyto. Dazje ne znayu gde nachat iskat risheniya.
  3. kak ponat? Dymyu chto da, lokalno, no ne znayu chto mozjet bit. Ne znayu yestli fishka s Xpenology, s QNAP, s kamerami, ili prosto netvork kakto tarmozit. Eto ne vsegda, inogda otchen bistra vklychaetsa, a inogda tak vobshe ne gryzit i potom esho gavorit error chto podkluchtisa ne mozjet.
  4. Nadeyus ktoto smozjet pomoch. Y menya 8.0.3-5159 i xpenology katoriy ystanovlin na qnap kak VM. Innogda, bistro zahodit dscem, a innogda ne podklychaetsa vobshe. Ne znayu pochemy.
  5. uzje probival, ne rabotala vserovno Plus, yestli i srabotalabi, chto ostonavlivayet nastayashego vladeltsa eto kombinatsii skazat chto etot lisens kod ego, a patom ya v pralote bobla
  6. zanet li kto kak mozjno ispolzivat' nastoyashiy lisense cod na xpenology SS? y menya yest' na 8 kamer cod i hotelbi ispolzivat ego na novayu versiu SS no on ne rabotayet iz za mac/sn kombinatsii
  7. Yes, I did that before installation. Model + SN + Mac = WORKS SN + MAC + DIFFERENT MODEL THAN THE SN/MAC BELONG TO = DOES NOT WORK
  8. I have already tried this in the past. Did not work. Used REAL combo SN/MAC but different model and it did not work. Give it a shot on your end, maybe it will, but from my experience it did not.
  9. Same here. I've tried the same last week with no luck. If you take a 3615xs SN / MAC from a real physical box and put it on the XPEnology 3615xs, then it might work, but if the models dont match up, it wont work apparently.
  10. elitef

    DSM 6.2 Loader

    Tried changing the SN / MAC to reflect a real syno that I have 1813 but apparently the system checks somehow that the model 3617 is not correct for the 1815 SN / MAC combo, so cannot log in online, quick connect, or verify surveillance station serial # Does anyone have any ideas/recommendations on getting this to work?
  11. elitef

    DSM 6.2 Loader

    This seems to have worked! Thank you VERY much. I have done SATA in VMwW as well as when setting up the initial VM in QNAP, so both are set to SATA and it is now working. Now to figure out how to get the Surveillance Station to work with a license pack that I have because I end up getting a message that the the connection failed when it tries to reach out to the backend server or something.
  12. elitef

    DSM 6.2 Loader

    Yes, I have done that already which is what I mentioned in my last post. I used the instructions from this youtube Video This worked for 6.1.7, but does NOT work for 6.2. I get stuck at the bootloader message to use find.synology.com but it is not discoverable on the network through the website or Synology Assistant.
  13. elitef

    DSM 6.2 Loader

    Funny enough, I saw your video yesterday. Your video shows 6.0.2 version which I've gotten to work just fine, as well as all the way up to 6.1.7. It is the 6.2 that I am having issues with. I've created the OVF file in VMwW but I have yet to be able to get it to work on the QNAP because it loads/boots to the screen where it says to use the find.synology.com but my SynoAssistant isnt finding it. When I did the same exact thing using the USB method by BootyTrap on youtube, I was able to create the USB fine, connected it to the QNAP, booted the VM with USB being the primary boot option and it worked just fine. I just do not want to use a USB in order to run it since it is within the QNAP. It is as if the 6.2 loader somehow requires something different in VMwW in terms of configuration compared to the older version for 6.1.7.