NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
No NAS access from non-domain-member PC
Device:
ReadyNAS Pro 4
RAIDiator 4.2.19
Joined to Windows 2003 AD domain
Symptom:
I am trying to connect to an AD-protected share from a computer that is not a member of the domain, but am unable to do so no matter what credentials I supply. I have tried domain\username, domain.lan\username (the domain uses .lan as its TLD), just username, username@domain.lan, the actual email address associated with the username, administrator, domain\administrator, nas-name\administrator, nas-name\admin, etc., and nothing works. When I connect to the share from a domain member computer on which I am logged in as username I have no problems accessing the share. Guest access to the share is disabled. Does this mean that *only* domain computers can connect to the share? Other non-AD-protected shares on the NAS work fine from the non-domain-member computer. I just figured any computer could connect so long as the person has the correct credentials.
TIA
ReadyNAS Pro 4
RAIDiator 4.2.19
Joined to Windows 2003 AD domain
Symptom:
I am trying to connect to an AD-protected share from a computer that is not a member of the domain, but am unable to do so no matter what credentials I supply. I have tried domain\username, domain.lan\username (the domain uses .lan as its TLD), just username, username@domain.lan, the actual email address associated with the username, administrator, domain\administrator, nas-name\administrator, nas-name\admin, etc., and nothing works. When I connect to the share from a domain member computer on which I am logged in as username I have no problems accessing the share. Guest access to the share is disabled. Does this mean that *only* domain computers can connect to the share? Other non-AD-protected shares on the NAS work fine from the non-domain-member computer. I just figured any computer could connect so long as the person has the correct credentials.
TIA
3 Replies
Replies have been turned off for this discussion
- For whatever reason this problem fixed itself after a Windows Update and reboot. I had previously attempted the "net use * /delete" workaround to no avail.
For future reference, which of the logs you can download shows failed user login attempts? - Does the client computer you're using have the DNS server for the active directory listed?
- Yes it does. I believe the problem *may* have been related to me messing around with some Internet Expolorer Security settings. Specifically the setting for Local Intranet and Trusted Sites auto-logon. I may have had the option set to use the current logged on user's credentials to access sites in those zones. Off the top of my head those were the only settings I was messing around with at the time. I don't know if those settings affect Windows Explorer but I wouldn't put it past Microsoft. I'm thinking that because the logon credentials on that computer are not domain credentials, and that share is locked down to Active Directory users, the computer was trying to connect to the share using non-domain credentials and getting denied. That's just a guess though.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
