Re: SQL Server and SP2

• Previous message: Mike Epprecht \(SQL MVP\): "Re: SQL Server and SP2"
• In reply to: Mike Epprecht \(SQL MVP\): "Re: SQL Server and SP2"
• Next in thread: Jon Jahren: "Re: SQL Server and SP2"
• Messages sorted by: [ date ] [ thread ]

Date: Wed, 17 Nov 2004 16:55:01 -0800

I have already done this. Under "Enabled Protocols" is both Named Pipes and
TCP/IP set for port 1433. Still no luck.

I beginning to think that there must be something about my machine and the
way it is set up. I have spoken with others who have sucessfully gotten sql
server to listen on a tcp connection after having installed sp2. I've got a 2
year old Dell P4 with 2.6 gig processor and 256meg ram. I have Visual Studio
.NET installed and have developed apps in the past that used ADO.NET using
tcp as the proptocol to my sql server instance. But it seems that no matter
what I try, I cannot get Windows to open up port 1433. The firewall did open
udp 445 after I asked it too, but not 1433. Even turning off the damn fire
wall did not solve the problem.

"Mike Epprecht (SQL MVP)" wrote:

> Run "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\svrnetcn.exe"
>
> It is the Server Network Utility and in there you configure which protocols
> SQL Server works on.
>
> Cheers
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program: http://www.microsoft.com/mvp
>
> Blog: http://www.msmvps.com/epprecht/
>
> "Z" <Z@webcast.net> wrote in message
> news:06BBF5BF-6CD9-4351-BE9D-0A410BDF230F@microsoft.com...
> > Thank you, Jon, for replying. I did open UDP port 1434 as per your
> > suggestion, but it was not helpful. I also opened tcp port 445 as
> discussed
> > in the knowledge base article at http://support.microsoft.com/?id=836269.
> I
> > know sql server is not listening for tcp connections because the sql log
> file
> > does not report it. It reports only that it's listening on shared memory
> and
> > named pipes.
> >
> > I'm still stuck.
> >
> > "Jon Jahren" wrote:
> >
> > > I understand your frustration. You've probably already done this, but
> just
> > > in case:
> > > - Have you opened UDP port 1434 as well as TCP port 1433? If no, try it.
> > > - Are you absolutely sure your client is using TCP/IP netlib to connect
> to
> > > SQL Server? If both TCP/IP and Named Pipes are enabled both on the
> client
> > > and server, you might see that Named Pipes is the one chosen in certain
> > > OS/SQL/Network configurations. In this case, you need to open port 445
> in
> > > you firewall as well. Even better, specify in your connection string
> that
> > > you only want TCP/IP, for example by prefixing your server name with the
> > > netlib hint : "tcp:myserver".
> > >
> > > Jon Jahren
> > >
> > > "Z" <Z@webcast.net> wrote in message
> > > news:99E0049E-EC70-4ADA-99FB-B033C242A676@microsoft.com...
> > > > Hi all. I join those who have installed sp2 and have lost the ability
> to
> > > > communicate with sql server over port 1433. I have read all of the
> posts
> > > at
> > > > this forum and have tried all of the fixes recommended. Microsoft's
> > > > publication (841521) about running firewall.cpl and allowing sql
> server to
> > > > run just does not work. The registry reports that sql server is
> listening
> > > on
> > > > port 1433 as the static port for my named instance of sql server. The
> > > server
> > > > network utility and client network utility both show tcpip is enabled
> and
> > > set
> > > > for port 1433. I have applied sp3a to sql server and have run the
> > > > SQLCritUpdPkg_ENU.exe program that Robert Buscemi reports worked for
> him
> > > (see
> > > > post 6/19 below with 17 responses).
> > > >
> > > > This is terribly frustrating and a real bone-headed move on MS's part.
> How
> > > > can they ship an "upgrade" that disables their own database server,
> and
> > > then
> > > > come out with lame responses about running firewall.cpl as if that
> will
> > > > magically fix it? They should spend more time on serious, critical
> issues
> > > > such as this instead of the stupid dancing paper clip. And I have to
> > > teach
> > > > this stuff!
> > > >
> > > > I would very much like an answer to this problem that just works. No
> lies,
> > > > no false directions, just the plain truth about a plan of action that
> is
> > > > guaranteed to work.
> > >
> > >
> > >
>
>
>

• Previous message: Mike Epprecht \(SQL MVP\): "Re: SQL Server and SP2"
• In reply to: Mike Epprecht \(SQL MVP\): "Re: SQL Server and SP2"
• Next in thread: Jon Jahren: "Re: SQL Server and SP2"
• Messages sorted by: [ date ] [ thread ]