126 reputation
16
bio website noiregrets.com
location Sydney, Australia
age 28
visits member for 4 years, 2 months
seen Oct 21 '12 at 22:15

Software Engineer for Awesome


Sep
21
awarded  Notable Question
Oct
14
awarded  Popular Question
Mar
14
awarded  Critic
Feb
2
awarded  Student
Feb
2
revised Why don't ports resolve correctly for localhost and {my server name}?
added 76 characters in body
Feb
2
asked Why don't ports resolve correctly for localhost and {my server name}?
Feb
1
revised SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
added 4 characters in body
Feb
1
awarded  Commentator
Feb
1
comment SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
No luck. Good idea though.
Feb
1
comment SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
Ah you mean disabling? I'll give it a try...
Feb
1
comment SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
It's already enabled.
Feb
1
revised SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
added 200 characters in body
Feb
1
comment SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
I've already tried most of that as I listed above. I also checked that I was allowing remote connections (shouldn't matter anyway) but I already was. Remember, the problem is specifically that connecting to "localhost" fails, but connecting to "127.0.0.1" and "::1" both work.
Feb
1
comment SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
The error was along the lines of "A network-related or instance-specific error has occurred. The server was not found or not accessible". Anyway, I shouldn't have to use the name of the instance. I want my connection string to match between my local environment and my production environment. In other words, I want them both to point to simply "localhost". I think you guys are kind of missing the point anyway. using "127.0.0.1" works, but "localhost" doesn't. So the problem has to be something other than naming the instance. It's gotta be something related to the binding of "localhost".
Jan
31
revised SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
added 5112 characters in body
Jan
31
revised SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
added 1 characters in body
Jan
31
comment SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
Ah just lingering. They're gone now.
Jan
31
awarded  Editor
Jan
31
comment SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
I thought the connection from the 5XXXX ports were my SSMS connections using 127.0.0.1, but I closed SSMS and still see those. My Web Server isn't running AFAIK.
Jan
31
revised SQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1
added 1122 characters in body; added 13 characters in body; added 1 characters in body