Windows Authentication error

• 
  Hello Eric,
  
  Can you please tell us if it still happens when you log off and on again? I think there could be an issue with ADO .NET Connection Pooling and caching expired credentials. This seems to be an issue in ADO .NET if you're using connection pooling and it's been a long time between SQL Server SSPI logins.

  Brian Donahue August 07, 2006 06:43

  - 0 +
• 
  Brian,
  
  Still happens. I tried the 'Clear Cache' and 'Close All Current Connections' and I still get prompted. And it's right at the initial connection point. I can reboot the box, start the MSSQL service, start Management Studio, type 'ssf<tab>', get the login box, and blammo, nothing.
  
  Are there any system settings I can check?
  
  Thanks for all your help.
  
  Eric

  Mags August 07, 2006 09:24

  - 0 +
• 
  Hi Eric
  
  You need to specify the server name and the instance name. I have tried Local (local) and that didnt work but when I specified the servername\instance name it was all fine.
  
  Let me know if that works.
  
  Thanks
  
  Glen

  GlenC August 14, 2006 07:01

  - 0 +
• 
  Glen,
  
  So what would I put for the instance name when I'm using the default instance on localhost? I did not install a named instance on my machine.
  
  Eric

  Mags August 14, 2006 11:58

  - 0 +
• 
  I believe it would be the servername\local
  
  Failing that I am all out of ideas.......
  
  Thanks
  
  Glen

  GlenC August 15, 2006 03:04

  - 0 +
• 
  It was a firewall issue that was causing my authentication issues. Once I shut down the firewall (have to figure that part out next) everything worked fine.
  
  Thanks for your help.
  
  Eric

  Mags August 17, 2006 09:42

  - 0 +

Add comment

Please sign in to leave a comment.