Timeline for Cannot connect to linked server using name in hosts file
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2022 at 17:25 | comment | added | ktakmn | Ok it is possible I am starting to get my head around it. I tested putting an A record into our DNS and it does indeed give the same error as when I put a record in the hosts file: login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. However, I do have an A record which works in the DNS with linked servers. That A record has the same name as the server name - presumably that it why it works with Kerberos, whereas A records with names different to the server name do not work? Thank you again. | |
| Aug 2, 2022 at 17:35 | comment | added | David Browne - Microsoft | Because a hosts file entry is more like an DNS A-record. | |
| Aug 2, 2022 at 17:29 | vote | accept | ktakmn | ||
| Aug 2, 2022 at 17:22 | comment | added | ktakmn | Thank you for this. After great pain with OleDb providers I have got this working using your example. Sorry if I am being slow, but I still do not quite understand what the difference is between creating an CNAME record in the domain's DNS and putting a record in the hosts file on the database server where the linked server is created. The former works and the latter does not... using the same server alias. | |
| Aug 1, 2022 at 23:17 | history | answered | David Browne - Microsoft | CC BY-SA 4.0 |