"Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> wrote in message
news:53642094-FE1C-4BFB-85BF-E114587DDB0F@microsoft.com...
> It looks like your SQL Server is listening on shared memory (which is a
> local pipe) and named pipes, but is not listening on TCP/IP. So if you
want
> to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
> restart SQL Server. You use the Server Network Utility for that.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Safeer" <safeerm@gmail.com> wrote in message
> news:uCxeUt5VHHA.868@TK2MSFTNGP05.phx.gbl...
> > Hi,
> >
> > Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
> > SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard
Edition
> >
> > My workstation is Windows 2000. I am connecting to the server using
MSTSC.
> >
> > My sql server log shows the following.
> > "SQL server listening on Shared Memory, Named Pipes."
> >
> > Actually TCP/IP/1433 is enabled in the server.
> > & I am not able to telnet the machine with port 1433 from the server
> > itself.
> >
> > NB: No one is using this machine now and I need to setup and install
> > service
> > packs. Its a new box with installed SQL 2K and nobody know the SA
> > password.
> >
> > Thanks...Safeer
> >
> >
> > "Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> wrote in
message
> > news:08EB12C9-D906-4977-A40E-0F050C837E1E@microsoft.com...
> >> We need more info.
> >> - What version and edition of SQL Server are you using?
> >> - What version of the Windows are you using?
> >> It sounds like you are connecting from a client on another computer. If
> > you
> >> are using SQL Server 2005, use the Surface Area Configuration tool to
> >> confirm that your SQL Server instance is listening for remote
> >> connections.
> >> Also, a firewall could be blocking 1433. This is common with Windows XP
> >> service pack 2.
> >> If SQL Server is running on Vista, you have other issues.
> >> For SQL Server 2005, there is a short tutorial that will help. See
> >> http://msdn2.microsoft.com/en-us/library/ms345318.aspx
> >> --
> >> Rick Byham (MSFT)
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >> "Safeer" <safeerm@gmail.com> wrote in message
> >> news:eu1sb1rVHHA.1016@TK2MSFTNGP04.phx.gbl...
> >> >I tried telnet ipaddress 1433, its not connecting thru the port.
> >> >
> >> > I am connected to the server directly and then checked the port using
> >> > server
> >> > utility and its 1433.
> >> >
> >> >
> >> > "Safeer" <safeerm@gmail.com> wrote in message
> >> > news:e1jmNjrVHHA.4028@TK2MSFTNGP04.phx.gbl...
> >> >> I am having administrative previlages in the SQL Server Machine, but
I
> > am
> >> >> not able to connect to the SQL Server instance. Can you please help.
I
> > am
> >> >> using windows authendication.
> >> >>
> >> >> Thanks...Safeer
> >> >>
> >> >>
> >> >
> >> >
> >>
> >
> >
>

"Safeer" <safeerm@gmail.com> wrote in message
news:e%23n1O5eWHHA.4668@TK2MSFTNGP04.phx.gbl...
> Hi Rick,
>
> I've already did that. Now I did it again and restarted the server. In the
> Server Netwrok Utility, its showing tcp/ip. But the log is not showing
> TCP/IP.
>
> Thanks...Safeer
>
>
>
> "Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:53642094-FE1C-4BFB-85BF-E114587DDB0F@microsoft.com...
>> It looks like your SQL Server is listening on shared memory (which is a
>> local pipe) and named pipes, but is not listening on TCP/IP. So if you
> want
>> to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
>> restart SQL Server. You use the Server Network Utility for that.
>> --
>> Rick Byham (MSFT)
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "Safeer" <safeerm@gmail.com> wrote in message
>> news:uCxeUt5VHHA.868@TK2MSFTNGP05.phx.gbl...
>> > Hi,
>> >
>> > Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
>> > SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard
> Edition
>> >
>> > My workstation is Windows 2000. I am connecting to the server using
> MSTSC.
>> >
>> > My sql server log shows the following.
>> > "SQL server listening on Shared Memory, Named Pipes."
>> >
>> > Actually TCP/IP/1433 is enabled in the server.
>> > & I am not able to telnet the machine with port 1433 from the server
>> > itself.
>> >
>> > NB: No one is using this machine now and I need to setup and install
>> > service
>> > packs. Its a new box with installed SQL 2K and nobody know the SA
>> > password.
>> >
>> > Thanks...Safeer
>> >
>> >
>> > "Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> wrote in
> message
>> > news:08EB12C9-D906-4977-A40E-0F050C837E1E@microsoft.com...
>> >> We need more info.
>> >> - What version and edition of SQL Server are you using?
>> >> - What version of the Windows are you using?
>> >> It sounds like you are connecting from a client on another computer.
>> >> If
>> > you
>> >> are using SQL Server 2005, use the Surface Area Configuration tool to
>> >> confirm that your SQL Server instance is listening for remote
>> >> connections.
>> >> Also, a firewall could be blocking 1433. This is common with Windows
>> >> XP
>> >> service pack 2.
>> >> If SQL Server is running on Vista, you have other issues.
>> >> For SQL Server 2005, there is a short tutorial that will help. See
>> >> http://msdn2.microsoft.com/en-us/library/ms345318.aspx
>> >> --
>> >> Rick Byham (MSFT)
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >>
>> >> "Safeer" <safeerm@gmail.com> wrote in message
>> >> news:eu1sb1rVHHA.1016@TK2MSFTNGP04.phx.gbl...
>> >> >I tried telnet ipaddress 1433, its not connecting thru the port.
>> >> >
>> >> > I am connected to the server directly and then checked the port
>> >> > using
>> >> > server
>> >> > utility and its 1433.
>> >> >
>> >> >
>> >> > "Safeer" <safeerm@gmail.com> wrote in message
>> >> > news:e1jmNjrVHHA.4028@TK2MSFTNGP04.phx.gbl...
>> >> >> I am having administrative previlages in the SQL Server Machine,
>> >> >> but
> I
>> > am
>> >> >> not able to connect to the SQL Server instance. Can you please
>> >> >> help.
> I
>> > am
>> >> >> using windows authendication.
>> >> >>
>> >> >> Thanks...Safeer
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >
>> >
>>
>
>

