alientm
-
Posts
12 -
Joined
-
Last visited
Posts posted by alientm
-
-
Can i use this loader to DS3615xs ?
-
Thank you for your help and explanation.
I changed the rsync port to another one (the service works correctly), OpenVas no longer shows port 22 vulnerability. On the new port it did not show high vulnerability, only Log:"The service closed the connection after 0 seconds without sending any date
It might be protected by some TCP wrapper " -
-
-
22 minutes ago, Polanskiman said:
Tell me, where are you running OpenVas from?
Can you explain this question to me more?
I do not understand them very much (I translate to PL) -
However, with SSH disabled, I can not log in through putty (Putty closes itself when trying to login). When I enable SSH - I can log in through putty.
Is it possible that port 22 is open for Hyperbackup or folder synchronization (rsync)?
-
-
Currently working on DSM 6.1.5-15254 and OpenVas finds me critical vulnerability on port 22.
The SSH service is disabled (no checked box at SSH).Any advice why does SSH work when it's off?
-
Where to get vmdk bootloader for Vmware?
-
If you use ESXi 5.5 (or newer)
1) Use this loader (jun's)
https://mega.nz/#!5koz0ZjZ!SLWdLCD2db22 ... m-aJQ4w2gI
My ESXi 5.5 can not see the file DSM_6.1-disk1.vmdk when i try to add HDD (Use an Existing Virtual Disk), any suggestion ?
-
Vmware vSphere 5.5 environment.
Previously worked properly DS3615xs 6.0.2 Jun's Mod V1.01 + 6.0.2-8451
I have tried DS3615xs 6.1 Jun's Mod V1.02-alpha + update by Synolgy Assistant (DSM_DS3615xs_15047.pat).
Something goes wrong - Synology Assistant find DS3615xs with but status is "Recoverable", when I try use "Recover system", DSM reboot and still Assistant show "Recoverable"
I try back to DS3615xs 6.0.2 Jun's Mod V1.01 but still the same problem.
Is there a chance to run DSM properly?
DSM 6.2 loader does not run correctly in VirtualBox/VMWare
in DSM 6.x
Posted
I have the same problem on ESXi 6.5, trying to run the new ds918 loader but I still have the message: "screen will stop updateing shotly, please open ..."
I tested on the E1000 and VMXNET3 network card. After the startup, the same message and CPU usage for the virtual machine are 90-100%.