MSDE SP3a and XP SP2

Hi
According to various things I've read, XP SP2 will close off SQL Server
ports unless SQL/MSDE SP3 is installed.
However, I've installed MSDE 2000a (equivalent to MSDE 2000 SP3a) with
XP Pro SP2 and no network machine can see the DB server.
I uninstall XP SP2 and the network can see the DB server fine.
Can anybody throw any light onto this?
Thanks
Tony
Hi Tony,
XP SP2 installs an Internet Connection Firewall by default. It will block
the ports you need. You will need to "punch a hole" in the firewall for the
MSDE port (normally 1433 but you can change it using svrnetcn.exe).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Tony Taylor" <tony@.postopticsNOSPAM.co.uk> wrote in message
news:e1DMi4dhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi
> According to various things I've read, XP SP2 will close off SQL Server
> ports unless SQL/MSDE SP3 is installed.
> However, I've installed MSDE 2000a (equivalent to MSDE 2000 SP3a) with
> XP Pro SP2 and no network machine can see the DB server.
> I uninstall XP SP2 and the network can see the DB server fine.
> Can anybody throw any light onto this?
> Thanks
> Tony
|||Greg Low [MVP] wrote:

> Hi Tony,
> XP SP2 installs an Internet Connection Firewall by default. It will block
> the ports you need. You will need to "punch a hole" in the firewall for the
> MSDE port (normally 1433 but you can change it using svrnetcn.exe).
> HTH,
>
Hi Greg
Thanks for getting back quickly.
How can I find which port the server is listening on?
We're using a named instance which won't use the standard 1433.
With XP SP2, I've run netstat and the sqlservr.exe PID is not listed so
I can't get the port from that. svrnetcn.exe tells me the port is 0 (I
assume that's because XP SP2 has switched it off).
Thanks again
Tony
|||hi Tony,
"Tony Taylor" <tony@.postopticsNOSPAM.co.uk> ha scritto nel messaggio
news:%23tWgd9ehEHA.3912@.TK2MSFTNGP11.phx.gbl...
> How can I find which port the server is listening on?
> We're using a named instance which won't use the standard 1433.
> With XP SP2, I've run netstat and the sqlservr.exe PID is not listed so
> I can't get the port from that. svrnetcn.exe tells me the port is 0 (I
> assume that's because XP SP2 has switched it off).
Named instaces are resolved by the host listening on UDP port 1434, which
then redirect tha specific calls to a dinamically assigned port (as
default)... this is a dynamic port assignement behaviour...
with Windows XP sp2 Windows Firewall which blocs all these connections, you
have to manual set the port you want them to use, so chose a fixed port for
your named instance with Server Network Utility (svrnetcn.exe), open that
port on the Windows Firewall, and, for all remote client, use Client Network
Utility (cloconfg.exe) to map connections to that static port
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||You can also add a firewall exception for sqlserver.exe, rather than opening
the port wide open. If other executables need to accept connections, also add
exceptions for them. That will cover any port, but only for that executable.
"Andrea Montanari" wrote:

> hi Tony,
> "Tony Taylor" <tony@.postopticsNOSPAM.co.uk> ha scritto nel messaggio
> news:%23tWgd9ehEHA.3912@.TK2MSFTNGP11.phx.gbl...
> Named instaces are resolved by the host listening on UDP port 1434, which
> then redirect tha specific calls to a dinamically assigned port (as
> default)... this is a dynamic port assignement behaviour...
> with Windows XP sp2 Windows Firewall which blocs all these connections, you
> have to manual set the port you want them to use, so chose a fixed port for
> your named instance with Server Network Utility (svrnetcn.exe), open that
> port on the Windows Firewall, and, for all remote client, use Client Network
> Utility (cloconfg.exe) to map connections to that static port
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Damian,
"Damian" <Damian@.discussions.microsoft.com> ha scritto nel messaggio
news:9F11A754-13A0-4033-81E4-C8354D510EEA@.microsoft.com...
> You can also add a firewall exception for sqlserver.exe, rather than
opening
> the port wide open. If other executables need to accept connections, also
add
> exceptions for them. That will cover any port, but only for that
executable.
still do not have Windows Firewall enabled, but I do think the problem is
outside calls to SQL Server and not the opposite, requiring that
sqlserver.exe should be added to the exceptions list..
but will investigate as soon as I get WinXP sp2 installed
you have to cover outside calls from IIS, winforms apps and so on...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Damian wrote:
[vbcol=seagreen]
> You can also add a firewall exception for sqlserver.exe, rather than opening
> the port wide open. If other executables need to accept connections, also add
> exceptions for them. That will cover any port, but only for that executable.
> "Andrea Montanari" wrote:
>
Hi chaps
I've tried the follwing:
use svrnetcn.exe to assign a static port to the named instance, open
that port in Windows Firewall and use cliconfg.exe to map connections to
that port
and
allow sqlservr.exe through as an exception in Windows Firewall
but neither have worked. Maybe I've missed something.
Has anyone actually had any success connecting across a network with XP
SP2 on the MSDE box?
Thanks
Tony