"William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
news:uPPE4YgWHHA.4384@TK2MSFTNGP02.phx.gbl...
> Is the SQL Server Browser service started?
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> --------------------------------------------------------------------------
---------------------------------------------
>
> "Safeer" <safeerm@gmail.com> wrote in message
> news:e%23n1O5eWHHA.4668@TK2MSFTNGP04.phx.gbl...
> > Hi Rick,
> >
> > I've already did that. Now I did it again and restarted the server. In
the
> > Server Netwrok Utility, its showing tcp/ip. But the log is not showing
> > TCP/IP.
> >
> > Thanks...Safeer
> >
> >
> >
> > "Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> wrote in
message
> > news:53642094-FE1C-4BFB-85BF-E114587DDB0F@microsoft.com...
> >> It looks like your SQL Server is listening on shared memory (which is a
> >> local pipe) and named pipes, but is not listening on TCP/IP. So if you
> > want
> >> to connect using TCP/IP and port 1433, you will have to enable TCP/IP
and
> >> restart SQL Server. You use the Server Network Utility for that.
> >> --
> >> Rick Byham (MSFT)
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >> "Safeer" <safeerm@gmail.com> wrote in message
> >> news:uCxeUt5VHHA.868@TK2MSFTNGP05.phx.gbl...
> >> > Hi,
> >> >
> >> > Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
> >> > SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard
> > Edition
> >> >
> >> > My workstation is Windows 2000. I am connecting to the server using
> > MSTSC.
> >> >
> >> > My sql server log shows the following.
> >> > "SQL server listening on Shared Memory, Named Pipes."
> >> >
> >> > Actually TCP/IP/1433 is enabled in the server.
> >> > & I am not able to telnet the machine with port 1433 from the server
> >> > itself.
> >> >
> >> > NB: No one is using this machine now and I need to setup and install
> >> > service
> >> > packs. Its a new box with installed SQL 2K and nobody know the SA
> >> > password.
> >> >
> >> > Thanks...Safeer
> >> >
> >> >
> >> > "Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> wrote in
> > message
> >> > news:08EB12C9-D906-4977-A40E-0F050C837E1E@microsoft.com...
> >> >> We need more info.
> >> >> - What version and edition of SQL Server are you using?
> >> >> - What version of the Windows are you using?
> >> >> It sounds like you are connecting from a client on another computer.
> >> >> If
> >> > you
> >> >> are using SQL Server 2005, use the Surface Area Configuration tool
to
> >> >> confirm that your SQL Server instance is listening for remote
> >> >> connections.
> >> >> Also, a firewall could be blocking 1433. This is common with Windows
> >> >> XP
> >> >> service pack 2.
> >> >> If SQL Server is running on Vista, you have other issues.
> >> >> For SQL Server 2005, there is a short tutorial that will help. See
> >> >> http://msdn2.microsoft.com/en-us/library/ms345318.aspx
> >> >> --
> >> >> Rick Byham (MSFT)
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> > rights.
> >> >>
> >> >> "Safeer" <safeerm@gmail.com> wrote in message
> >> >> news:eu1sb1rVHHA.1016@TK2MSFTNGP04.phx.gbl...
> >> >> >I tried telnet ipaddress 1433, its not connecting thru the port.
> >> >> >
> >> >> > I am connected to the server directly and then checked the port
> >> >> > using
> >> >> > server
> >> >> > utility and its 1433.
> >> >> >
> >> >> >
> >> >> > "Safeer" <safeerm@gmail.com> wrote in message
> >> >> > news:e1jmNjrVHHA.4028@TK2MSFTNGP04.phx.gbl...
> >> >> >> I am having administrative previlages in the SQL Server Machine,
> >> >> >> but
> > I
> >> > am
> >> >> >> not able to connect to the SQL Server instance. Can you please
> >> >> >> help.
> > I
> >> > am
> >> >> >> using windows authendication.
> >> >> >>
> >> >> >> Thanks...Safeer
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
> >
>
>

