> You can check to see if it's a firewall or port blocking issue or not by
> using TELNET and seeing if it can connect. Type this from a command
> prompt (replace INET_SERVER with your server name).
>
> telnet INET_SERVER 1433
>
> If the telnet session fails to connect, you have a firewall issue or are
> not using the correct port or host name - when I try to connect to
> something that is blocked by a firewall, the error reported for me was
> "could not open connection to the host on port xxxx: Connect failed".
>
> If you get a screen that appears to be the start of the connected session,
> you can be sure you have actually opened a port to another machine. You
> won't be able to do anything meaningful from this telnet session, but it
> rules out firewall, port, or hostname issues. Close it and use the same
> settings to connect with Query Analyzer or Enterprise Manager.
>
> Good luck,
> Tony Sebion
>
> "Josep" <hola@microsoft.com> wrote in message
> news:#1fFelMxFHA.700@TK2MSFTNGP11.phx.gbl:
>
>> Hi !!
>>
>> I would like to connect to a SQL Server (MSDE edition) that's in
>> Internet,
>> using Enterprise Manager either Query Analizer. For these I've configured
>> the client tool as:
>>
>> Server Alias: INET_SERVER
>> Net: TCP/IP
>> Connection parameters:
>> Server name: [DNS_NAME]\[REMOTE_SERVER_NAME]\[INSTANCE_NAME]
>> Port number: 1433
>>
>> Althought I've tried to configure the server name in different ways, I
>> haven't found the successful way to do it.
>> I don't think it's a firewall problem. In theory I've successfull
>> disabled.
>>
>>
>> Thanks !!
>>
>> Josep.
>

> Well, it seems I didn't unblock the port successfully. So, my work is to
> find how this router works... where else I've to configure the ports...
> but I like to know that's not an SQL Server problem :-)
>
> Thank you Tony for explaining me this very fast way, and easy, to know if
> a port is blocked or not :D
>
> Josep.
>
>
>
> "Tony Sebion" <tony@sebion.com> escribió en el mensaje
> news:3q2bkiFcpoaaU1@individual.net...
>> You can check to see if it's a firewall or port blocking issue or not by
>> using TELNET and seeing if it can connect. Type this from a command
>> prompt (replace INET_SERVER with your server name).
>>
>> telnet INET_SERVER 1433
>>
>> If the telnet session fails to connect, you have a firewall issue or are
>> not using the correct port or host name - when I try to connect to
>> something that is blocked by a firewall, the error reported for me was
>> "could not open connection to the host on port xxxx: Connect failed".
>>
>> If you get a screen that appears to be the start of the connected
>> session, you can be sure you have actually opened a port to another
>> machine. You won't be able to do anything meaningful from this telnet
>> session, but it rules out firewall, port, or hostname issues. Close it
>> and use the same settings to connect with Query Analyzer or Enterprise
>> Manager.
>>
>> Good luck,
>> Tony Sebion
>>
>> "Josep" <hola@microsoft.com> wrote in message
>> news:#1fFelMxFHA.700@TK2MSFTNGP11.phx.gbl:
>>
>>> Hi !!
>>>
>>> I would like to connect to a SQL Server (MSDE edition) that's in
>>> Internet,
>>> using Enterprise Manager either Query Analizer. For these I've
>>> configured
>>> the client tool as:
>>>
>>> Server Alias: INET_SERVER
>>> Net: TCP/IP
>>> Connection parameters:
>>> Server name: [DNS_NAME]\[REMOTE_SERVER_NAME]\[INSTANCE_NAME]
>>> Port number: 1433
>>>
>>> Althought I've tried to configure the server name in different ways, I
>>> haven't found the successful way to do it.
>>> I don't think it's a firewall problem. In theory I've successfull
>>> disabled.
>>>
>>>
>>> Thanks !!
>>>
>>> Josep.
>>
>
>