Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / March 2008

Tip: Looking for answers? Try searching our database.

SQL Server 2005 Express Question - Cross Post

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tim Morrison - 08 Mar 2008 17:48 GMT
I have purchased a dedicated server from GoDaddy.

Ive installed MS-SQL Express 2005 to be used for an internal application.

Windows 2003

Firewall Turned Off (just until i figure this problem out)

I cannot connect to the database from remote. Ive tried everything ive read
about (turning on remote connections, etc) and am still having no luck.

GoDaddy wont help because i didnt purchase their managed services.

Is there something else im missing? Is this a setup issue, or something
particular with a GoDaddy dedicated server?

Should SQL 2005 EXPRESS allow this type of connection?

TIA

Tim
Tibor Karaszi - 08 Mar 2008 19:27 GMT
On the machine, use "SQL Server Configuration Manager" and enable TCP/IP netlib.

Signature

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

>I have purchased a dedicated server from GoDaddy.
>
[quoted text clipped - 17 lines]
>
> Tim
Tim Morrison - 08 Mar 2008 21:49 GMT
Ive already done that, and restarted the service. still no luck. GoDaddy
says they do not have anything blocked.

I am using a named instance if that matters.

Tim

> On the machine, use "SQL Server Configuration Manager" and enable TCP/IP
> netlib.
[quoted text clipped - 21 lines]
>>
>> Tim
Tibor Karaszi - 09 Mar 2008 09:05 GMT
> I am using a named instance if that matters.

How do you connect to the machine? Try for instance using IP address:
123.45.56.67\InstanceName

You can also specify the port number when you connect, and skip the instancename. Say that port
number is 1223:
123.45.56.67,1223

You will find the port number in SQL Server errorlog file. If you connect by instance name, then the
firewall need to let through both the "data" port (1223 in above example), TCP, as well as 1434,
UDP.

Signature

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

> Ive already done that, and restarted the service. still no luck. GoDaddy says they do not have
> anything blocked.
[quoted text clipped - 26 lines]
>>>
>>> Tim
Tim Morrison - 09 Mar 2008 14:54 GMT
This is the message if i do not specify a port:

TITLE: Connect to Server
------------------------------

Cannot connect to ***.***.**.**\KSOFT. [IP ADDRESS HIDDEN]

------------------------------
ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server.  When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&
EvtID=-1&LinkId=20476


------------------------------
BUTTONS:

OK
------------------------------

This is the message if i do specift a port:

TITLE: Connect to Server
------------------------------

Cannot connect to ***.***.**.**,1433\KSOFT.

------------------------------
ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server.  When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061)

For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&
EvtID=10061&LinkId=20476


------------------------------
BUTTONS:

OK
------------------------------

Thanks.

Tim

>> I am using a named instance if that matters.
>
[quoted text clipped - 42 lines]
>>>>
>>>> Tim
Tibor Karaszi - 09 Mar 2008 15:19 GMT
You said in an earlier post:

>>> I am using a named instance if that matters.

But you try to connect using:

> Cannot connect to ***.***.**.**,1433\KSOFT.

Why do you specify 1433 above? 1333 is for a default instance but you said you are using a named
instance? Also, the format is wrong. If you specify a port number, then you *do not* specify an
instance name.
Signature

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

> This is the message if i do not specify a port:
>
[quoted text clipped - 91 lines]
>>>>>
>>>>> Tim
Tim Morrison - 09 Mar 2008 16:53 GMT
I didnt know that. I tried just the dynamic port set in the configuration
manager, and now all is working. Thank you very much.

Tim

> You said in an earlier post:
>
[quoted text clipped - 110 lines]
>>>>>>
>>>>>> Tim
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.