This is not a name resolution problem. You can see the resources if you use the name but not when you use the IP.
IP SMB file share access will fail to use Kerberos. A network trace will yield the following error in the KRB_ERROR with Kerberos error "Server not found in Kerberos database". By default, will attempt to use Kerberos as its ideal security provider. When using Kerberos to authenticate itself to a server, the client requests a session ticket for the Service Principal Name. IP addresses are not names, then we fail to use Kerberos. After failure occurs the server will
proceed down the list of supported security providers.
IP addresses typically change and it isn't feasible to add these addresses as SPNs. A service principal name can be one of the following; DNS name for the domain, the DNS name of a host, or the distinguished name of a service connection point
object. Consider the "name" element in Service Principal Name. This behavior is by design.
Main Topics
Browse All Topics





by: lnkevinPosted on 2007-01-18 at 13:20:31ID: 18344942
You can try the following steps:
1. Stop NetLogon service.
2. Open DNS Console > Delete Active directory integrated zone.
3. Stop and start DNS Service.
4. Close and Reopen DNS Console > Re-create zone.
5. Finally Start Netlogon service.
The above procedure will re-register all DC SRVs in DNS Zone.
K