Thanks a Lot for your quick response
Could I force the fixed port in the registry? The MSDE doesn't provide
the administration tool you mention and the database is distributed
automatically to the client bundled in an app.
Ruben Sanchez
Argentina
[quoted text, click to view] kevmc@online.microsoft.com (Kevin McDonnell [MSFT]) wrote in message news:<ut40mPbdEHA.2932@cpmsftngxa10.phx.gbl>...
> You need to set a fixed port for MSDE to listen on. Instances by default
> listen on dynamic ports.
> The client needs to use TCP/IP to connect and not Named Pipes. That's why
> opening 135 and 445 allows it to work.
> You're right these ports should NOT be open on the firewall.
>
> To check the port being used.
>
> If you are using the Server Network Utility, click "Start", point to
> "All Programs", point to Microsoft SQL Server, and then click "Server
> Network Utility". If you are using MSDE or the command line, click
> "Start", and then click "Run". In the "Run" dialog box, type
> "svrnetcn.exe" (without the quotation marks), and then click "OK".
>
> To set the port to a fixed port, just type in the port number you'd like.
> Then restart the MSSQL$ instance for it to take
> affect.
>
> Then, change you clients to connect to this specific port. Either use the
> SQL Client network Utility or change your connection strings
>
>
>
> Thanks,
>
> Kevin McDonnell
> Microsoft Corporation
>
You should be able to run : svrnetcn.exe if you have MSDE.
Otherwise, the registry location is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\InstanceNameHere\MSSQLServer\SuperSocketNetLib\Tcp
Modify the TcpPort
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.