# Disqualified after 3 years

**URL:** <https://forum.storj.io/t/disqualified-after-3-years/23645>\
**Category:** troubleshooting\
**Tags:** windows-gui, refs, junctions, disqualification, hardware\
**Created:** [August 30, 2023, 11:53pm UTC](https://forum.storj.io/t/disqualified-after-3-years/23645 "2023-08-30T23:53:10Z")\
**Posts on this page:** 1\
**Showing post:** 68

<div class="post-metadata">

**Author:** ![Toyoo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/toyoo/32/1126_2.png) [@Toyoo](https://forum.storj.io/u/Toyoo)\
**Post date:** [September 5, 2023, 9:52pm UTC](https://forum.storj.io/t/disqualified-after-3-years/23645/68 "2023-09-05T21:52:24Z")

</div>

> [@AndMetal](#):
>
> My point is the node is already indirectly doing this checking as part of its normal function

What do you mean here?

> [@AndMetal](#):
>
> something like NFS might not support exclusive file locks in the same way newer versions of NFS or CIFS/SMB would, but it seems like a bit of a stretch to me to declare that all remote storage options (other than ISCSI) are a non-starter

“Not supported” means “not supported”. You do it on your own responsibility, and if it fails because of a networked file system, the node will not be reinstated. I’ve briefly operated an SMB-based storage node and I know [it can work](https://forum.storj.io/t/node-operating-with-remote-drive/19782/4), but I had to do additional engineering and it wouldn’t be Storj Inc.'s fault if I made a mistake doing so.

Storj Inc. does not test this configuration, does not promise it will be reliable, will not reinstate disqualified nodes on SMB.

---

_[View the full topic](https://forum.storj.io/t/disqualified-after-3-years/23645)._
