|
|
Posted by Erland Sommarskog on 01/19/06 10:30
Oscar Santiesteban Jr. (o_santiesteban@bellsouth.net) writes:
> Thanks Erland for the comments. Here is some follow up.
> The "Audit Logoff" seems to come from the client. We have monitored all
> connections using ETHERReal and the logoff comes from the IP address.
I don't know how you conclude this, but at least in Profiler you will
not be able to tell who disconnected whom.
Anyway, in another post you said that the database is Access which is
using linked tables. Do each user have it's own Access database? Or do
they connect to a central Access database which then connects to SQL
Server?
Not that it may matter that much. I know very little about Access, but
my guess is that when Access access SQL Server it's still done in the
context of the user.
What you should try is to set up Access with linked tables to some
other server where you don't have this problem. First verify that
connection pooling works, that is you don't see constant logoffs. Then
sever the connection like pulling out the network cable and put it
back again or similar. If Access handles this gracefully, that is you
don't get an error message, then there is more reason to suspect that
you have a network problem.
After all, since what appears to have changed at your site is the
configuration of server and network, so it's natural to look for
the cause there.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|