I recently added a Win10 client to our local domain. This one machine (of ~20) cannot connect to the ReadyNAS 2100 NAS we use for file storage. We add file shares (hosted on the NAS) to all Windows 10 clients using GPO. The domain is a samba AD domain (Univention Corporate Server).
Troubleshooting so far:
- I can ping the NAS from the client (hostname and IP address).
- nslookup successfully resolves the NAS by hostname.
- GPO modelling indicates the file share policy is successfully applied to the client
All other clients receive the same GPO (in the same ou) and can access the shares
I can't access the NAS web interface - I get a 'connection refused error'.
- The problematic client can only 'see' four machines when browsing the network in Windows Explorer, but can connect to everything (except the NAS) by IP address.
I cant work out if this is a DNS issue, a kerberos issue, or some strange faulty hardware/software issue.
Anybody got troubleshooting suggestions?