I am trying to do a SQL Express Unmanned installation and I have been having trouble with the TCP/IP settings.
I have tried both disablenetworkprotocols=0 and =2 and after the installation is complete I open the configuration manager to check the settings. It says TCP/IP is enabled but when i check the properties it says both IP1 (my ip address) and IP2 (localhost 127.0.0.1) are both disabled.
To me this doesnt make any sence. I can enable TCP/IP at installation but the IPs are disabled making a TCP connection impossible without further configuration. Is that not illogical
Does anyone know how to enable these, specifically IP2, at setup or by a script. I need a way to enable them programmatically so the user will not have to open the configuration manager an enable them himself
Thanks for your help
Default TCP/IP Settings
Hot Topic
- P2P Replication Conflicts
- Error while restoring SQL7 data on SQL Express 2005
- Using Reporting Service 2005 with Analysis Service 2005?
- SQL Server 2005 Enterprise - x64 Edition - CoCreateInstance() failure
- Cube Size Estimation formula....
- The Query Could not be processed. The data provider didn't supply any other error information (SSAS 2005, SharePoint, OWC 11)
- Registry to store configuration values ?
- Point #2
- Connecting to SQL 2005 server on Windows 2003
- SOS, please help
SQL Server
- rsStreamNotFound error is comming..using Reporting services
- Error during Loading Data form a falt file into DB2 database??s
- SQL DMO - Backward Compatibility Components Redistributable
- Package still referencing old parameters from an old connection
- How to convert Dynamic Properties to SSIS Package Config?
- Update conflict
- Mapping UDF Parameters to Variables
- SQL Mobile 2005 Merge Replication with SQL 2005 x64
- installing sql server mobile in an hp ipaq rx1955
- no help dialog in vs ssis
Default TCP/IP Settings
Alexander WF
It sounds like your network interface should be configured correctly. The setting under the IP Address -> Enabled is only used if the Listen All under the Protocol Tab is set to "No" by default I believe it is should be set to yes with your configuration.
mr_venhola
With the default connfiguration after installation I cannot make a TCP/IP connection using either computername/instance name or localhost as the server
The minimum I have to do to get a connection is to set the IPALL TCP port to 1433
Is there any reason why i would have to set this port to get a connection and is there a way to set the port by a script or a stored procedure
Thanks