Connect to database established, then dropped

Question

Hello,

We are running SQLServer 2008r2 on a windows 2008r2,sp1 server. Some (not all) users are having connectivity issues from their client workstations.

For the user I am testing with (using his ID) here are the facts:

If I remote into the DB server as the user, I can bring up the database and access data just fine. This leads me to cross off sql server security.

If I try SSMS from my laptop, I get Error 10054 - existing connection (I got in) forcibly closed by the host. The dev server connects, prod does not. I have compared everything I know of and all parms match.

I loaded his application client onto my laptop. When I try to connect through the application, his ID gets a general network error. My ID accesses the application just fine. He has a userid in another domain, it accesses the application just fine. The event viewer shows this: The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library. [CLIENT: ***.***.***.***]  when he tried to connect through his fat client to prod.

---

Dianne

Answer 1

You refer to "Domain", so I am assuming you are using trusted connections. Since you are using trusted security, the Authentication and Authorization are being preformed by the Active Directory server (or whatever LDAP Server you are using), nor SQL server. 

1) Since these accounts exist in different domains, I would verify the the trust relationship between the domains, i.e. user, computer, SQL server user accounts are configured correctly. For example a user in one domain may have a more complex security token then another user and I have seen this problem  before ( MSSQLSERVER 17832 )

2)  Are the versions of AD the same and compatible? The security being provided by one AD server may not be compatible with the other. 

3) It is possible the account information is corrupted, assuming there are no dependence, you may want to have the user account dropped and recreated. 

4) If the AD configuration is ruled out, Verify that you are using the SQL 2008R2 native client drivers and not an older SQL client that may not support some feature associated with the other account.

---

William F. Kinsley

Answer 2

Hello,

Just a little add-in to the post of WFKinsley.

You should have a look at these links :

http://blogs.msdn.com/b/ialonso/archive/2008/02/19/a-tale-about-solving-cannot-generate-sspi-context-followed-by-the-resolution-of-dbnetlib-connectionread-recv-general-network-error-check-your-network-documentation.aspx

http://blogs.msdn.com/b/sql_protocols/archive/2008/04/08/understanding-connection-forcibly-closed-by-remote-host-errors-caused-by-toe-chimney.aspx

This blog ( which is the official blog of the Microsoft team who is developping the protocols for SQL Server ) is one of the best source for informations about connectivity problems

A last link  ( even if it is related to SQL Server 2000 ) :

http://msgroups.net/microsoft.public.sqlserver.server/Linked-server-sql2k8-x64-sql7 

Please, could you give more informations about ?

- the operating system of the client workstations and your laptop ( full edition and last installed service pack )

- the network protocol used by the application ( and the connection string )

We are waiting for your feedback to try to help you more efficiently.

Have a nice day

---

Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

Answer 3

Actually this did indeed have to do with the actual user.  The issue was the MaxTokenSize spoken of here:

http://decipherinfosys.wordpress.com/2008/08/27/maxtokensize-and-windows-authentication/

Thanks for helping,

Dianne

---

Dianne