Multiple IP's. Only want 1 for SQL 1433

Hi,
I've got an SQL server 2000 (sp3).
This box has multiple IP addresses. These are for web pages
But i only want the SQL server (port 1433) to listen on one of these addressses.
It seems to listen on all the addresses which i don't want it to. for sercuirty reasons as well
as for it's resource sake.
I've poked around in the properties and connection settings and it doesn't seem to let you change IP's only ports etc.
Please let me know how i can work this out..
Thankyou
There is no way to prevent SQL Server from listening on all the ip
addresses that are bound to NIC cards on the machine. If you want to limit
the ones that clients can connect to then that will have to be impletmented
at the client level.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Multiple IP's. Only want 1 for SQL 1433

Hi,
I've got an SQL server 2000 (sp3).
This box has multiple IP addresses. These are for web pages
But i only want the SQL server (port 1433) to listen on one of these address
ses.
It seems to listen on all the addresses which i don't want it to. for sercui
rty reasons as well
as for it's resource sake.
I've poked around in the properties and connection settings and it doesn't s
eem to let you change IP's only ports etc.
Please let me know how i can work this out..
ThankyouThere is no way to prevent SQL Server from listening on all the ip
addresses that are bound to NIC cards on the machine. If you want to limit
the ones that clients can connect to then that will have to be impletmented
at the client level.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Multiple Instances of SQL Server Service Manager

- I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
2003 (Standard, v5.2) server operating in terminal services mode. The SQL
Server Service Manager is in the startup folder for all users, so multiple
instances are running when more than one user is logged in.
- I am having some problems with this server, so I'm trying to stop anything
that doesn't need to run.
- Can I delete the SQL Server Service Manager from the all users startup
folder? (I would start Service Manager when the Administrator logs in.)
- Thanks.
Hi
SQL Server Service Manager is not required for SQL Server operation. You can
remove it from the startup folder.
You can still manage SQL Server though Enterprise Manager and Control Panel
> Services.
Any reason you have a server that SQL Server needs to share with Terminal
Server users? It is not an optimal configuration.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave" wrote:

> - I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
> 2003 (Standard, v5.2) server operating in terminal services mode. The SQL
> Server Service Manager is in the startup folder for all users, so multiple
> instances are running when more than one user is logged in.
> - I am having some problems with this server, so I'm trying to stop anything
> that doesn't need to run.
> - Can I delete the SQL Server Service Manager from the all users startup
> folder? (I would start Service Manager when the Administrator logs in.)
> - Thanks.
|||Mike,
- Thanks for the info.
- Re your question, I am running Act2005 (which uses SQL2000) for a company
that offices virtually. We setup this server in a hosted datacenter, and
loaded all of our apps (Act, MSOffice, a cpl others) and access everything
using terminal services on the server and remote desktop connection on the
client PCs.
- This configuration generally works, although there are some bugs which I
attribute to the poor job done by my IT provider, and the fact that Act2005
is not designed for terminal services. My only big problem is that Act
occasionally starts using a lot of memory (over 1GB of VM in some cases) and
the whole server slows down.
- Thanks again for your help, and please let me know if you have any
suggestions for my configuration.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> SQL Server Service Manager is not required for SQL Server operation. You can
> remove it from the startup folder.
> You can still manage SQL Server though Enterprise Manager and Control Panel
> Any reason you have a server that SQL Server needs to share with Terminal
> Server users? It is not an optimal configuration.
> Regards
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Dave" wrote:
sql

Multiple Instances of SQL Server Service Manager

- I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
2003 (Standard, v5.2) server operating in terminal services mode. The SQL
Server Service Manager is in the startup folder for all users, so multiple
instances are running when more than one user is logged in.
- I am having some problems with this server, so I'm trying to stop anything
that doesn't need to run.
- Can I delete the SQL Server Service Manager from the all users startup
folder? (I would start Service Manager when the Administrator logs in.)
- Thanks.Hi
SQL Server Service Manager is not required for SQL Server operation. You can
remove it from the startup folder.
You can still manage SQL Server though Enterprise Manager and Control Panel
> Services.
Any reason you have a server that SQL Server needs to share with Terminal
Server users? It is not an optimal configuration.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave" wrote:
> - I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
> 2003 (Standard, v5.2) server operating in terminal services mode. The SQL
> Server Service Manager is in the startup folder for all users, so multiple
> instances are running when more than one user is logged in.
> - I am having some problems with this server, so I'm trying to stop anything
> that doesn't need to run.
> - Can I delete the SQL Server Service Manager from the all users startup
> folder? (I would start Service Manager when the Administrator logs in.)
> - Thanks.|||Mike,
- Thanks for the info.
- Re your question, I am running Act2005 (which uses SQL2000) for a company
that offices virtually. We setup this server in a hosted datacenter, and
loaded all of our apps (Act, MSOffice, a cpl others) and access everything
using terminal services on the server and remote desktop connection on the
client PCs.
- This configuration generally works, although there are some bugs which I
attribute to the poor job done by my IT provider, and the fact that Act2005
is not designed for terminal services. My only big problem is that Act
occasionally starts using a lot of memory (over 1GB of VM in some cases) and
the whole server slows down.
- Thanks again for your help, and please let me know if you have any
suggestions for my configuration.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> SQL Server Service Manager is not required for SQL Server operation. You can
> remove it from the startup folder.
> You can still manage SQL Server though Enterprise Manager and Control Panel
> > Services.
> Any reason you have a server that SQL Server needs to share with Terminal
> Server users? It is not an optimal configuration.
> Regards
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Dave" wrote:
> > - I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
> > 2003 (Standard, v5.2) server operating in terminal services mode. The SQL
> > Server Service Manager is in the startup folder for all users, so multiple
> > instances are running when more than one user is logged in.
> > - I am having some problems with this server, so I'm trying to stop anything
> > that doesn't need to run.
> > - Can I delete the SQL Server Service Manager from the all users startup
> > folder? (I would start Service Manager when the Administrator logs in.)
> > - Thanks.

