listening on... interfaces

The errorlog on my installation reports the following:
SQL server listening on MY.INTERNAL.IP.1: 22847.
SQL server listening on MY.PUBLIC.IP: 22847.
SQL server listening on MY.INTERNAL.IP.2: 22847.
SQL server listening on 127.0.0.1: 22847.
SQL server listening on TCP, Named Pipes.
SQL Server is ready for client connections
How can I configure SQL to not listen at all on the public IP?
Thanks.
-RickHi
You have to configure IPSec at NIC level to disallow connections on the
public IP. By default and design, SQL Server will always listen on all IP's
and SQL Server can not be configured not to listen on them.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rick" <Rick@.discussions.microsoft.com> wrote in message
news:67BA2827-A522-40DB-B288-0C63A9A1797B@.microsoft.com...
> The errorlog on my installation reports the following:
> SQL server listening on MY.INTERNAL.IP.1: 22847.
> SQL server listening on MY.PUBLIC.IP: 22847.
> SQL server listening on MY.INTERNAL.IP.2: 22847.
> SQL server listening on 127.0.0.1: 22847.
> SQL server listening on TCP, Named Pipes.
> SQL Server is ready for client connections
> How can I configure SQL to not listen at all on the public IP?
> Thanks.
> -Rick
>|||Wow, I have to admit I don't know the first thing about IPSec. Is this a
configuration I can do in the OS?
Am I barking up the right tree? Isn't it common to not want your SQL Server
to be listening to the wild wild internet?
Thanks,
-Rick
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> You have to configure IPSec at NIC level to disallow connections on the
> public IP. By default and design, SQL Server will always listen on all IP'
s
> and SQL Server can not be configured not to listen on them.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Rick" <Rick@.discussions.microsoft.com> wrote in message
> news:67BA2827-A522-40DB-B288-0C63A9A1797B@.microsoft.com...
>
>|||> Isn't it common to not want your SQL Server
> to be listening to the wild wild internet?
Definitely. That's what firewalls are for.
Hope this helps.
Dan Guzman
SQL Server MVP
"Rick" <Rick@.discussions.microsoft.com> wrote in message
news:404BBC8C-884B-4ED5-8C24-703E44D0F35C@.microsoft.com...[vbcol=seagreen]
> Wow, I have to admit I don't know the first thing about IPSec. Is this a
> configuration I can do in the OS?
> Am I barking up the right tree? Isn't it common to not want your SQL
> Server
> to be listening to the wild wild internet?
> Thanks,
> -Rick
> "Mike Epprecht (SQL MVP)" wrote:
>|||"Dan Guzman" wrote:
> Definitely. That's what firewalls are for.
Thanks Dan. The system is a typical (dual-homed) SBS2003. I thought that I
got a level of firewalling with SBS. I guess I was naive. So I'm not sure
of which way to go. Would you folks recommend:
1) New hardware firewall (any suggestions?)
2) TCP/IP (and UDP) filtering in Advanced TCP/IP Settings?
3) IPSec policies?
4) Move my SQL databases to an internal server?
5) Combination of above?|||> 1) New hardware firewall (any suggestions?)
> 2) TCP/IP (and UDP) filtering in Advanced TCP/IP Settings?
> 3) IPSec policies?
> 4) Move my SQL databases to an internal server?
> 5) Combination of above?
Every company I've worked for uses a hardware firewall and deploys SQL
Servers on an internal network. You can get the job done using
IPSec/Filtering on your SQL Servers but it's best not to let the traffic in
at all. I'm not a network guy so you probably don't want my recommendations
on hardware :-)
Hope this helps.
Dan Guzman
SQL Server MVP
"Rick" <Rick@.discussions.microsoft.com> wrote in message
news:60607EA5-883E-4882-9EC7-2F0B4CB5FEBC@.microsoft.com...
> "Dan Guzman" wrote:
> Thanks Dan. The system is a typical (dual-homed) SBS2003. I thought that
> I
> got a level of firewalling with SBS. I guess I was naive. So I'm not
> sure
> of which way to go. Would you folks recommend:
> 1) New hardware firewall (any suggestions?)
> 2) TCP/IP (and UDP) filtering in Advanced TCP/IP Settings?
> 3) IPSec policies?
> 4) Move my SQL databases to an internal server?
> 5) Combination of above?
>

listening on tcp port

Can someone please help me. For somereason my sql server isnt listening on the TCP ports but is listening on the shared pipes port. I congifured the server network utility to listen on the tcp port but when i look at the logs it still isnt listening. I
restarted the server and agent after i configured it and i even started the server. Doese anyone know how to enable SQL server to listen on TCP ports if it isnt already doing so.
Thanks
John
Hi
You can see the server protocols through server network manager. It could be
that it is not listening on the ports that you exepect. Therefore check out
the properties for TCP/IP.
John
"jaccurso" <jaccurso@.liserver.com> wrote in message
news:76A57F55-303E-4C38-8699-A2AD5E7C7D0D@.microsoft.com...
> Can someone please help me. For somereason my sql server isnt listening
on the TCP ports but is listening on the shared pipes port. I congifured
the server network utility to listen on the tcp port but when i look at the
logs it still isnt listening. I restarted the server and agent after i
configured it and i even started the server. Doese anyone know how to
enable SQL server to listen on TCP ports if it isnt already doing so.
> Thanks
> John

