Re: Can't connect to SQL Server through ISA
From: Phillip Windell (_at_.)
Date: 01/27/05
- Next message: Phillip Windell: "Re: ISA 2004 Server Errors"
- Previous message: Phillip Windell: "Re: Web App needs information about original client's IP"
- In reply to: Hoof Hearted: "Can't connect to SQL Server through ISA"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 Jan 2005 16:13:35 -0600
"Hoof Hearted" <HoofHearted@discussions.microsoft.com> wrote in message
news:D8AEAC67-363E-44AA-A7D5-4A9B19A56330@microsoft.com...
> SBS 2003: I can't connect into my SQL server from the outside world.
However
> I've noticed that I can connect briefly immediately after the server has
been
> rebooted. I assume this must be because SQL Server starts prior to ISA. I
can
> connect perfectly on the internal network. But only by using the internal
IP
> address. I can't connect by using the server name.
If you can connect by using the internal IP as the "target" then you have a
severly flawed design. The internal IP#s should never be able to be used as
"destinations" and they should not even be "routable" from the Public
Network.
> I don't know much about ISA, but various KB articles say that all I need
is
> a Protocol Definition for TCP Port 1433 outbound, and a Protocol Rule
which
> makes use of the definition.
No, this is so a user behind ISA can connect to an SQL Server that is on the
outside out there in Internet Land.
For a user outside in Internet Land to access a SQL Server that is behind
the proxy requires the proxy to "Publish" the SQL Server using the Server
Publishing Features of ISA.
-- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com
- Next message: Phillip Windell: "Re: ISA 2004 Server Errors"
- Previous message: Phillip Windell: "Re: Web App needs information about original client's IP"
- In reply to: Hoof Hearted: "Can't connect to SQL Server through ISA"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|