Connect to SQL Server Remotely but not Locally

  • Thread starter Thread starter DragonslayerApps
  • Start date Start date
D

DragonslayerApps

I'm so stumped by this one that I don't even know where to begin
looking.

I have recently created two ASP.Net 2.0 web applications. They work
together with a SQL Server 2000 database. IIS & SQL Server reside on
the same machine.

They have both been working nicely all through the development process
on both the development machine and the production server. Suddenly
today I have a strange problem which has cropped up in both of them. If
I run the sites using Visual Studio development server (which makes
remote calls over the internet to the database), they work normally.
However, when run from the production server and making local calls to
the same database, they fail with the following error:

"An operation on a socket could not be performed because the system
lacked sufficient buffer space or because a queue was full."

This happens both on one site that I have modified today, and another
one which I have not modified in two days. They applications use the
same connection string in both locations. I can connect to the database
using Query Analyzer both remotely and locally.

I have restarted the web service. I have re-copied the files. I have
stopped and restarted the websites. I have assigned them to a different
application pool. I have restarted SQL Server. I have rebooted the
physical server. The error will not go away.

Any guesses or next steps to diagnosis?

John Stevens
Dragonslayer Applications
MCAD, MCP
 
Modifying previous post: Rebooting the server did resolve the problem,
at least temporarily. Perhaps there is a memory leak of some kind. I
would still appreciate input on why there would be a problem when
connecting locally but not remotely.
 
Back
Top