Multiple Instances of SQL Server Service Manager

- I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
2003 (Standard, v5.2) server operating in terminal services mode. The SQL
Server Service Manager is in the startup folder for all users, so multiple
instances are running when more than one user is logged in.
- I am having some problems with this server, so I'm trying to stop anything
that doesn't need to run.
- Can I delete the SQL Server Service Manager from the all users startup
folder? (I would start Service Manager when the Administrator logs in.)
- Thanks.Hi
SQL Server Service Manager is not required for SQL Server operation. You can
remove it from the startup folder.
You can still manage SQL Server though Enterprise Manager and Control Panel
> Services.
Any reason you have a server that SQL Server needs to share with Terminal
Server users? It is not an optimal configuration.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave" wrote:

> - I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
> 2003 (Standard, v5.2) server operating in terminal services mode. The SQL
> Server Service Manager is in the startup folder for all users, so multiple
> instances are running when more than one user is logged in.
> - I am having some problems with this server, so I'm trying to stop anythi
ng
> that doesn't need to run.
> - Can I delete the SQL Server Service Manager from the all users startup
> folder? (I would start Service Manager when the Administrator logs in.)
> - Thanks.|||Mike,
- Thanks for the info.
- Re your question, I am running Act2005 (which uses SQL2000) for a company
that offices virtually. We setup this server in a hosted datacenter, and
loaded all of our apps (Act, MSOffice, a cpl others) and access everything
using terminal services on the server and remote desktop connection on the
client PCs.
- This configuration generally works, although there are some bugs which I
attribute to the poor job done by my IT provider, and the fact that Act2005
is not designed for terminal services. My only big problem is that Act
occasionally starts using a lot of memory (over 1GB of VM in some cases) and
the whole server slows down.
- Thanks again for your help, and please let me know if you have any
suggestions for my configuration.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> SQL Server Service Manager is not required for SQL Server operation. You c
an
> remove it from the startup folder.
> You can still manage SQL Server though Enterprise Manager and Control Pane
l
> Any reason you have a server that SQL Server needs to share with Terminal
> Server users? It is not an optimal configuration.
> Regards
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Dave" wrote:
>

multiple instances

Hello,
I have a basic question about running multiple instances.
I would like to install 2 instances of SQL server 2000 sp3 and configure
both to the default port 1433.
I only need one up and running at any one time. So shut down one start up
the other.
Can this work? Or the way the "listener service" is configured during
install it will error on installing the second sql instance? or some other
problem?
Any help would be appreciated.
As long as both aren't running at the same time then they can be configured
to listen on the same port. This can be done most easily with the server
network utility post installation. If you try and have both running, the
second one to start will have errors like "SuperSocket Info: Bind failed on
TCP port 1433." Why do you want to do this ?
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"greg" <greg@.nospam.com> wrote in message
news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have a basic question about running multiple instances.
> I would like to install 2 instances of SQL server 2000 sp3 and configure
> both to the default port 1433.
> I only need one up and running at any one time. So shut down one start up
> the other.
> Can this work? Or the way the "listener service" is configured during
> install it will error on installing the second sql instance? or some
> other
> problem?
>
> Any help would be appreciated.
>
>
>
|||Thanks for the info.
It is a testing box. And 1 product requires case sensitivity on and one
requires it off.
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:OoOVIYRkEHA.2908@.TK2MSFTNGP10.phx.gbl...
> As long as both aren't running at the same time then they can be
configured
> to listen on the same port. This can be done most easily with the server
> network utility post installation. If you try and have both running, the
> second one to start will have errors like "SuperSocket Info: Bind failed
on[vbcol=seagreen]
> TCP port 1433." Why do you want to do this ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "greg" <greg@.nospam.com> wrote in message
> news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
up
>
|||greg wrote:[vbcol=seagreen]
> Thanks for the info.
> It is a testing box. And 1 product requires case sensitivity on and
> one requires it off.
>
>
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
> news:OoOVIYRkEHA.2908@.TK2MSFTNGP10.phx.gbl...
Why can't you run both instances at the same time?
David G.

multiple instances

