CFF KB - Carrz-Fox-Fire Promotions Knowledge Base
CFF KB is all about 1 thing: The Sharing of Knowledge and the Power we gain from it.Knowledge Base
- Breadrumbs:
Connect to SQL Server 2005 Through the network
- Article ID:
137 - Date Created
Wednesday, June 15, 2011 - Last Updated
Wednesday, June 15, 2011 - This Article Has been Viewed
1636 times - Short Desc
When you set up SQL Server on a Machine, and then setup the client on another machine, you have to enable TCP/IP and open a port on SQL Server in order to access it from the SQL Server Client. - Details
To access SQL Server from a Networking Client, you must first enable TCP/IP and open a port, if you do not open a port in SQL Server, you will receive the following error.TITLE: Connect to Server
------------------------------
Cannot connect to your-server\instance2005.
------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server, Error: -1) - Recreate Issue
To recreate this issue.
Do not Enable TCP/IP or assign a Port #.
This will cause the above error. - Resolve Issue
To correct this issue, perform the following actions on your machine running SQL Server.
There are 2 ways of getting to the area that you will be performing this action in.
#1:
Click [Start]
Then [All Programs]
Then [Microsoft SQL Server 2005]
Then [Configuration Tools]
Then [SQL Server Configuration Manager]
Then [SQL Server 2005 Network Configuration]
Then [Protocols for SERVERNAME]
#2:
Click [Start]
Then [Administrator Tools]
Then [Computer Management]
Once the window opens, from the Navigation Tree on the Left
Choose [Services and Applications]
Then [SQL Server Configuration Manager]
Then [SQL Server 2005 Network Configuration]
Then [Protocols for SERVERNAME]
Next, perform the following:
Choose [TCP/IP]
Right Click and choose [Enable]
Click [OK] to the dialogAny Changes made will be saved; however, they will not take effect until the service is stopped and restarted.
Now, Double Click on [TCP/IP] (To bring up its Properly page)
Click on the [IP Address] Tab
In IP1 (or) the IP that has an actual IP Address to it, not the default 127.0.0.1
[TCP Port]: [443]
Click [Apply] then [OK]
Click [OK] to the dialog
Now, you must restart SQL Server
To do this, do the following:
Click on [Start]
Then [Administrator Tools]
Then [Services]
Scroll through the list and
[Right Click] on [SQL Server]
Choose [Restart]
If you do not have [Administrator Tools] in your Start Menu.
Click [My Computer]
Then [Control Panel]
Then [Administrator Tools]
Then [Services]
Now, on the Client machine, connect to your SQL Server Instance with the
[Server Name]: machine-name\sqlinstance
[Authentication]: SQL Server Authentication
[Login]: username
[Password]: ********
Share With Friends (Updated 6-8-2010)
Recent Articles
All Topics
- Coming Soon - Knowledge Exchange
Trending Articles
- Microsoft VBScript runtime error '800a0046' Permission denied FileSystemObject 24694
- Microsoft OLE DB Provider for SQL Server error '80040e57' String or binary data would be truncated. or The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data. 21297
- ADODB.Parameters error '800a0e7c' Parameter object is improperly defined 19544
- After Effects warning: Audio conforming failed for the following file .cfa. Perhaps due to disk space 17785
- The backup set holds a backup of a database other than the existing 16825