sql server connect: Could not close net-library -- sql server connect

RE: Could not close net-library

anonymous NO[at]SPAM discussions.microsoft.com
5/27/2004 7:10:01 AM

Hi Kevin, the service that are running on the server are
those:

Alerter
Automatic updates
Backupexec 8.x Agent, alert, device, job engine, naming
service, notification server and server
Com+ event system
Computer browser
DHCP Client
DFS
Distributed link tracking client
Distributed transcaction coordinator
DNS Client
Event log
FTP publishing service
IIS Admin
IPSEC Pol. agent
License logging service
Logical disk manager
Messenger
Microsoft search
MSSQL Server
Network connection
NOD32 Kernel service (anti virus)
NTLM security support provider
NVDIAL driver helper service
Plug and play
spooler
Protected storage
Remote access connection manager
RPC
Remote registry service
Removable storage
Runas service
security account manager
server
SMTP
SQL SERVER AGENT
system event notification
task scheduler
TCPIP Netbios helper
telephony
terminal service
terminal service licensing
Windows management instrumentation & driver
workstation
WWW

It's working for 1 or 2 days and after, client cannot
connect anymore on the server. the message saying that
SQL Server does not exist or access denied. If I stop and
restard MSSQL Service, it work again. Also, when sql
server start, i get the message:

19012 :
SuperSocket Info: Bind failed on TCP port 1433.

I can telnet to port 1433 and it connect. The things is I
don't see any other apps that can use that port.

Thanks for your help!

[quoted text, click to view]

RE: Could not close net-library

kevmc NO[at]SPAM online.microsoft.com
5/27/2004 5:54:47 PM

Hi Gabriel,
Those services look pretty standard. I've seen issues with customers
running PortMapper software for web servers.

Is this a SQL Server Clustered Server or Standalone?
Are the clients local clients or are they connecting from a Wide Area
Network?

You may want to run PortQry on the machine to verify that another
application isn't using 1433 or
run netstat -a

310099 Description of the Portqry.exe Command-Line Utility
http://support.microsoft.com/?id=310099

Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.

RE: Could not close net-library

anonymous NO[at]SPAM discussions.microsoft.com
5/28/2004 8:07:46 AM

Hello Kevin, the Sql server is stand alone and the clients
are connecting on the sql server via terminal server.
I tried to run PORTQRY and it respond with the ms-sql-
server-s port on 1433. I also check in enterprise manager
and the clients are connected trought tcp/ip.

I don't know what else should I check...

[quoted text, click to view]

RE: Could not close net-library

kevmc NO[at]SPAM online.microsoft.com
6/1/2004 7:15:07 PM

OK. So, tell me about the applications that are connecting to SQL Server.
Are they ODBC or DbLibrary ?

Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.

RE: Could not close net-library

SqlJunkies User
11/15/2004 5:48:44 AM

Try disabling NOD32, that may be the source of the bind error when you restart. Have had similar issue ourselves. See this discussion also, someone having similar problems:

http://www.wilderssecurity.com/showthread.php?t=11426

---
Posted using Wimdows.net NntpNews Component -

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server connect group.