Hello,
I have a basic question about running multiple instances.
I would like to install 2 instances of SQL server 2000 sp3 and configure
both to the default port 1433.
I only need one up and running at any one time. So shut down one start up
the other.
Can this work? Or the way the "listener service" is configured during
install it will error on installing the second sql instance? or some other
problem?
Any help would be appreciated.As long as both aren't running at the same time then they can be configured
to listen on the same port. This can be done most easily with the server
network utility post installation. If you try and have both running, the
second one to start will have errors like "SuperSocket Info: Bind failed on
TCP port 1433." Why do you want to do this ?
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"greg" <greg@.nospam.com> wrote in message
news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have a basic question about running multiple instances.
> I would like to install 2 instances of SQL server 2000 sp3 and configure
> both to the default port 1433.
> I only need one up and running at any one time. So shut down one start up
> the other.
> Can this work? Or the way the "listener service" is configured during
> install it will error on installing the second sql instance? or some
> other
> problem?
>
> Any help would be appreciated.
>
>
>|||Thanks for the info.
It is a testing box. And 1 product requires case sensitivity on and one
requires it off.
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:OoOVIYRkEHA.2908@.TK2MSFTNGP10.phx.gbl...
> As long as both aren't running at the same time then they can be
configured
> to listen on the same port. This can be done most easily with the server
> network utility post installation. If you try and have both running, the
> second one to start will have errors like "SuperSocket Info: Bind failed
on
> TCP port 1433." Why do you want to do this ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "greg" <greg@.nospam.com> wrote in message
> news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
up[vbcol=seagreen]
>|||greg wrote:[vbcol=seagreen]
> Thanks for the info.
> It is a testing box. And 1 product requires case sensitivity on and
> one requires it off.
>
>
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
> news:OoOVIYRkEHA.2908@.TK2MSFTNGP10.phx.gbl...
Why can't you run both instances at the same time?
David G.

multiple instances

Hello,
I have a basic question about running multiple instances.
I would like to install 2 instances of SQL server 2000 sp3 and configure
both to the default port 1433.
I only need one up and running at any one time. So shut down one start up
the other.
Can this work? Or the way the "listener service" is configured during
install it will error on installing the second sql instance? or some other
problem?
Any help would be appreciated.As long as both aren't running at the same time then they can be configured
to listen on the same port. This can be done most easily with the server
network utility post installation. If you try and have both running, the
second one to start will have errors like "SuperSocket Info: Bind failed on
TCP port 1433." Why do you want to do this ?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"greg" <greg@.nospam.com> wrote in message
news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have a basic question about running multiple instances.
> I would like to install 2 instances of SQL server 2000 sp3 and configure
> both to the default port 1433.
> I only need one up and running at any one time. So shut down one start up
> the other.
> Can this work? Or the way the "listener service" is configured during
> install it will error on installing the second sql instance? or some
> other
> problem?
>
> Any help would be appreciated.
>
>
>|||Thanks for the info.
It is a testing box. And 1 product requires case sensitivity on and one
requires it off.
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:OoOVIYRkEHA.2908@.TK2MSFTNGP10.phx.gbl...
> As long as both aren't running at the same time then they can be
configured
> to listen on the same port. This can be done most easily with the server
> network utility post installation. If you try and have both running, the
> second one to start will have errors like "SuperSocket Info: Bind failed
on
> TCP port 1433." Why do you want to do this ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "greg" <greg@.nospam.com> wrote in message
> news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> > Hello,
> >
> > I have a basic question about running multiple instances.
> >
> > I would like to install 2 instances of SQL server 2000 sp3 and configure
> > both to the default port 1433.
> >
> > I only need one up and running at any one time. So shut down one start
up
> > the other.
> >
> > Can this work? Or the way the "listener service" is configured during
> > install it will error on installing the second sql instance? or some
> > other
> > problem?
> >
> >
> >
> > Any help would be appreciated.
> >
> >
> >
> >
> >
> >
>|||greg wrote:
> Thanks for the info.
> It is a testing box. And 1 product requires case sensitivity on and
> one requires it off.
>
>
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
> news:OoOVIYRkEHA.2908@.TK2MSFTNGP10.phx.gbl...
>> As long as both aren't running at the same time then they can be
>> configured to listen on the same port. This can be done most easily
>> with the server network utility post installation. If you try and
>> have both running, the second one to start will have errors like
>> "SuperSocket Info: Bind failed on TCP port 1433." Why do you want to
>> do this ?
>> --
>> HTH
>> Jasper Smith (SQL Server MVP)
>> http://www.sqldbatips.com
>> I support PASS - the definitive, global
>> community for SQL Server professionals -
>> http://www.sqlpass.org
>> "greg" <greg@.nospam.com> wrote in message
>> news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
>> Hello,
>> I have a basic question about running multiple instances.
>> I would like to install 2 instances of SQL server 2000 sp3 and
>> configure both to the default port 1433.
>> I only need one up and running at any one time. So shut down one
>> start up the other.
>> Can this work? Or the way the "listener service" is configured
>> during install it will error on installing the second sql instance?
>> or some other
>> problem?
>>
>> Any help would be appreciated.
Why can't you run both instances at the same time?
--
David G.