Timeline for SQL Server 2008 server cannot connect to itself with alias name or "localhost"
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2014 at 18:47 | history | post merged (destination) | |||
| Jan 30, 2014 at 18:35 | comment | added | Emo | No I'm on the active node. Double checked that. | |
| Jan 30, 2014 at 18:33 | comment | added | Emo | Sorry to cross post. Wasn't aware that was an issue. You can remove from Serverfault and leave on dbastackexchange | |
| Jan 30, 2014 at 18:29 | review | Close votes | |||
| Feb 3, 2014 at 19:38 | |||||
| Jan 30, 2014 at 18:13 | history | migrated | from serverfault.com (revisions) | ||
| Jan 30, 2014 at 18:09 | comment | added | Cougar9000 | Are you trying to connect with localhost from the passive node? | |
| Jan 30, 2014 at 17:21 | comment | added | Emo | Default. Sorry forgot to add that in. And connecting as localhost isn't that important, I bring it up for possible trouble shooting...and the fact that it denotes something is wrong. | |
| Jan 30, 2014 at 16:18 | comment | added | Aaron Bertrand | Is it a default instance or a named instance? How important is it that you can connect via "localhost" when using the proper name works? | |
| Jan 30, 2014 at 16:08 | answer | added | pithhelmet | timeline score: 3 | |
| Jan 30, 2014 at 15:52 | history | asked | Emo | CC BY-SA 3.0 |