• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About fwiler

  • Rank

Recent Profile Visitors

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

  1. That's unfortunately is not the right question to ask. It may very well be Unraid and how it handles or identifies your hardware, but you have to narrow down the issue first before you can fix it. All the other one's you have tried, may be using a different driver for the nic (This is just an example) It could be chipset, memory controller, sata controller, etc. In my example we had issues with Broadcom nic that came with Dell server. It was on the Windows WHQL list It had the same issue you describe where you can start a transfer, and then it just slowly dies down to 0.
  2. I think it's pretty much telling you. You've run out of memory. Make sure your VM hasn't been allocated more memory than what unraid and your vm need + overhead.
  3. Having a separate account for Veeam is actually recommended, as is most backup software. It's not unusual because you can't have same user account accessing same share and backup at same time. It would create a massive amount of errors and /or corruption. Just don't become an admin You have to keep track of accounts for hundreds of different services and security features to do it correctly.
  4. This is the correct answer for a domain joined computer. Otherwise Windows will automatically assume you are trying to use a Windows domain user and try to authenticate to the domain controller. Example. Login with user Administrator will login to domain Administrator. To login to Administrator on local computer you have to type .\Administrator for user name.
  5. This sounds very similar to a nic driver problem. I see this quite often on Windows server side connecting with clients. Especially with older nics from Broadcom or Realtek.. but also on Intel. Usually upgrading the firmware of the nic will help, but also knowing the driver being used. If Unraid is not using the correct files needed or misidentifies your nic, then you will see this problem. Also an issue- Multiple Windows machines with same user signed in. This will cause issues with shares. Especially prominent if Settings > Accounts > Sync your settings. By default,