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
> 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