File Share/Domain issue
-
- New here
- Posts: 6
- Joined: Wed Nov 23, 2022 8:43 pm
File Share/Domain issue
Hi,
I've set-up my NAS as a temp back solution, but i'm having a slight issue. I've added it to my Windows Domain and it has joined fine. I can access it via Name and IP from my 2 domain controllers fine and all works as it should but I can not access it from any other device on the network just the 2 domain controllers.
Any idea what might be causing this or a potential way of resolving it?
I've set-up my NAS as a temp back solution, but i'm having a slight issue. I've added it to my Windows Domain and it has joined fine. I can access it via Name and IP from my 2 domain controllers fine and all works as it should but I can not access it from any other device on the network just the 2 domain controllers.
Any idea what might be causing this or a potential way of resolving it?
- dolbyman
- Guru
- Posts: 35273
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: File Share/Domain issue
What happens when you try?
"can not access" isn't really revealing any error messages
"can not access" isn't really revealing any error messages
-
- New here
- Posts: 6
- Joined: Wed Nov 23, 2022 8:43 pm
Re: File Share/Domain issue
"Windows cannot access \\*SERVERNAME""
Check spelling name etc - But i'm able to connect from the DC without any issue so the name/spelling is correct
Check spelling name etc - But i'm able to connect from the DC without any issue so the name/spelling is correct
- dolbyman
- Guru
- Posts: 35273
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: File Share/Domain issue
and you have assigned domain user/group permissions to the shares?
-
- Experience counts
- Posts: 2043
- Joined: Thu Mar 03, 2016 1:11 am
Re: File Share/Domain issue
Did you try to access by IP too (\\1.2.3.4 - replace with IP of your NAS)?
Regards
Regards
A raid is never a substitute for backup! Never!
Deadbolt - READ 1st post!!!
Deadbolt - information
Deadbolt - find your OP_RETURN!
VPN=VPN? No!
How to clean up your NAS after malware attack
www.raidisnotabackup.com
Deadbolt - READ 1st post!!!
Deadbolt - information
Deadbolt - find your OP_RETURN!
VPN=VPN? No!
How to clean up your NAS after malware attack
www.raidisnotabackup.com
-
- New here
- Posts: 6
- Joined: Wed Nov 23, 2022 8:43 pm
-
- New here
- Posts: 6
- Joined: Wed Nov 23, 2022 8:43 pm
- dolbyman
- Guru
- Posts: 35273
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: File Share/Domain issue
can clients at least ping the NAS (name or IP)?
-
- New here
- Posts: 6
- Joined: Wed Nov 23, 2022 8:43 pm
- dolbyman
- Guru
- Posts: 35273
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: File Share/Domain issue
Do you have ABE and ABSE enabled ? (if so, that would hide shares and folders from users without correct permissions)
-
- First post
- Posts: 1
- Joined: Tue Nov 29, 2022 11:31 pm
Re: File Share/Domain issue
qnap is definitely an incompatible device for domain users. It has issues with the domain structure.
- dolbyman
- Guru
- Posts: 35273
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: File Share/Domain issue
works fine here (domain user/groups with folder permissions)
care to elaborate or just rambling?
care to elaborate or just rambling?
-
- New here
- Posts: 6
- Joined: Wed Nov 23, 2022 8:43 pm
Re: File Share/Domain issue
Hi Guys,
Thanks for everyone's input. I finally managed to work it out!
It appears that somehow a IP block list was populated (no idea how) it was a range of IP's typically the devices I tested were all in the blocked range, Whereas the DC's weren't. What was odd was that when you rebooted the NAS the servers in that range that was blocked worked and then after a few mins would stop. I'm assuming it takes a while for the qnap service that runs that feature to work which is what was helping to make it even more confusing and thinking it was a windows issue.
Thanks for everyone's input. I finally managed to work it out!
It appears that somehow a IP block list was populated (no idea how) it was a range of IP's typically the devices I tested were all in the blocked range, Whereas the DC's weren't. What was odd was that when you rebooted the NAS the servers in that range that was blocked worked and then after a few mins would stop. I'm assuming it takes a while for the qnap service that runs that feature to work which is what was helping to make it even more confusing and thinking it was a windows issue.