Insights /Windows Server and file permissions

A file share works by IP address but fails by server name: where is the problem usually located?

When IP access works but name access fails, investigate DNS suffixes, A/AAAA records, stale caches, hosts overrides, SPNs, and names resolving to the wrong address.

A file share works by IP address but fails by server name: where is the problem usually located?
Key assessment

Establish a factual baseline with “DNS A/AAAA” and “short names, FQDNs and DNS suffixes”, then move to “hosts file and DNS cache”. Use effective access, credentials and real file operations as the evidence chain and avoid changing production before the fault boundary is clear.

Risk boundaries and prerequisites

Start by checking DNS A/AAAA, short names, FQDNs and DNS suffixes and hosts file and DNS cache independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · DNS A/AAAAChecking DNS A/AAAA helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline.Record the actual state of DNS A/AAAA. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
02 · short names, FQDNs and DNS suffixesChecking short names, FQDNs and DNS suffixes helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline.Record the actual state of short names, FQDNs and DNS suffixes. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
03 · hosts file and DNS cacheChecking hosts file and DNS cache helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline.Record the actual state of hosts file and DNS cache. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
04 · SPN/Kerberos authenticationChecking SPN/Kerberos authentication helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline.Record the actual state of SPN/Kerberos authentication. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
05 · DFS aliases and CNAME recordsChecking DFS aliases and CNAME records helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline.Record the actual state of DFS aliases and CNAME records. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
06 · IPv6 preferenceChecking IPv6 preference helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline.Record the actual state of IPv6 preference. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
Read-only examples
nslookup fileserver.corp.example
ipconfig /displaydns

Investigation and change sequence

  1. Capture a baseline for DNS A/AAAA and short names, FQDNs and DNS suffixes and compare it with a known-good system.
  2. Correlate evidence from hosts file and DNS cache and SPN/Kerberos authentication to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to DFS aliases and CNAME records, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check IPv6 preference and the real business workflow. Confirm the final effective access and application behavior for real file, print or share workflows.

Validation and rollback evidence

  • Confirm the final effective access and application behavior for real file, print or share workflows.
  • Recheck DFS aliases and CNAME records and IPv6 preference against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming DNS A/AAAA is sufficient while overlooking short names, FQDNs and DNS suffixes and dependent checks.
  • Changing several settings before preserving the original evidence for hosts file and DNS cache.
  • An administrator being able to access a file does not prove normal users have the intended rights.

Common questions and acceptance criteria

What should be checked first?

Begin with DNS A/AAAA and short names, FQDNs and DNS suffixes. Capture reproducible errors and protect recoverable data before changing production.

What proves the issue is resolved?

Confirm the final effective access and application behavior for real file, print or share workflows.

What evidence should be retained?

Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.

PreviousAfter a domain password change, sign-in still reports an incorrect password or the old password appears to work: what should be checked?NextA shared folder keeps requesting a username and password even though the password is correct: why is access still denied?

Need an assessment based on your actual environment?