"Safeer" <safeerm@gmail.com> wrote in message
news:eR6kqFsWHHA.3332@TK2MSFTNGP04.phx.gbl...
> Its SQL Server 2000.
>
>
> "William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
> news:uPPE4YgWHHA.4384@TK2MSFTNGP02.phx.gbl...
>> Is the SQL Server Browser service started?
>>
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> --------------------------------------------------------------------------
> ---------------------------------------------
>>
>> "Safeer" <safeerm@gmail.com> wrote in message
>> news:e%23n1O5eWHHA.4668@TK2MSFTNGP04.phx.gbl...
>> > Hi Rick,
>> >
>> > I've already did that. Now I did it again and restarted the server. In
> the
>> > Server Netwrok Utility, its showing tcp/ip. But the log is not showing
>> > TCP/IP.
>> >
>> > Thanks...Safeer
>> >
>> >
>> >
>> > "Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> wrote in
> message
>> > news:53642094-FE1C-4BFB-85BF-E114587DDB0F@microsoft.com...
>> >> It looks like your SQL Server is listening on shared memory (which is
>> >> a
>> >> local pipe) and named pipes, but is not listening on TCP/IP. So if you
>> > want
>> >> to connect using TCP/IP and port 1433, you will have to enable TCP/IP
> and
>> >> restart SQL Server. You use the Server Network Utility for that.
>> >> --
>> >> Rick Byham (MSFT)
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >>
>> >> "Safeer" <safeerm@gmail.com> wrote in message
>> >> news:uCxeUt5VHHA.868@TK2MSFTNGP05.phx.gbl...
>> >> > Hi,
>> >> >
>> >> > Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
>> >> > SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard
>> > Edition
>> >> >
>> >> > My workstation is Windows 2000. I am connecting to the server using
>> > MSTSC.
>> >> >
>> >> > My sql server log shows the following.
>> >> > "SQL server listening on Shared Memory, Named Pipes."
>> >> >
>> >> > Actually TCP/IP/1433 is enabled in the server.
>> >> > & I am not able to telnet the machine with port 1433 from the server
>> >> > itself.
>> >> >
>> >> > NB: No one is using this machine now and I need to setup and install
>> >> > service
>> >> > packs. Its a new box with installed SQL 2K and nobody know the SA
>> >> > password.
>> >> >
>> >> > Thanks...Safeer
>> >> >
>> >> >
>> >> > "Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> wrote in
>> > message
>> >> > news:08EB12C9-D906-4977-A40E-0F050C837E1E@microsoft.com...
>> >> >> We need more info.
>> >> >> - What version and edition of SQL Server are you using?
>> >> >> - What version of the Windows are you using?
>> >> >> It sounds like you are connecting from a client on another
>> >> >> computer.
>> >> >> If
>> >> > you
>> >> >> are using SQL Server 2005, use the Surface Area Configuration tool
> to
>> >> >> confirm that your SQL Server instance is listening for remote
>> >> >> connections.
>> >> >> Also, a firewall could be blocking 1433. This is common with
>> >> >> Windows
>> >> >> XP
>> >> >> service pack 2.
>> >> >> If SQL Server is running on Vista, you have other issues.
>> >> >> For SQL Server 2005, there is a short tutorial that will help. See
>> >> >> http://msdn2.microsoft.com/en-us/library/ms345318.aspx
>> >> >> --
>> >> >> Rick Byham (MSFT)
>> >> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> > rights.
>> >> >>
>> >> >> "Safeer" <safeerm@gmail.com> wrote in message
>> >> >> news:eu1sb1rVHHA.1016@TK2MSFTNGP04.phx.gbl...
>> >> >> >I tried telnet ipaddress 1433, its not connecting thru the port.
>> >> >> >
>> >> >> > I am connected to the server directly and then checked the port
>> >> >> > using
>> >> >> > server
>> >> >> > utility and its 1433.
>> >> >> >
>> >> >> >
>> >> >> > "Safeer" <safeerm@gmail.com> wrote in message
>> >> >> > news:e1jmNjrVHHA.4028@TK2MSFTNGP04.phx.gbl...
>> >> >> >> I am having administrative previlages in the SQL Server Machine,
>> >> >> >> but
>> > I
>> >> > am
>> >> >> >> not able to connect to the SQL Server instance. Can you please
>> >> >> >> help.
>> > I
>> >> > am
>> >> >> >> using windows authendication.
>> >> >> >>
>> >> >> >> Thanks...Safeer
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >>
>> >
>> >
>>
>>
>
>