May 23, 2006 at 7:25 pm
Hello All,
We currently have a set of SQL Admins who use SQL Ent Manager to connect to two of our SQL Servers. There are three sets of users - Application develepers, DBA's and Security Admin. The DBA's and developers can connect to these servers using TCP/IP without any problems. However the Security Admin folk cannot connect unless they use NamedPipes. This was alright until we put a mandate in place to disable Namepipes now the the Sec Admin people cannot connect.
The error message is vague and all the searching I have done on the internet does not help me.
At the Client
SQLState: '01000' SQL Server Error: 10054 TCP/IP Sockets ConnectionRead (recv())
Connection Failed:
SQLState: '08S01'
SQL Server Error: 11
General network error
At the server
Error: 17805, Severity: 20, State: 2
Invalid buffer received from client..
The problem only occurs when using Windows Authentication and to make it more confusing, if a DBA logs onto the Sec Admin PC with their own account and tries to connect to ther SQL server with their own ID there is no problem at all. This indicates it is not a SQL Ent Manager problem on the PC, not a connectivity issue (named pipes works) and is probably related to the specific user account.
Has anyone seen this error message before or these symptoms?
Thanks and Regards
May 23, 2006 at 10:30 pm
Further to my Post - Could it be a result of the users being a member of too many AD Global groups??? The Sec Admin users have considerably more group memberships that other users who connect to the same SQL servers?
May 23, 2006 at 11:04 pm
I have found the solution and it all has to due with the MaxtTokenSize registry key. Please read the MS Article http://support.microsoft.com/?kbid=327825.
There are a few other posts here that have the same problem.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply