Re: Issuses installing MSDE 2000 SP3a on Windows XP SP2

From: Andrea Montanari (andrea.sqlDMO_at_virgilio.it)
Date: 10/18/04


Date: Mon, 18 Oct 2004 19:19:00 +0200

hi,
"Dancer" <REMOVE THISdancer_yard@hotmail.com> ha scritto nel messaggio
news:u4wSXKTtEHA.1216@TK2MSFTNGP10.phx.gbl
>...
>
> I have also tried typing in the instance namely ClientName\VSDOTNET in
> Server drop list within SQL Server Service Manager. The Services
> work when i do this but the setting is not retained when system is
> rebooted.
>
> I have tried switching the firewall back to ON status but that does
> not solve this issue.
>
> ...........
> 1. Anybody know a solution for this issue?

please have a look at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;814132

>
> 2. What are the port settings that I need to open in the firewall and
> how do i do this ?

as you installed a named instance, it will not be listening on standard SQL
Server port, TCP/IP 1433, but usually it's port is dynamically assigned
based on a service listening on UDP 1434 port, which then redirects all
connections to the appropriate assigned port...
you can hae a look at http://support.microsoft.com/default.aspx?kbid=841249
for further info on how configure SQL Server (MSDE) running on Win XP Pro sp
2...

personally I had a test on a virtual machine...
assigned a static port to a named instance (say TCP/IP 666 as I do not have
a Doom server in my Lan =;-D)
closed UDP 1434 port
set exceptions on TCP/IP 666 port for both the subnet mask or specific IP
addresses of my lan
and all worked like a charm..
caveat:
specifying a static port implies that all remote clients have to set an
alias using Client Network Utility (cliconfg.exe) pointing to the specified
666 Doom TCP/IP port

>
> 3. I am planning to program with VS 2003 and need to use the MSDE,
> are there any gremlings to look out for ?

nope, just and advice... MSDE is intended for deployment and not for
development... you can find SQL Server Developer Edition at about $49.00,
which includes all dev tools you'll need to fine tune, troubleshoot and test
you MSDE based applications...

-- 
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm        http://italy.mvps.org
DbaMgr2k ver 0.9.1  -  DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply


Relevant Pages

  • Re: Remote ODBC connection to SQL Server 2005 Exp.
    ... Using the port 1433 is not the only way to access a SQL-Server via tcp/ip: ... my IP address has to pass through their router. ... the SQL Server Configuration Manager, clicked on "SQL Server 2005 Network ...
    (microsoft.public.access.externaldata)
  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Getting an absolutely up to date version of MSDE
    ... The real reason for updating is that I have online SQL Server ... > Enterprise Manager connection does not now work (has worked splendidly ... They say that this is because my MSDE has not been upgraded to ... port 1433 is the standard IANA assigned port to Microsoft for SQL ...
    (microsoft.public.sqlserver.msde)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... Either SQL Server 2000 or SQL Server 2005. ... So you have to move one of them to another port. ... You could allow an program exception in your firewall instead of a port number exception. ... I understand that you can connect to SQL 2000 named instance on the local ...
    (microsoft.public.sqlserver.setup)