Re: Kerio 2.1.5 Blocking SQL remote server
From: Ross McKay (rosko_at_zeta.NOT.THIS.BIT.org.au)
Date: 09/01/03
- Next message: Uli Wachowitz: "Re: Newbie question, ping of death"
- Previous message: mhicaoidh: "Re: Kerio 2.1.5 Blocking SQL remote server"
- In reply to: mhicaoidh: "Kerio 2.1.5 Blocking SQL remote server"
- Next in thread: mhicaoidh: "Re: Kerio 2.1.5 Blocking SQL remote server"
- Reply: mhicaoidh: "Re: Kerio 2.1.5 Blocking SQL remote server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 01 Sep 2003 16:21:17 +1000
On Mon, 01 Sep 2003 05:44:10 GMT, "mhicaoidh"
<®êmõvé_mhic_aoidh@hotÑîXmailŠPäM.com> wrote:
>I am trying to get a computer to connect to a MS SQL 2000 server that is
>running on another computer on the LAN. After beating my head against the
>wall over why the server cannot be seen from the client, I discovered that
>the culprit is Kerio.
>...
Don't know enough about Kerio to comment on that, but:
SQL Server 2000 supports a variety of connection protocols. The default
is usually named pipes, which of course requires the usual Microsoft
stuff being trusted between computers. The generally easier way (and
faster also) is TCP/IP - SQL Server listens on a known port, your client
connects to that port. The default port number is 1433.
Given this, you should only need to allow traffic to port 1433 on the
server from your client PC. You can also allow traffic to port 1434 if
you are using the SQL Service Service Manager or Enterprise Manager, as
it looks for servers on this port - but it isn't needed generally.
You don't mention what your client software is, or how it is configured.
If you are using the SQL Server client software and have the network
utilities, you can run the Client Network Utility and create an alias
for your server specifically nominating TCP/IP protocol and the port
number (if it isn't 1433).
If not, and you are using ODBC, you can set your connection to
specifically use TCP/IP (and again specify the port if necessary).
If instead you are using OLE-DB, as part of your connection string
specify the TCP/IP Sockets library (as below). To specify a port other
than 1433, I believe that you can append it to the Data Source or Server
with a comma (haven't tried it).
Network Library=dbmssocn;
HTH
Ross.
-- Ross McKay, WebAware Pty Ltd "Since when were you so generously inarticulate?" - Elvis Costello
- Next message: Uli Wachowitz: "Re: Newbie question, ping of death"
- Previous message: mhicaoidh: "Re: Kerio 2.1.5 Blocking SQL remote server"
- In reply to: mhicaoidh: "Kerio 2.1.5 Blocking SQL remote server"
- Next in thread: mhicaoidh: "Re: Kerio 2.1.5 Blocking SQL remote server"
- Reply: mhicaoidh: "Re: Kerio 2.1.5 Blocking SQL remote server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