listening on tcp port

Can someone please help me. For somereason my sql server isnt listening on
the TCP ports but is listening on the shared pipes port. I congifured the s
erver network utility to listen on the tcp port but when i look at the logs
it still isnt listening. I
restarted the server and agent after i configured it and i even started the
server. Doese anyone know how to enable SQL server to listen on TCP ports i
f it isnt already doing so.
Thanks
JohnHi
You can see the server protocols through server network manager. It could be
that it is not listening on the ports that you exepect. Therefore check out
the properties for TCP/IP.
John
"jaccurso" <jaccurso@.liserver.com> wrote in message
news:76A57F55-303E-4C38-8699-A2AD5E7C7D0D@.microsoft.com...
> Can someone please help me. For somereason my sql server isnt listening
on the TCP ports but is listening on the shared pipes port. I congifured
the server network utility to listen on the tcp port but when i look at the
logs it still isnt listening. I restarted the server and agent after i
configured it and i even started the server. Doese anyone know how to
enable SQL server to listen on TCP ports if it isnt already doing so.
> Thanks
> John

listening on tcp port

Can someone please help me. For somereason my sql server isnt listening on the TCP ports but is listening on the shared pipes port. I congifured the server network utility to listen on the tcp port but when i look at the logs it still isnt listening. I restarted the server and agent after i configured it and i even started the server. Doese anyone know how to enable SQL server to listen on TCP ports if it isnt already doing so
Thank
JohnHi
You can see the server protocols through server network manager. It could be
that it is not listening on the ports that you exepect. Therefore check out
the properties for TCP/IP.
John
"jaccurso" <jaccurso@.liserver.com> wrote in message
news:76A57F55-303E-4C38-8699-A2AD5E7C7D0D@.microsoft.com...
> Can someone please help me. For somereason my sql server isnt listening
on the TCP ports but is listening on the shared pipes port. I congifured
the server network utility to listen on the tcp port but when i look at the
logs it still isnt listening. I restarted the server and agent after i
configured it and i even started the server. Doese anyone know how to
enable SQL server to listen on TCP ports if it isnt already doing so.
> Thanks
> John

Listening IP address

Hi,
I'm running MS SQL 2000 on Windows 2000 adv srv with 2 network adapters on
it .
How can I configure MS SQL to listen from one IP address and don't listen
from another?
Thanks,
LeonidYou can't do this with SQL. You could block the port on the adapter using
IPSEC
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leonid" <le_le_to@.hotmail.!!!NO-SPAM!!!.com> wrote in message
news:qJGdnZeQApEvx5Xd4p2dnA@.comcast.com...
> Hi,
> I'm running MS SQL 2000 on Windows 2000 adv srv with 2 network adapters on
> it .
> How can I configure MS SQL to listen from one IP address and don't listen
> from another?
> Thanks,
> Leonid
>sql

Listening IP address

Hi,
I'm running MS SQL 2000 on Windows 2000 adv srv with 2 network adapters on
it .
How can I configure MS SQL to listen from one IP address and don't listen
from another?
Thanks,
LeonidYou can't do this with SQL. You could block the port on the adapter using
IPSEC
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leonid" <le_le_to@.hotmail.!!!NO-SPAM!!!.com> wrote in message
news:qJGdnZeQApEvx5Xd4p2dnA@.comcast.com...

quote:

---

> Hi,
> I'm running MS SQL 2000 on Windows 2000 adv srv with 2 network adapters on
> it .
> How can I configure MS SQL to listen from one IP address and don't listen
> from another?
> Thanks,
> Leonid
>

---

|||By default you can't do this. You could put the SQL Server behind an ISA
server (firewall) and only publish the IP that you need.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Listening IP address

Hi,
I'm running MS SQL 2000 on Windows 2000 adv srv with 2 network adapters on
it .
How can I configure MS SQL to listen from one IP address and don't listen
from another?
Thanks,
LeonidYou can't do this with SQL. You could block the port on the adapter using
IPSEC
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leonid" <le_le_to@.hotmail.!!!NO-SPAM!!!.com> wrote in message
news:qJGdnZeQApEvx5Xd4p2dnA@.comcast.com...

quote:

---

> Hi,
> I'm running MS SQL 2000 on Windows 2000 adv srv with 2 network adapters on
> it .
> How can I configure MS SQL to listen from one IP address and don't listen
> from another?
> Thanks,
> Leonid
>

---

Listening for report events

I have a series of reports and want to fire off a stored procedure to update
a "Printed date" column in my database. I don't want to do this from the
dataset that populates my datset as I only want this to occur if the report
is successfully generated. Is there any way I can do this with the scheduler?
If not, are the any report events that I can listen for? And or any other
solution to this problem.Sorry. I don't think I made my intentions very clear. I meant to say that I
have a series of report, and want to fire off a stored procedure everytime a
report is successfully generated.
"Graham Hope" wrote:
> I have a series of reports and want to fire off a stored procedure to update
> a "Printed date" column in my database. I don't want to do this from the
> dataset that populates my datset as I only want this to occur if the report
> is successfully generated. Is there any way I can do this with the scheduler?
> If not, are the any report events that I can listen for? And or any other
> solution to this problem.