From: Ellen K. 

Thanks, that is very helpful.

On Sun, 23 Oct 2005 16:08:04 -0400, "Geo" 
wrote in message :

>Same difference, all of netlink is "external" meaning it is
all physically
>on the internet. However I can block traffic using any of a number of
>methods, software firewall on the sql server, a null route in the local
>router, a gateway router null route, a packet shaper/blocker, I mean there
>are a ton of ways to regulate traffic on the network even if that network is
>part of the internet and directly accessible without blocks.
>
>Their "external IP address" may have a rule in a software
firewall that says
>block anything not from "external IP address B" which could
just be their
>web server and that web server may require credentials to access anything
>from the database or may also have IP restrictions. So it's really not
>exposed to the net in general or maybe it is. I can't say without more
>information.
>
>Geo.
>
>"Ellen K."  wrote in message
>news:a3inl1tkh43a7chhovs5pm4aavk1m4sqgc{at}4ax.com...
>> I think I used the wrong terminology, I meant "external IP
address", not
>> "public IP address".  Our own servers, except for the
mail server, all
>> only have internal IP addresses.
>>
>> On Sun, 23 Oct 2005 12:23:50 -0400, "Geo"
 wrote in
>> message :
>>
>> >It depends on what they mean by "it has a public IP
address". All my
>servers
>> >have a public IP address at netlink but the SQL server can't talk to
>> >anything outside netlink.
>> >
>> >It is something to be concerned about but without knowing the
exact setup
>I
>> >can't say if it's a high or low risk.
>> >
>> >Geo.
>> >
>> >"Ellen K."  wrote in message
>> >news:2s4ml1hqp0j39pq719j08l3e4od9h1ohn4{at}4ax.com...
>> >> Meanwhile the guy who is now in charge of all the
infrastructure stuff
>> >> came back from vacation and I found out that we have NO IDEA what's
>> >> actually going on behind the eOn router, i.e. for all we know maybe
>that
>> >> SQL Server has a public IP address.  I was astounded to
learn that we
>> >> can't see anything about it.   NetworkGuy had told me that box is
>behind
>> >> our firewall... but if that's the case, AND it has a
public IP address,
>> >> then I think we are vulnerable, right?
>> >
>>
>

--- BBBS/NT v4.01 Flag-5