Re: Windows XP Professional/SQL Server 2000 (SP3a) - General Netwo

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: C Kim (CKim_at_discussions.microsoft.com)
Date: 09/02/04 

Date: Thu, 2 Sep 2004 07:35:09 -0700

Thanks a lot for the information. My responses are below - any further help
is greatly appreciated:

What are the server protocols enabled?
Named pipes, TCP/IP

If you are using TCP/IP, please note the port number that this protocol
binds to on the Server Net Utility. I would further check the SQL errorlog
to see if we are successfully binding to that port. If there is a failure
to bind to this port, then some other process is locking that port.
There are issues in binding in the log <2004-09-01 15:45:54.90 server
SuperSocket Info: Bind failed on TCP port 1433.> I can't seem to find what
other process is taking this port. I also tried using port 1133 (something
other than the default 1433) to see if that would work but it too failed.

 Check if there are any aliases defined in the Client Network Utility. If
there are any aliases defined, check the properties to see what protocol is
configured. If there are more than one aliases defined, please remove all
others except for one. If you need to check this from client machine and
you do not have SQL client tools group under Start->Programs, then use
CLICONFG.EXE
I had tried earlieron to create an alias to see if that would help but it
didn't. Currently there are no aliases.

Check to see what protocols are enabled on the Client Network Utility.
Check the properties for TCP/IP protocol if that is the one that you are
using to connect.
Named pipes and TCP/IP are enabled. I checked the properties for TCP/IP and
it matched up with the server fine. I can use Query Analyzer and Enterprise
Manager fine on my local SQL Server. It really is an issue though when it
comes to using the Microsoft JDBC SQL Server driver that uses TCP/IP which is
what seems to have the problem.

Check to see if Enabled Shared Memory Protocol is checked. If not, please
check this protocol.
This had already been checked off.

Regards,
C Kim

Relevant Pages

  • Re: "Opening ports"
    ... When filtering log on port 5656, ... Create Protocol: ... Understanding the ISA 2004 Access Rule Processing ... Microsoft Internet Security & Acceleration Server: ...
    (microsoft.public.isa)
  • Re: SBS2003, Terminal server and Mobile 6
    ... RRAS as Firewall) and SBS 2K3 Premium: ... in order for a custom protocol to be considered a "Server" ... In the ''Policy Elements'' branch of ISA server mmc, ... Next...Enter the destination port number for the custom protocol being ...
    (microsoft.public.windows.server.sbs)
  • Re: not what Im after
    ... Users A, B, and C have to be listening to a port to get a message over that ... proxy server between then, then the proxy server actually "owns" the IP ... Will you be using an established protocol or are you writing your own? ... "Advanced .NET Remoting" by Ingo Rammer. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Remote access from Internet
    ... An initial proposal was to implement the entire user interface as a Java applet and use a simple back-end protocol to move data. ... The user who desires access connects to relay server with a browser and logs in. ... then you probably need to block all ports *except* for one that you actively manage - ideally by something strong like SSH. ... As a side note on ssh security, there is no need to put ssh on port 22. ...
    (comp.arch.embedded)
  • RE: Port Forwarding
    ... RRAS as Firewall) and SBS 2K3 Premium: ... in order for a custom protocol to be considered a "Server" ... In the ''Policy Elements'' branch of ISA server mmc, ... For example, for Terminal Server, the port number would be 3389. ...
    (microsoft.public.windows.server.sbs)