Re: Coonecting to an External SQL Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Chris,

If you manually telnet to the remote SQL server on 1433 does it get blocked
the same way?

telnet x.x.x.x 1433

where x.x.x.x is the IP address of the remote SQL server.

Based on what you are seeing in the Monitoring it would appear that the rule
is not matching for some reason.


--

Hope that helps,
David Copeland
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.


SBS Newsgroups:

SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

"Chris Guimbellot" <cguimbellot@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:O5t65Vr%23FHA.904@xxxxxxxxxxxxxxxxxxxxxxx
> David,
>
> Thanks for your continued help. Yes, it is denying on port 1433 -
> Microsoft SQL (TCP). The rule that I created is not showing up in the
> logging at all. What is denying my attempted connection is the SBS
> Internet Access Rule. Just as an FYI, the SBS Internet Access Rule is the
> same one that allows me to connect to the external server from a client.
> It seems the rule that I created for SQL TCP and UDP isn't coming into
> play at all. Any other ideas? Thanks,
>
> Chris
>
> "David Copeland [MSFT]" <davidcop@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:epx2WRn%23FHA.160@xxxxxxxxxxxxxxxxxxxxxxx
>> Chris,
>>
>> Is it showing a denied for TCP port 1433? or a different port? Is the
>> rule that is denying it after your rule that you created? What does it
>> show as the source network?
>>
>>
>> --
>>
>> Hope that helps,
>> David Copeland
>> Microsoft Small Business Server Support
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> SBS Newsgroups:
>>
>> SBS v4.x: microsoft.public.backoffice.smallbiz
>> SBS 2000: microsoft.public.backoffice.smallbiz2000
>> SBS 2003: microsoft.public.windows.server.sbs
>>
>> "Chris Guimbellot" <cguimbellot@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:uffDnQg%23FHA.984@xxxxxxxxxxxxxxxxxxxxxxx
>>> David,
>>>
>>> Thanks for the help. I had already tried making the access rule as you
>>> described, but I did it again just in case. When I looked at the logging
>>> area of ISA, I saw a Denied Connection message. Its pretty much the
>>> same problem I had before. Any ideas? Thanks again,
>>>
>>> Chris
>>>
>>> "David Copeland [MSFT]" <davidcop@xxxxxxxxxxxxxxxxxxxx> wrote in message
>>> news:%23fSfmM$9FHA.3980@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Chris,
>>>>
>>>> With trying to do the connection from the server itself you are correct
>>>> you wouldn't install the firewall client on the server. In that case
>>>> with ISA 2004 you would need to create an Acces rule to allow that
>>>> traffic by right clicking on Firewall Policy and selecting New Access
>>>> Rule.
>>>> Then in the wizard use something like
>>>>
>>>> Name: Remote SQL
>>>> Action: Allow
>>>> Protocols: Selected protocols and add Microsoft SQL (TCP) and Microsoft
>>>> SQL (UDP) Assuming that the remote SQL Server is allowing/using TCP
>>>> (sockets)
>>>> Access Rule Sources: Localhost
>>>> Access Rule Destination: You could either be specific and create a
>>>> Computer or maybe Computer Set as a Network Entity and then select it
>>>> or depending on needs use External under Networks.
>>>> User Set: Depends on needs.. may need to select All Users
>>>>
>>>> Once you complete the wizard and click the Apply.. test connecting to
>>>> the remote server again.. If it's working then in the Monitoring you
>>>> should see the Remote SQL rule allowing access.
>>>>
>>>>
>>>> --
>>>>
>>>> Hope that helps,
>>>> David Copeland
>>>> Microsoft Small Business Server Support
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>>
>>>>
>>>> SBS Newsgroups:
>>>>
>>>> SBS v4.x: microsoft.public.backoffice.smallbiz
>>>> SBS 2000: microsoft.public.backoffice.smallbiz2000
>>>> SBS 2003: microsoft.public.windows.server.sbs
>>>>
>>>> "Chris Guimbellot" <cguimbellot@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>>>> message news:%23eVEm$19FHA.3808@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> David,
>>>>>
>>>>> Thanks for the response. I do not have the Firewall client installed.
>>>>> I am trying to access it from the server. I don't think I need the
>>>>> firewall client installed on the server, do I? I can connect to it
>>>>> from a client running Enterprise Manager as well as Firewall Client.
>>>>> That said, it seems like I might need to install Firewall Client on
>>>>> the server, but not sure.
>>>>>
>>>>> When I tried the monitoring like you mentioned, when I tried from the
>>>>> server, it was telling me that the action was Denied and gave the SBS
>>>>> Internet Access Rule as the reason. When I looked at the rule, it
>>>>> seems that it allows everything. I have to be missing something. When
>>>>> tried to connect on the client, it let me though using the same SBS
>>>>> Internet Access Rule that blocked me from doing it on the server. Does
>>>>> that mean that the custom rule that I created is useless? I ask
>>>>> because I don't see it anywhere in the logging.
>>>>>
>>>>> I really need to run from the server because I have data transfers
>>>>> that go out to that database every night.
>>>>>
>>>>> Any help would be most appreciated. Thanks,
>>>>>
>>>>> Chris
>>>>>
>>>>> "David Copeland [MSFT]" <davidcop@xxxxxxxxxxxxxxxxxxxx> wrote in
>>>>> message news:eX2n7C19FHA.320@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>> Chris,
>>>>>>
>>>>>> Does the machine you are trying to connect from have the ISA firewall
>>>>>> client installed? If not, does it work if you install it? What does
>>>>>> it show in the ISA Server Management mmc under Monitoring and then
>>>>>> click on the Logging tab.. If you start the logging and then attempt
>>>>>> to connect do you see the traffic destined for that server? Does it
>>>>>> show it as being allowed or blocked? If it's blocking it which rule
>>>>>> does it show that is preventing it?
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Hope that helps,
>>>>>> David Copeland
>>>>>> Microsoft Small Business Server Support
>>>>>>
>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>> rights.
>>>>>>
>>>>>>
>>>>>> SBS Newsgroups:
>>>>>>
>>>>>> SBS v4.x: microsoft.public.backoffice.smallbiz
>>>>>> SBS 2000: microsoft.public.backoffice.smallbiz2000
>>>>>> SBS 2003: microsoft.public.windows.server.sbs
>>>>>>
>>>>>> "Chris Guimbellot" <cguimbellot@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>>>>>> message news:eu%23hQHy9FHA.1484@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> Hello,
>>>>>>>
>>>>>>> SBS2003 Premium, SQL2000, ISA2004
>>>>>>>
>>>>>>> I am having trouble connecting to a SQL Server 2000 database located
>>>>>>> on my ISP. I know that the problem lies in ISA, but cant figure it
>>>>>>> out. I tried to creating an access rule using the built-in Microsoft
>>>>>>> SQL (TCP) protocol (port 1433 outbound) to allows clients on the
>>>>>>> internal network to connect outbound. However, when I try to add a
>>>>>>> new registration in SQL Enterprise Manager to the server with my
>>>>>>> ISP, I get am access denied message. If I plug directly into the
>>>>>>> internet (bypassing the ISA server) I can connect without a problem.
>>>>>>> I know that there is some simple setting I am missing, but cant
>>>>>>> figure it out. Any suggestions would be appreciated. Thanks,
>>>>>>>
>>>>>>> Chris
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.