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.

1. Conclusion and scope

Prepare the client and server versions, domain membership, DNS and gateway settings, network location, full error text, event timestamps, and recent changes. The reserved example domain corp.example is used throughout; no customer domain, IP address, account, or device identifier is included.

This issue falls under Windows Server and file permissions. Logs and configuration can often be collected remotely first. Bulk permission changes, switch-path work, production cutovers, and recovery drills should use a controlled implementation window.

2. Symptoms and environment

• Capture the complete error text, event-log timestamp, and failed action rather than relying on a verbal description.
• Record the affected scope, first occurrence, reproducibility, and whether the result changes on another subnet.
• Use Effective Access to evaluate the permissions inherited through group membership, ACL inheritance, and explicit deny entries.

3. Troubleshooting sequence

1. Confirm the connection-specific DNS suffix and suffix search list. When a short name fails, compare it with the full FQDN.
2. Verify A, AAAA, and PTR records point to the current address. Before removing duplicates or stale records, confirm DHCP and dynamic-update ownership.
3. Check hosts, LMHOSTS, proxy PAC files, and the local DNS cache for stale overrides; do not let a temporary bypass conceal the DNS root cause.
4. Domain members and computers being joined must use internal DNS; public resolvers do not provide the AD SRV records required for discovery.
5. Check name resolution, DNS suffixes, SMB connectivity, the server firewall, and the exact share name; a successful ping does not prove SMB access.
6. Change one variable at a time and export the current configuration before making changes.

nslookup filesrv.corp.example
Resolve-DnsName filesrv.corp.example
ipconfig /displaydns
klist get cifs/filesrv.corp.example

4. Safe remediation and rollout

Start with read-only queries, configuration exports, and one-system validation. Once the root cause is confirmed, define the target scope, change window, and rollback method. In an enterprise environment, migrate per-user permissions to department, role, and project security groups while retaining an access matrix, approvals, and rollback scripts.

• Domain members and computers being joined must use internal DNS; public resolvers do not provide the AD SRV records required for discovery.
• Check name resolution, DNS suffixes, SMB connectivity, the server firewall, and the exact share name; a successful ping does not prove SMB access.
• Change one variable at a time and export the current configuration before making changes.

5. Validation, rollback and common mistakes

Do not stop when the service works once. Revalidate with the user workflow, logs, a restart or fresh sign-in, another network location where relevant, and the next policy or backup cycle.

Validation and rollback checks

• Change one variable at a time and export the current configuration before making changes.
• To trace deletions and changes, configure object-access auditing, an appropriate SACL, sufficient log capacity, and central retention.
• Remove incorrect cached credentials and stale SMB sessions, then confirm that the client is using the intended domain or local account.

Common mistakes to avoid

• Granting Everyone Full Control as a quick workaround.
• Changing share permissions while ignoring NTFS ACLs and inheritance.
• Resetting ACLs recursively without an export and a pilot folder.