How to configure MSDE to listen on TCP/IP

Hi:
I'm not able to connect to MSDE remotely. From the SQL Server logs, it
is listening on Shared Memory only. How do I configure it to listen on
TCP/IP ?
The MSDE is running on WinXP Pro SP2, and there is a instance of
SQL2005 Express installed side by side, the SQL2005 Express is
configure to listen on port 1618. The firewall already turned off.
Another problem is related to SQL2005 Express... I'm not able to
connect to the SQL2005 Express remotely when the firewall turned ON,
even port 1618 is already add into exception list.
Any idea ?
Thanks
JCVoonProblem solved. I enable the Named Pipes protocol using SVRNETCN.exe
and restart the MSDE.
Why must enabled the Named Pipes when I only need TCP/IP protocol '
JCVoon
On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
> Hi:
> I'm not able to connect to MSDE remotely. From the SQL Server logs, it
> is listening on Shared Memory only. How do I configure it to listen on
> TCP/IP ?
> The MSDE is running on WinXP Pro SP2, and there is a instance of
> SQL2005 Express installed side by side, the SQL2005 Express is
> configure to listen on port 1618. The firewall already turned off.
> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
> Any idea ?
> Thanks
> JCVoon|||network communications are typically more interactive for named pipes wherea
s.
data transmissions are more streamlined and have less overhead in TCP/IP
You can have more in SQL BOL
"jcvoon" wrote:

> Problem solved. I enable the Named Pipes protocol using SVRNETCN.exe
> and restart the MSDE.
> Why must enabled the Named Pipes when I only need TCP/IP protocol '
> JCVoon
>
> On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
>|||> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
You have to add the C:\Program Files\Microsoft SQL
Server\90\Shared\sqlbrowser.exe into the exceptions list.