Hi Greg K, I see you can only use sa. If you make a new sql login user on the SQL Server and give it sysadmin does it see the databases just like sa?
Greg Greg Wood g...@woodgreg.com 0417044439 On Thu, Mar 24, 2011 at 1:58 PM, Greg Keogh <g...@mira.net> wrote: > Hi Greg L and others, > > > > I’ve spent many hours over the last couple of days trying to get SQL Server > 2008 R2 Windows Authentication working over the LAN, with absolutely no > success. I’m not experienced in this area, but I’ve tried every sensible > trick I can think and nothing makes any difference. The worst thing is that > I don’t know who to blame: the domain, SQL Server, user/group settings, > what? > > > > I have now found that just one of the thirteen databases CAN be accessed and > twelve can’t. I tried carefully comparing the attributes of a working and > non-working DB, but the one that works comes from outside my office and is a > mess, making it a useless apples and oranges comparison. > > > > Grant: I don’t see any strange schemas that are candidates for deletion. > > > > My only workaround for now is to use ‘sa’ in all connection strings. > > > > Greg K