See below...
--
Tibor Karaszi
MCSE, MCSD, MCT, SQL Server MVP
Cornerstone Sweden AB
>How exactly does a client go about using Multiprotocol?
Client Configuration Utility in the SQL Server program group. Net Library
Tab, default network.
Quote:> I thought that was a
>server side issue. Also, Sql Server may be listening on 1433, but all the
>clients I have seen start pounding on doors starting at 1490 and if no one
>answers move up to 15xx. After three doors (ports) are attempted the client
>quits. Client in this case is i/wsql.
I believe that 1433 is when Sockets is used. You are refering to
Multiprotocol (RPC), which might be handeled drifferently. (Note that I'm no
network expert, though :-).
>>Johnny,
>>Three guesses:
>>The client is using Multiprotocol, instead of TCP/IP _sockets_. Check with
>>Client Config Utility.
>>The server isn't listening on TCP/IP _Sockets_. Check with SQL Server
>Setup.
>>The port on SQL Server is changed. Check with SQL Server Setup.
>>--
>>Tibor Karaszi
>>MCSE, MCSD, MCT, SQL Server MVP
>>Cornerstone Sweden AB
>>>Can anyone show me the steps to connect MS SQL Server via Internet
>>>using TCP/IP protocol in the client side ? So that, I can use MS Query
>>>or ISQL_W to retrieve the records.
>>>I've tested the connection is failure when there is a Firewall before
>>>the MS SQL Server (That means, it is ok when no firewall exist). I am
>>>sure that I've added and opened the port (e.g. 1433) for MS SQL
>>>Server, but the error is still exist when using ISQL_W or via the
>>>ODBC.
>>>Please help and describe in details.
>>>Thanks
>>>Johnny
>>>Please reply to newsgroup directly or click the following email
>>>address.
by