Showing posts with label ports. Show all posts
Showing posts with label ports. Show all posts
Monday, February 20, 2012
Ports used by ReportViewer web controls
When a ReportViewer control is used to access a report on a remote SQL Server database, on what ports does the communcation occur? Does the control communicate on on the SQL Server ports of 1433 and 1434 or does it communcate as a web service on port 80 (or 443 for HTPPS)?It will depend on the url that you set for the report server. For a standard url it will use 80 (and 443), however you can always pass in a url for a non-standard port.
PORTS USED
Hey all
I am using Transactional replication with updatebale subscriptions
What network ports are used for SQL server 2005 replication
This is for firewall config.
Thanx
The agent will attempt to connect to SQL Server on the port that you have setup in the Network Config. Ususally its 1433 TCP by default.
Martin
|||
Hi all,
I have some doubts about this issue too. We are preparing a landscape to set SQL Server 2005 replication between a internal server and another one in Internet. We need to set the firewall to allow only the ports needed. The only port we need is 1433? The distributor and publisher are in the server in Internet, and the subscriber will stay in our internal network.
Regards
Sergio
PORTS USED
Hey all
I am using Transactional replication with updatebale subscriptions
What network ports are used for SQL server 2005 replication
This is for firewall config.
Thanx
The agent will attempt to connect to SQL Server on the port that you have setup in the Network Config. Ususally its 1433 TCP by default.
Martin
|||Hi all,
I have some doubts about this issue too. We are preparing a landscape to set SQL Server 2005 replication between a internal server and another one in Internet. We need to set the firewall to allow only the ports needed. The only port we need is 1433? The distributor and publisher are in the server in Internet, and the subscriber will stay in our internal network.
Regards
Sergio
PORTS USED
Hey all
I am using Transactional replication with updatebale subscriptions
What network ports are used for SQL server 2005 replication
This is for firewall config.
Thanx
The agent will attempt to connect to SQL Server on the port that you have setup in the Network Config. Ususally its 1433 TCP by default.
Martin
|||Hi all,
I have some doubts about this issue too. We are preparing a landscape to set SQL Server 2005 replication between a internal server and another one in Internet. We need to set the firewall to allow only the ports needed. The only port we need is 1433? The distributor and publisher are in the server in Internet, and the subscriber will stay in our internal network.
Regards
Sergio
Ports to open in Windows Firewall for SQL Server 2005
I'm running the Develpers version of SQL Server 2005 on my developer machine.
I want to test an application from another machine but can neither log on nor
use the SQL Server Management Studio from the remote machine unless I turn
off the Windows Firewall on the development machine. (I made sure to enable
remote connections via the Surface Configuration Tool too).
Though I seem to have the correct services listed in the "Exclusions" of the
Windows Firewall, I think that I should probably explicitly open the ports
that SQL Server and the Management Studio use. What are the correct ports or
is there a better way to work through the Windows Firewall. (This problem
should only exist in my development environment because I would not use the
Windows Firewall in a production setting on the Server)
Michael Hockstein
Did you also enable and start the sqlbrowser service?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"michael" <howlinghound@.nospam.nospam> wrote in message
news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
> I'm running the Develpers version of SQL Server 2005 on my developer
> machine.
> I want to test an application from another machine but can neither log on
> nor
> use the SQL Server Management Studio from the remote machine unless I turn
> off the Windows Firewall on the development machine. (I made sure to
> enable
> remote connections via the Surface Configuration Tool too).
> Though I seem to have the correct services listed in the "Exclusions" of
> the
> Windows Firewall, I think that I should probably explicitly open the ports
> that SQL Server and the Management Studio use. What are the correct ports
> or
> is there a better way to work through the Windows Firewall. (This problem
> should only exist in my development environment because I would not use
> the
> Windows Firewall in a production setting on the Server)
>
> --
> Michael Hockstein
|||Yes it is enabled and running. I can establish connections if I disable the
Windows Firewall on the machine with the SQL Server instance.
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> Did you also enable and start the sqlbrowser service?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
>
>
|||After a little searching, I thought that simple enabling port 1433 on the
server machine's fire wall would do the trick. It does allow connection to
the server for data exchange but it does not allow remote administration via
the SQL Server Management Studio. What additional port need to be opened to
allow this?
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> Did you also enable and start the sqlbrowser service?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
>
>
|||Hi there michael,
If your connecting fine to the database and it accepts data exchange,
perhaps you might look at the database permissions. Rather than any more
ports.
Opening 1433 within the firewall as far as im aware, is all you need for
admin.
Give the test account full sysadmin rights, and try that.
regards..
"michael" <howlinghound@.nospam.nospam> wrote in message
news:601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com...[vbcol=seagreen]
> After a little searching, I thought that simple enabling port 1433 on the
> server machine's fire wall would do the trick. It does allow connection to
> the server for data exchange but it does not allow remote administration
> via
> the SQL Server Management Studio. What additional port need to be opened
> to
> allow this?
> --
> Michael Hockstein
>
> "Roger Wolter[MSFT]" wrote:
|||Hi Michael,
As Grumpy has mentioned, generally 1433 port is enough for connecting to
SQL server database engine. Also, for 2005, you can also try opening the
1434 UDP port since it will be used for establishing linked connection from
other applications. See the following article which describes the
"Connecting SQL Server over internet...":
Connecting to SQL Server over the Internet
http://msdn2.microsoft.com/en-us/library/ms175483.aspx
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "grumpy" <dtREMOVE2k@.blueTHISyonder.co.uk>
| Newsgroups: microsoft.public.sqlserver.connect
| References: <171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com>
<#imE4XEJGHA.3904@.TK2MSFTNGP10.phx.gbl>
<601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com>
| Subject: Re: Ports to open in Windows Firewall for SQL Server 2005
| Lines: 71
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <x%dDf.11677$wl.6669@.text.news.blueyonder.co.uk>
| Date: Mon, 30 Jan 2006 01:31:09 GMT
| NNTP-Posting-Host: 82.42.42.142
| X-Complaints-To: abuse@.blueyonder.co.uk
| X-Trace: text.news.blueyonder.co.uk 1138584669 82.42.42.142 (Mon, 30 Jan
2006 01:31:09 GMT)
| NNTP-Posting-Date: Mon, 30 Jan 2006 01:31:09 GMT
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfee d00.sul.t-online.de!newsfe
ed01.sul.t-online.de!t-online.de!solnet.ch!solnet.ch!newsfeed.freenet.de! bor
der2.nntp.ams.giganews.com!border1.nntp.ams.gigane ws.com!nntp.giganews.com!p
e2.news.blueyonder.co.uk!blueyonder!pe1.news.bluey onder.co.uk!blueyonder!tex
t.news.blueyonder.co.uk!53ab2750!not-for-mail
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.connect:46765
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Hi there michael,
| If your connecting fine to the database and it accepts data exchange,
| perhaps you might look at the database permissions. Rather than any more
| ports.
|
| Opening 1433 within the firewall as far as im aware, is all you need for
| admin.
|
| Give the test account full sysadmin rights, and try that.
|
| regards..
|
| "michael" <howlinghound@.nospam.nospam> wrote in message
| news:601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com...
| > After a little searching, I thought that simple enabling port 1433 on
the
| > server machine's fire wall would do the trick. It does allow connection
to
| > the server for data exchange but it does not allow remote
administration
| > via
| > the SQL Server Management Studio. What additional port need to be
opened
| > to
| > allow this?
| >
| > --
| > Michael Hockstein
| >
| >
| > "Roger Wolter[MSFT]" wrote:
| >
| >> Did you also enable and start the sqlbrowser service?
| >>
| >> --
| >> This posting is provided "AS IS" with no warranties, and confers no
| >> rights.
| >> Use of included script samples are subject to the terms specified at
| >> http://www.microsoft.com/info/cpyright.htm
| >>
| >> "michael" <howlinghound@.nospam.nospam> wrote in message
| >> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
| >> > I'm running the Develpers version of SQL Server 2005 on my developer
| >> > machine.
| >> > I want to test an application from another machine but can neither
log
| >> > on
| >> > nor
| >> > use the SQL Server Management Studio from the remote machine unless
I
| >> > turn
| >> > off the Windows Firewall on the development machine. (I made sure to
| >> > enable
| >> > remote connections via the Surface Configuration Tool too).
| >> >
| >> > Though I seem to have the correct services listed in the
"Exclusions"
| >> > of
| >> > the
| >> > Windows Firewall, I think that I should probably explicitly open the
| >> > ports
| >> > that SQL Server and the Management Studio use. What are the correct
| >> > ports
| >> > or
| >> > is there a better way to work through the Windows Firewall. (This
| >> > problem
| >> > should only exist in my development environment because I would not
use
| >> > the
| >> > Windows Firewall in a production setting on the Server)
| >> >
| >> >
| >> > --
| >> > Michael Hockstein
| >>
| >>
| >>
|
|
|
|||I meant is sqlbrowser enabled through the firewall.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"michael" <howlinghound@.nospam.nospam> wrote in message
news:D7E1B295-425A-47F9-9B9F-7E439508C1A9@.microsoft.com...[vbcol=seagreen]
> Yes it is enabled and running. I can establish connections if I disable
> the
> Windows Firewall on the machine with the SQL Server instance.
> --
> Michael Hockstein
>
> "Roger Wolter[MSFT]" wrote:
|||That's the trick! Enable the SQL Browser and Port 1433 in the Windows
Firewall and you get both connectivity and the ability to remotely
administer. Thanks!
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> I meant is sqlbrowser enabled through the firewall.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:D7E1B295-425A-47F9-9B9F-7E439508C1A9@.microsoft.com...
>
>
I want to test an application from another machine but can neither log on nor
use the SQL Server Management Studio from the remote machine unless I turn
off the Windows Firewall on the development machine. (I made sure to enable
remote connections via the Surface Configuration Tool too).
Though I seem to have the correct services listed in the "Exclusions" of the
Windows Firewall, I think that I should probably explicitly open the ports
that SQL Server and the Management Studio use. What are the correct ports or
is there a better way to work through the Windows Firewall. (This problem
should only exist in my development environment because I would not use the
Windows Firewall in a production setting on the Server)
Michael Hockstein
Did you also enable and start the sqlbrowser service?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"michael" <howlinghound@.nospam.nospam> wrote in message
news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
> I'm running the Develpers version of SQL Server 2005 on my developer
> machine.
> I want to test an application from another machine but can neither log on
> nor
> use the SQL Server Management Studio from the remote machine unless I turn
> off the Windows Firewall on the development machine. (I made sure to
> enable
> remote connections via the Surface Configuration Tool too).
> Though I seem to have the correct services listed in the "Exclusions" of
> the
> Windows Firewall, I think that I should probably explicitly open the ports
> that SQL Server and the Management Studio use. What are the correct ports
> or
> is there a better way to work through the Windows Firewall. (This problem
> should only exist in my development environment because I would not use
> the
> Windows Firewall in a production setting on the Server)
>
> --
> Michael Hockstein
|||Yes it is enabled and running. I can establish connections if I disable the
Windows Firewall on the machine with the SQL Server instance.
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> Did you also enable and start the sqlbrowser service?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
>
>
|||After a little searching, I thought that simple enabling port 1433 on the
server machine's fire wall would do the trick. It does allow connection to
the server for data exchange but it does not allow remote administration via
the SQL Server Management Studio. What additional port need to be opened to
allow this?
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> Did you also enable and start the sqlbrowser service?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
>
>
|||Hi there michael,
If your connecting fine to the database and it accepts data exchange,
perhaps you might look at the database permissions. Rather than any more
ports.
Opening 1433 within the firewall as far as im aware, is all you need for
admin.
Give the test account full sysadmin rights, and try that.
regards..
"michael" <howlinghound@.nospam.nospam> wrote in message
news:601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com...[vbcol=seagreen]
> After a little searching, I thought that simple enabling port 1433 on the
> server machine's fire wall would do the trick. It does allow connection to
> the server for data exchange but it does not allow remote administration
> via
> the SQL Server Management Studio. What additional port need to be opened
> to
> allow this?
> --
> Michael Hockstein
>
> "Roger Wolter[MSFT]" wrote:
|||Hi Michael,
As Grumpy has mentioned, generally 1433 port is enough for connecting to
SQL server database engine. Also, for 2005, you can also try opening the
1434 UDP port since it will be used for establishing linked connection from
other applications. See the following article which describes the
"Connecting SQL Server over internet...":
Connecting to SQL Server over the Internet
http://msdn2.microsoft.com/en-us/library/ms175483.aspx
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "grumpy" <dtREMOVE2k@.blueTHISyonder.co.uk>
| Newsgroups: microsoft.public.sqlserver.connect
| References: <171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com>
<#imE4XEJGHA.3904@.TK2MSFTNGP10.phx.gbl>
<601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com>
| Subject: Re: Ports to open in Windows Firewall for SQL Server 2005
| Lines: 71
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <x%dDf.11677$wl.6669@.text.news.blueyonder.co.uk>
| Date: Mon, 30 Jan 2006 01:31:09 GMT
| NNTP-Posting-Host: 82.42.42.142
| X-Complaints-To: abuse@.blueyonder.co.uk
| X-Trace: text.news.blueyonder.co.uk 1138584669 82.42.42.142 (Mon, 30 Jan
2006 01:31:09 GMT)
| NNTP-Posting-Date: Mon, 30 Jan 2006 01:31:09 GMT
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfee d00.sul.t-online.de!newsfe
ed01.sul.t-online.de!t-online.de!solnet.ch!solnet.ch!newsfeed.freenet.de! bor
der2.nntp.ams.giganews.com!border1.nntp.ams.gigane ws.com!nntp.giganews.com!p
e2.news.blueyonder.co.uk!blueyonder!pe1.news.bluey onder.co.uk!blueyonder!tex
t.news.blueyonder.co.uk!53ab2750!not-for-mail
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.connect:46765
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Hi there michael,
| If your connecting fine to the database and it accepts data exchange,
| perhaps you might look at the database permissions. Rather than any more
| ports.
|
| Opening 1433 within the firewall as far as im aware, is all you need for
| admin.
|
| Give the test account full sysadmin rights, and try that.
|
| regards..
|
| "michael" <howlinghound@.nospam.nospam> wrote in message
| news:601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com...
| > After a little searching, I thought that simple enabling port 1433 on
the
| > server machine's fire wall would do the trick. It does allow connection
to
| > the server for data exchange but it does not allow remote
administration
| > via
| > the SQL Server Management Studio. What additional port need to be
opened
| > to
| > allow this?
| >
| > --
| > Michael Hockstein
| >
| >
| > "Roger Wolter[MSFT]" wrote:
| >
| >> Did you also enable and start the sqlbrowser service?
| >>
| >> --
| >> This posting is provided "AS IS" with no warranties, and confers no
| >> rights.
| >> Use of included script samples are subject to the terms specified at
| >> http://www.microsoft.com/info/cpyright.htm
| >>
| >> "michael" <howlinghound@.nospam.nospam> wrote in message
| >> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
| >> > I'm running the Develpers version of SQL Server 2005 on my developer
| >> > machine.
| >> > I want to test an application from another machine but can neither
log
| >> > on
| >> > nor
| >> > use the SQL Server Management Studio from the remote machine unless
I
| >> > turn
| >> > off the Windows Firewall on the development machine. (I made sure to
| >> > enable
| >> > remote connections via the Surface Configuration Tool too).
| >> >
| >> > Though I seem to have the correct services listed in the
"Exclusions"
| >> > of
| >> > the
| >> > Windows Firewall, I think that I should probably explicitly open the
| >> > ports
| >> > that SQL Server and the Management Studio use. What are the correct
| >> > ports
| >> > or
| >> > is there a better way to work through the Windows Firewall. (This
| >> > problem
| >> > should only exist in my development environment because I would not
use
| >> > the
| >> > Windows Firewall in a production setting on the Server)
| >> >
| >> >
| >> > --
| >> > Michael Hockstein
| >>
| >>
| >>
|
|
|
|||I meant is sqlbrowser enabled through the firewall.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"michael" <howlinghound@.nospam.nospam> wrote in message
news:D7E1B295-425A-47F9-9B9F-7E439508C1A9@.microsoft.com...[vbcol=seagreen]
> Yes it is enabled and running. I can establish connections if I disable
> the
> Windows Firewall on the machine with the SQL Server instance.
> --
> Michael Hockstein
>
> "Roger Wolter[MSFT]" wrote:
|||That's the trick! Enable the SQL Browser and Port 1433 in the Windows
Firewall and you get both connectivity and the ability to remotely
administer. Thanks!
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> I meant is sqlbrowser enabled through the firewall.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:D7E1B295-425A-47F9-9B9F-7E439508C1A9@.microsoft.com...
>
>
Ports to open in Windows Firewall for SQL Server 2005
I'm running the Develpers version of SQL Server 2005 on my developer machine
.
I want to test an application from another machine but can neither log on no
r
use the SQL Server Management Studio from the remote machine unless I turn
off the Windows Firewall on the development machine. (I made sure to enable
remote connections via the Surface Configuration Tool too).
Though I seem to have the correct services listed in the "Exclusions" of the
Windows Firewall, I think that I should probably explicitly open the ports
that SQL Server and the Management Studio use. What are the correct ports or
is there a better way to work through the Windows Firewall. (This problem
should only exist in my development environment because I would not use the
Windows Firewall in a production setting on the Server)
Michael HocksteinDid you also enable and start the sqlbrowser service?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"michael" <howlinghound@.nospam.nospam> wrote in message
news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
> I'm running the Develpers version of SQL Server 2005 on my developer
> machine.
> I want to test an application from another machine but can neither log on
> nor
> use the SQL Server Management Studio from the remote machine unless I turn
> off the Windows Firewall on the development machine. (I made sure to
> enable
> remote connections via the Surface Configuration Tool too).
> Though I seem to have the correct services listed in the "Exclusions" of
> the
> Windows Firewall, I think that I should probably explicitly open the ports
> that SQL Server and the Management Studio use. What are the correct ports
> or
> is there a better way to work through the Windows Firewall. (This problem
> should only exist in my development environment because I would not use
> the
> Windows Firewall in a production setting on the Server)
>
> --
> Michael Hockstein|||Yes it is enabled and running. I can establish connections if I disable the
Windows Firewall on the machine with the SQL Server instance.
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> Did you also enable and start the sqlbrowser service?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
>
>|||After a little searching, I thought that simple enabling port 1433 on the
server machine's fire wall would do the trick. It does allow connection to
the server for data exchange but it does not allow remote administration via
the SQL Server Management Studio. What additional port need to be opened to
allow this?
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> Did you also enable and start the sqlbrowser service?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
>
>|||Hi there michael,
If your connecting fine to the database and it accepts data exchange,
perhaps you might look at the database permissions. Rather than any more
ports.
Opening 1433 within the firewall as far as im aware, is all you need for
admin.
Give the test account full sysadmin rights, and try that.
regards..
"michael" <howlinghound@.nospam.nospam> wrote in message
news:601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com...[vbcol=seagreen]
> After a little searching, I thought that simple enabling port 1433 on the
> server machine's fire wall would do the trick. It does allow connection to
> the server for data exchange but it does not allow remote administration
> via
> the SQL Server Management Studio. What additional port need to be opened
> to
> allow this?
> --
> Michael Hockstein
>
> "Roger Wolter[MSFT]" wrote:
>|||Hi Michael,
As Grumpy has mentioned, generally 1433 port is enough for connecting to
SQL server database engine. Also, for 2005, you can also try opening the
1434 UDP port since it will be used for establishing linked connection from
other applications. See the following article which describes the
"Connecting SQL Server over internet...":
Connecting to SQL Server over the Internet
http://msdn2.microsoft.com/en-us/library/ms175483.aspx
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "grumpy" <dtREMOVE2k@.blueTHISyonder.co.uk>
| Newsgroups: microsoft.public.sqlserver.connect
| References: <171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com>
<#imE4XEJGHA.3904@.TK2MSFTNGP10.phx.gbl>
<601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com>
| Subject: Re: Ports to open in Windows Firewall for SQL Server 2005
| Lines: 71
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <x%dDf.11677$wl.6669@.text.news.blueyonder.co.uk>
| Date: Mon, 30 Jan 2006 01:31:09 GMT
| NNTP-Posting-Host: 82.42.42.142
| X-Complaints-To: abuse@.blueyonder.co.uk
| X-Trace: text.news.blueyonder.co.uk 1138584669 82.42.42.142 (Mon, 30 Jan
2006 01:31:09 GMT)
| NNTP-Posting-Date: Mon, 30 Jan 2006 01:31:09 GMT
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsfe
ed01.sul.t-online.de!t-online.de!solnet.ch!solnet.ch!newsfeed.freenet.de!bor
der2.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!p
e2.news.blueyonder.co.uk!blueyonder!pe1.news.blueyonder.co.uk!blueyonder!tex
t.news.blueyonder.co.uk!53ab2750!not-for-mail
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.connect:46765
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Hi there michael,
| If your connecting fine to the database and it accepts data exchange,
| perhaps you might look at the database permissions. Rather than any more
| ports.
|
| Opening 1433 within the firewall as far as im aware, is all you need for
| admin.
|
| Give the test account full sysadmin rights, and try that.
|
| regards..
|
| "michael" <howlinghound@.nospam.nospam> wrote in message
| news:601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com...
| > After a little searching, I thought that simple enabling port 1433 on
the
| > server machine's fire wall would do the trick. It does allow connection
to
| > the server for data exchange but it does not allow remote
administration
| > via
| > the SQL Server Management Studio. What additional port need to be
opened
| > to
| > allow this?
| >
| > --
| > Michael Hockstein
| >
| >
| > "Roger Wolter[MSFT]" wrote:
| >
| >> Did you also enable and start the sqlbrowser service?
| >>
| >> --
| >> This posting is provided "AS IS" with no warranties, and confers no
| >> rights.
| >> Use of included script samples are subject to the terms specified at
| >> http://www.microsoft.com/info/cpyright.htm
| >>
| >> "michael" <howlinghound@.nospam.nospam> wrote in message
| >> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
| >> > I'm running the Develpers version of SQL Server 2005 on my developer
| >> > machine.
| >> > I want to test an application from another machine but can neither
log
| >> > on
| >> > nor
| >> > use the SQL Server Management Studio from the remote machine unless
I
| >> > turn
| >> > off the Windows Firewall on the development machine. (I made sure to
| >> > enable
| >> > remote connections via the Surface Configuration Tool too).
| >> >
| >> > Though I seem to have the correct services listed in the
"Exclusions"
| >> > of
| >> > the
| >> > Windows Firewall, I think that I should probably explicitly open the
| >> > ports
| >> > that SQL Server and the Management Studio use. What are the correct
| >> > ports
| >> > or
| >> > is there a better way to work through the Windows Firewall. (This
| >> > problem
| >> > should only exist in my development environment because I would not
use
| >> > the
| >> > Windows Firewall in a production setting on the Server)
| >> >
| >> >
| >> > --
| >> > Michael Hockstein
| >>
| >>
| >>
|
|
||||I meant is sqlbrowser enabled through the firewall.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"michael" <howlinghound@.nospam.nospam> wrote in message
news:D7E1B295-425A-47F9-9B9F-7E439508C1A9@.microsoft.com...[vbcol=seagreen]
> Yes it is enabled and running. I can establish connections if I disable
> the
> Windows Firewall on the machine with the SQL Server instance.
> --
> Michael Hockstein
>
> "Roger Wolter[MSFT]" wrote:
>|||That's the trick! Enable the SQL Browser and Port 1433 in the Windows
Firewall and you get both connectivity and the ability to remotely
administer. Thanks!
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> I meant is sqlbrowser enabled through the firewall.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:D7E1B295-425A-47F9-9B9F-7E439508C1A9@.microsoft.com...
>
>
.
I want to test an application from another machine but can neither log on no
r
use the SQL Server Management Studio from the remote machine unless I turn
off the Windows Firewall on the development machine. (I made sure to enable
remote connections via the Surface Configuration Tool too).
Though I seem to have the correct services listed in the "Exclusions" of the
Windows Firewall, I think that I should probably explicitly open the ports
that SQL Server and the Management Studio use. What are the correct ports or
is there a better way to work through the Windows Firewall. (This problem
should only exist in my development environment because I would not use the
Windows Firewall in a production setting on the Server)
Michael HocksteinDid you also enable and start the sqlbrowser service?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"michael" <howlinghound@.nospam.nospam> wrote in message
news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
> I'm running the Develpers version of SQL Server 2005 on my developer
> machine.
> I want to test an application from another machine but can neither log on
> nor
> use the SQL Server Management Studio from the remote machine unless I turn
> off the Windows Firewall on the development machine. (I made sure to
> enable
> remote connections via the Surface Configuration Tool too).
> Though I seem to have the correct services listed in the "Exclusions" of
> the
> Windows Firewall, I think that I should probably explicitly open the ports
> that SQL Server and the Management Studio use. What are the correct ports
> or
> is there a better way to work through the Windows Firewall. (This problem
> should only exist in my development environment because I would not use
> the
> Windows Firewall in a production setting on the Server)
>
> --
> Michael Hockstein|||Yes it is enabled and running. I can establish connections if I disable the
Windows Firewall on the machine with the SQL Server instance.
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> Did you also enable and start the sqlbrowser service?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
>
>|||After a little searching, I thought that simple enabling port 1433 on the
server machine's fire wall would do the trick. It does allow connection to
the server for data exchange but it does not allow remote administration via
the SQL Server Management Studio. What additional port need to be opened to
allow this?
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> Did you also enable and start the sqlbrowser service?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
>
>|||Hi there michael,
If your connecting fine to the database and it accepts data exchange,
perhaps you might look at the database permissions. Rather than any more
ports.
Opening 1433 within the firewall as far as im aware, is all you need for
admin.
Give the test account full sysadmin rights, and try that.
regards..
"michael" <howlinghound@.nospam.nospam> wrote in message
news:601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com...[vbcol=seagreen]
> After a little searching, I thought that simple enabling port 1433 on the
> server machine's fire wall would do the trick. It does allow connection to
> the server for data exchange but it does not allow remote administration
> via
> the SQL Server Management Studio. What additional port need to be opened
> to
> allow this?
> --
> Michael Hockstein
>
> "Roger Wolter[MSFT]" wrote:
>|||Hi Michael,
As Grumpy has mentioned, generally 1433 port is enough for connecting to
SQL server database engine. Also, for 2005, you can also try opening the
1434 UDP port since it will be used for establishing linked connection from
other applications. See the following article which describes the
"Connecting SQL Server over internet...":
Connecting to SQL Server over the Internet
http://msdn2.microsoft.com/en-us/library/ms175483.aspx
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "grumpy" <dtREMOVE2k@.blueTHISyonder.co.uk>
| Newsgroups: microsoft.public.sqlserver.connect
| References: <171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com>
<#imE4XEJGHA.3904@.TK2MSFTNGP10.phx.gbl>
<601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com>
| Subject: Re: Ports to open in Windows Firewall for SQL Server 2005
| Lines: 71
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <x%dDf.11677$wl.6669@.text.news.blueyonder.co.uk>
| Date: Mon, 30 Jan 2006 01:31:09 GMT
| NNTP-Posting-Host: 82.42.42.142
| X-Complaints-To: abuse@.blueyonder.co.uk
| X-Trace: text.news.blueyonder.co.uk 1138584669 82.42.42.142 (Mon, 30 Jan
2006 01:31:09 GMT)
| NNTP-Posting-Date: Mon, 30 Jan 2006 01:31:09 GMT
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsfe
ed01.sul.t-online.de!t-online.de!solnet.ch!solnet.ch!newsfeed.freenet.de!bor
der2.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!p
e2.news.blueyonder.co.uk!blueyonder!pe1.news.blueyonder.co.uk!blueyonder!tex
t.news.blueyonder.co.uk!53ab2750!not-for-mail
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.connect:46765
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Hi there michael,
| If your connecting fine to the database and it accepts data exchange,
| perhaps you might look at the database permissions. Rather than any more
| ports.
|
| Opening 1433 within the firewall as far as im aware, is all you need for
| admin.
|
| Give the test account full sysadmin rights, and try that.
|
| regards..
|
| "michael" <howlinghound@.nospam.nospam> wrote in message
| news:601836B2-038B-47C1-B1D5-99230963883A@.microsoft.com...
| > After a little searching, I thought that simple enabling port 1433 on
the
| > server machine's fire wall would do the trick. It does allow connection
to
| > the server for data exchange but it does not allow remote
administration
| > via
| > the SQL Server Management Studio. What additional port need to be
opened
| > to
| > allow this?
| >
| > --
| > Michael Hockstein
| >
| >
| > "Roger Wolter[MSFT]" wrote:
| >
| >> Did you also enable and start the sqlbrowser service?
| >>
| >> --
| >> This posting is provided "AS IS" with no warranties, and confers no
| >> rights.
| >> Use of included script samples are subject to the terms specified at
| >> http://www.microsoft.com/info/cpyright.htm
| >>
| >> "michael" <howlinghound@.nospam.nospam> wrote in message
| >> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@.microsoft.com...
| >> > I'm running the Develpers version of SQL Server 2005 on my developer
| >> > machine.
| >> > I want to test an application from another machine but can neither
log
| >> > on
| >> > nor
| >> > use the SQL Server Management Studio from the remote machine unless
I
| >> > turn
| >> > off the Windows Firewall on the development machine. (I made sure to
| >> > enable
| >> > remote connections via the Surface Configuration Tool too).
| >> >
| >> > Though I seem to have the correct services listed in the
"Exclusions"
| >> > of
| >> > the
| >> > Windows Firewall, I think that I should probably explicitly open the
| >> > ports
| >> > that SQL Server and the Management Studio use. What are the correct
| >> > ports
| >> > or
| >> > is there a better way to work through the Windows Firewall. (This
| >> > problem
| >> > should only exist in my development environment because I would not
use
| >> > the
| >> > Windows Firewall in a production setting on the Server)
| >> >
| >> >
| >> > --
| >> > Michael Hockstein
| >>
| >>
| >>
|
|
||||I meant is sqlbrowser enabled through the firewall.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"michael" <howlinghound@.nospam.nospam> wrote in message
news:D7E1B295-425A-47F9-9B9F-7E439508C1A9@.microsoft.com...[vbcol=seagreen]
> Yes it is enabled and running. I can establish connections if I disable
> the
> Windows Firewall on the machine with the SQL Server instance.
> --
> Michael Hockstein
>
> "Roger Wolter[MSFT]" wrote:
>|||That's the trick! Enable the SQL Browser and Port 1433 in the Windows
Firewall and you get both connectivity and the ability to remotely
administer. Thanks!
Michael Hockstein
"Roger Wolter[MSFT]" wrote:
> I meant is sqlbrowser enabled through the firewall.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:D7E1B295-425A-47F9-9B9F-7E439508C1A9@.microsoft.com...
>
>
Ports reported as servers via SQLDMO
Does anyone know how to get SQLDMO not to interpret ports
as server instances? I presume this is due to named
pipes being turned off on these servers.
SQLDMO.NameList sqlServers = sqlApp.ListAvailableSQLServers();
This misbehaves for a SQL Server named instance that is
specified as "somewhere.domain.net, 1433".
The ListAvailableSQLServers() method comes back with...
"somewhere.domain.net"
"1433"
Any suggestions?The method ListAvailableSQLServers() is practically
useless. What are you trying to accomplish?
Linchi
>--Original Message--
>Does anyone know how to get SQLDMO not to interpret ports
>as server instances? I presume this is due to named
>pipes being turned off on these servers.
>SQLDMO.NameList sqlServers =>sqlApp.ListAvailableSQLServers();
>This misbehaves for a SQL Server named instance that is
>specified as "somewhere.domain.net, 1433".
>The ListAvailableSQLServers() method comes back with...
>"somewhere.domain.net"
>"1433"
>Any suggestions?
>.
>|||I have an application that needs to support a
configuration module. The module needs to provide an
administrator of the app to select a SQL Server instance
to which to bind for all data access. This app will
roam -- that is, travel on laptops and be run from
various states. SQL Server instances will also come and
go over time, so I do not want to store this info in any
config files. I need dynamic scanning of the network for
exposed instances so that the admin can select the
desired one.
ListAvailableSQLServers() does do that for me, but it
looks like it uses dbnetlib.dll whereas I need it to use
dbmssocn.dll in order to detect TCP/IP connections.|||You know that ListAvailableSQLServers() sees only those servers that are
being broadcast. If all your SQL instances happen to be detectable that way,
lucky you! That's not common in most bigger environments.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Martin Douglas" <martin_douglas@.fsafood.com> wrote in message
news:033f01c3a002$5a16ac80$a401280a@.phx.gbl...
> I have an application that needs to support a
> configuration module. The module needs to provide an
> administrator of the app to select a SQL Server instance
> to which to bind for all data access. This app will
> roam -- that is, travel on laptops and be run from
> various states. SQL Server instances will also come and
> go over time, so I do not want to store this info in any
> config files. I need dynamic scanning of the network for
> exposed instances so that the admin can select the
> desired one.
> ListAvailableSQLServers() does do that for me, but it
> looks like it uses dbnetlib.dll whereas I need it to use
> dbmssocn.dll in order to detect TCP/IP connections.
>|||1433 can show up because you have an alias configured with that name on the
machine you are running from, or there is garbage in the Registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib,
which is effectively what get enumerated.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2003 All rights reserved.
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:uZqtJMDoDHA.964@.TK2MSFTNGP10.phx.gbl...
> You know that ListAvailableSQLServers() sees only those servers that are
> being broadcast. If all your SQL instances happen to be detectable that
way,
> lucky you! That's not common in most bigger environments.
> --
> Linchi Shea
> linchi_shea@.NOSPAMml.com
>
> "Martin Douglas" <martin_douglas@.fsafood.com> wrote in message
> news:033f01c3a002$5a16ac80$a401280a@.phx.gbl...
> > I have an application that needs to support a
> > configuration module. The module needs to provide an
> > administrator of the app to select a SQL Server instance
> > to which to bind for all data access. This app will
> > roam -- that is, travel on laptops and be run from
> > various states. SQL Server instances will also come and
> > go over time, so I do not want to store this info in any
> > config files. I need dynamic scanning of the network for
> > exposed instances so that the admin can select the
> > desired one.
> >
> > ListAvailableSQLServers() does do that for me, but it
> > looks like it uses dbnetlib.dll whereas I need it to use
> > dbmssocn.dll in order to detect TCP/IP connections.
> >
>
as server instances? I presume this is due to named
pipes being turned off on these servers.
SQLDMO.NameList sqlServers = sqlApp.ListAvailableSQLServers();
This misbehaves for a SQL Server named instance that is
specified as "somewhere.domain.net, 1433".
The ListAvailableSQLServers() method comes back with...
"somewhere.domain.net"
"1433"
Any suggestions?The method ListAvailableSQLServers() is practically
useless. What are you trying to accomplish?
Linchi
>--Original Message--
>Does anyone know how to get SQLDMO not to interpret ports
>as server instances? I presume this is due to named
>pipes being turned off on these servers.
>SQLDMO.NameList sqlServers =>sqlApp.ListAvailableSQLServers();
>This misbehaves for a SQL Server named instance that is
>specified as "somewhere.domain.net, 1433".
>The ListAvailableSQLServers() method comes back with...
>"somewhere.domain.net"
>"1433"
>Any suggestions?
>.
>|||I have an application that needs to support a
configuration module. The module needs to provide an
administrator of the app to select a SQL Server instance
to which to bind for all data access. This app will
roam -- that is, travel on laptops and be run from
various states. SQL Server instances will also come and
go over time, so I do not want to store this info in any
config files. I need dynamic scanning of the network for
exposed instances so that the admin can select the
desired one.
ListAvailableSQLServers() does do that for me, but it
looks like it uses dbnetlib.dll whereas I need it to use
dbmssocn.dll in order to detect TCP/IP connections.|||You know that ListAvailableSQLServers() sees only those servers that are
being broadcast. If all your SQL instances happen to be detectable that way,
lucky you! That's not common in most bigger environments.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Martin Douglas" <martin_douglas@.fsafood.com> wrote in message
news:033f01c3a002$5a16ac80$a401280a@.phx.gbl...
> I have an application that needs to support a
> configuration module. The module needs to provide an
> administrator of the app to select a SQL Server instance
> to which to bind for all data access. This app will
> roam -- that is, travel on laptops and be run from
> various states. SQL Server instances will also come and
> go over time, so I do not want to store this info in any
> config files. I need dynamic scanning of the network for
> exposed instances so that the admin can select the
> desired one.
> ListAvailableSQLServers() does do that for me, but it
> looks like it uses dbnetlib.dll whereas I need it to use
> dbmssocn.dll in order to detect TCP/IP connections.
>|||1433 can show up because you have an alias configured with that name on the
machine you are running from, or there is garbage in the Registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib,
which is effectively what get enumerated.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2003 All rights reserved.
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:uZqtJMDoDHA.964@.TK2MSFTNGP10.phx.gbl...
> You know that ListAvailableSQLServers() sees only those servers that are
> being broadcast. If all your SQL instances happen to be detectable that
way,
> lucky you! That's not common in most bigger environments.
> --
> Linchi Shea
> linchi_shea@.NOSPAMml.com
>
> "Martin Douglas" <martin_douglas@.fsafood.com> wrote in message
> news:033f01c3a002$5a16ac80$a401280a@.phx.gbl...
> > I have an application that needs to support a
> > configuration module. The module needs to provide an
> > administrator of the app to select a SQL Server instance
> > to which to bind for all data access. This app will
> > roam -- that is, travel on laptops and be run from
> > various states. SQL Server instances will also come and
> > go over time, so I do not want to store this info in any
> > config files. I need dynamic scanning of the network for
> > exposed instances so that the admin can select the
> > desired one.
> >
> > ListAvailableSQLServers() does do that for me, but it
> > looks like it uses dbnetlib.dll whereas I need it to use
> > dbmssocn.dll in order to detect TCP/IP connections.
> >
>
Ports for Repication
Hi,
I want to set up a transactional replication between 2 sqlserver2000
databases.
Can anybody say me the ports I need for the replication.
Tanks
Jeanette
for ftp its 21 and 1433
for unc its 137 and 1433
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Jeanette" <needmoreinfo@.gmx.de> wrote in message
news:%23xqxOQWdEHA.3796@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I want to set up a transactional replication between 2 sqlserver2000
> databases.
> Can anybody say me the ports I need for the replication.
> Tanks
> Jeanette
>
|||However,does 1433 hold if you are not using 1433 as the
normal listening port for SQL Server? I somehow doubt it.
|||good point. I guess I should have said
for ftp its 21 and whatever port SQL Server communicates on, the default is
1433
for unc its 137 and whatever port SQL Server communicates on, the default is
1433
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
news:697c01c47577$67ab63e0$a501280a@.phx.gbl...
> However,does 1433 hold if you are not using 1433 as the
> normal listening port for SQL Server? I somehow doubt it.
>
|||Thanks for your help.
but now I have another problem. What can be the mistake when my Server is
not listening on the port 1433?
Thanks
Jeanette
"Hilary Cotter" <hilaryk@.att.net> schrieb im Newsbeitrag
news:uFLNhZYdEHA.712@.TK2MSFTNGP09.phx.gbl...
> good point. I guess I should have said
> for ftp its 21 and whatever port SQL Server communicates on, the default
is
> 1433
> for unc its 137 and whatever port SQL Server communicates on, the default
is
> 1433
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
> news:697c01c47577$67ab63e0$a501280a@.phx.gbl...
>
|||Open the "SQL Server network utility"
Add TCP/IP to the enabled protocols, and edit it to set the listening port.
Restart SQL Server.
"Jeanette" wrote:
> Thanks for your help.
> but now I have another problem. What can be the mistake when my Server is
> not listening on the port 1433?
> Thanks
> Jeanette
>
> "Hilary Cotter" <hilaryk@.att.net> schrieb im Newsbeitrag
> news:uFLNhZYdEHA.712@.TK2MSFTNGP09.phx.gbl...
> is
> is
>
>
I want to set up a transactional replication between 2 sqlserver2000
databases.
Can anybody say me the ports I need for the replication.
Tanks
Jeanette
for ftp its 21 and 1433
for unc its 137 and 1433
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Jeanette" <needmoreinfo@.gmx.de> wrote in message
news:%23xqxOQWdEHA.3796@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I want to set up a transactional replication between 2 sqlserver2000
> databases.
> Can anybody say me the ports I need for the replication.
> Tanks
> Jeanette
>
|||However,does 1433 hold if you are not using 1433 as the
normal listening port for SQL Server? I somehow doubt it.
|||good point. I guess I should have said
for ftp its 21 and whatever port SQL Server communicates on, the default is
1433
for unc its 137 and whatever port SQL Server communicates on, the default is
1433
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
news:697c01c47577$67ab63e0$a501280a@.phx.gbl...
> However,does 1433 hold if you are not using 1433 as the
> normal listening port for SQL Server? I somehow doubt it.
>
|||Thanks for your help.
but now I have another problem. What can be the mistake when my Server is
not listening on the port 1433?
Thanks
Jeanette
"Hilary Cotter" <hilaryk@.att.net> schrieb im Newsbeitrag
news:uFLNhZYdEHA.712@.TK2MSFTNGP09.phx.gbl...
> good point. I guess I should have said
> for ftp its 21 and whatever port SQL Server communicates on, the default
is
> 1433
> for unc its 137 and whatever port SQL Server communicates on, the default
is
> 1433
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
> news:697c01c47577$67ab63e0$a501280a@.phx.gbl...
>
|||Open the "SQL Server network utility"
Add TCP/IP to the enabled protocols, and edit it to set the listening port.
Restart SQL Server.
"Jeanette" wrote:
> Thanks for your help.
> but now I have another problem. What can be the mistake when my Server is
> not listening on the port 1433?
> Thanks
> Jeanette
>
> "Hilary Cotter" <hilaryk@.att.net> schrieb im Newsbeitrag
> news:uFLNhZYdEHA.712@.TK2MSFTNGP09.phx.gbl...
> is
> is
>
>
Ports and Replication in SQL Server 2000
Hi,
We are trying to configure sql server 2000 transactional replication across
2 data centres through vpn and firewall. While port 1433 is open for sql
server communication, it looks like the anonymous pull subscription uses a
different port to download the initial snapshot files.
We are not using FTP to download the snapshot files, bu the option to find
the snapshot files in the default folder.
We would like to know which port that the replication agent uses to download
the snapshot files to be opened? Can this port be configured to a fixed
unused port and how? Is FTP the best way for this scenarion?
Thanks for your help and time.
Vivek
If you don't use FTP SQL will download the snapshot from the default folder
which is usually a shared folder (NETBIOS).
I don't know the ports you have to open to make that works... but you
certainly don't want to do that...
I think you should activate the FTP server in your internal network (ie:
using the VPN) and make the subscribers download the snapshots from there.
Jos.
"vivek" <vivek@.discussions.microsoft.com> wrote in message
news:9F8EF204-2EB0-489C-AF3C-4D12B4BCEC59@.microsoft.com...
> Hi,
> We are trying to configure sql server 2000 transactional replication
across
> 2 data centres through vpn and firewall. While port 1433 is open for sql
> server communication, it looks like the anonymous pull subscription uses a
> different port to download the initial snapshot files.
> We are not using FTP to download the snapshot files, bu the option to find
> the snapshot files in the default folder.
> We would like to know which port that the replication agent uses to
download
> the snapshot files to be opened? Can this port be configured to a fixed
> unused port and how? Is FTP the best way for this scenarion?
> Thanks for your help and time.
> Vivek
We are trying to configure sql server 2000 transactional replication across
2 data centres through vpn and firewall. While port 1433 is open for sql
server communication, it looks like the anonymous pull subscription uses a
different port to download the initial snapshot files.
We are not using FTP to download the snapshot files, bu the option to find
the snapshot files in the default folder.
We would like to know which port that the replication agent uses to download
the snapshot files to be opened? Can this port be configured to a fixed
unused port and how? Is FTP the best way for this scenarion?
Thanks for your help and time.
Vivek
If you don't use FTP SQL will download the snapshot from the default folder
which is usually a shared folder (NETBIOS).
I don't know the ports you have to open to make that works... but you
certainly don't want to do that...
I think you should activate the FTP server in your internal network (ie:
using the VPN) and make the subscribers download the snapshots from there.
Jos.
"vivek" <vivek@.discussions.microsoft.com> wrote in message
news:9F8EF204-2EB0-489C-AF3C-4D12B4BCEC59@.microsoft.com...
> Hi,
> We are trying to configure sql server 2000 transactional replication
across
> 2 data centres through vpn and firewall. While port 1433 is open for sql
> server communication, it looks like the anonymous pull subscription uses a
> different port to download the initial snapshot files.
> We are not using FTP to download the snapshot files, bu the option to find
> the snapshot files in the default folder.
> We would like to know which port that the replication agent uses to
download
> the snapshot files to be opened? Can this port be configured to a fixed
> unused port and how? Is FTP the best way for this scenarion?
> Thanks for your help and time.
> Vivek
Ports And Protocols
Hi Folks ,
Got one for you ....
By default what ports and protocols do the following sql tools use...?
Enterprise Manager
SQL Query Analyser
SQL Profiler
And if anybody knows :
Performance Monitor
Mapping drives
Event Viewer
User/Server Manager
Any help would be greatly appreciated ....Do you mean TCP/IP ports and protocols?
Microsoft SQL uses port 1433 for the default instance, and 1434 for named instances. It uses the TDS protocol.
The other tools use a mish-mash of ports and protocols, but I'd start with port 135.
-PatP
Got one for you ....
By default what ports and protocols do the following sql tools use...?
Enterprise Manager
SQL Query Analyser
SQL Profiler
And if anybody knows :
Performance Monitor
Mapping drives
Event Viewer
User/Server Manager
Any help would be greatly appreciated ....Do you mean TCP/IP ports and protocols?
Microsoft SQL uses port 1433 for the default instance, and 1434 for named instances. It uses the TDS protocol.
The other tools use a mish-mash of ports and protocols, but I'd start with port 135.
-PatP
Ports
I hope this is okay, but I'm reposting this here as I
didn't get any response in the Security forum:
"I need to find out what tcp ports Sql Server 2000 needs.
1433 is the standard network-accessed port, right? And
isn't it 80 that the web comes through?
The reason I'm asking is because our security group came
by and showed me a list of ports mapped from our web
servers through the firewall to various of my production
sql servers. Furthermore, they know that none of these
ports has had any traffic in the last three months. So of
course they would like to close these access holes up
since they're not being used.
Most of these dead ports are 1433 which is incorrect
right? i.e. the web would not generally directly hit 1433
to access Sql Server? Plus isn't that a security risk?
I also see 1100, 1199, 7050 mapped in? Those aren't
standard ports used for anything Sql Server related,
right?"
replies in-line
"Cal" <anonymous@.discussions.microsoft.com> wrote in message
news:6e9e01c4ccc9$c6d001b0$a601280a@.phx.gbl...
> I hope this is okay, but I'm reposting this here as I
> didn't get any response in the Security forum:
> "I need to find out what tcp ports Sql Server 2000 needs.
> 1433 is the standard network-accessed port, right? And
> isn't it 80 that the web comes through?
Yes to both questions...
> The reason I'm asking is because our security group came
> by and showed me a list of ports mapped from our web
> servers through the firewall to various of my production
> sql servers. Furthermore, they know that none of these
> ports has had any traffic in the last three months. So of
> course they would like to close these access holes up
> since they're not being used.
> Most of these dead ports are 1433 which is incorrect
> right? i.e. the web would not generally directly hit 1433
> to access Sql Server? Plus isn't that a security risk?
The server listens on port 1433 and responds on a random port within a given
range.
> I also see 1100, 1199, 7050 mapped in? Those aren't
> standard ports used for anything Sql Server related,
> right?"
I can't answer what those specific ports are being used for, other utilities
can answer that...
for a better explanation of how SQL Server manages those ports see:
http://support.microsoft.com/kb/q287932/
Steve
didn't get any response in the Security forum:
"I need to find out what tcp ports Sql Server 2000 needs.
1433 is the standard network-accessed port, right? And
isn't it 80 that the web comes through?
The reason I'm asking is because our security group came
by and showed me a list of ports mapped from our web
servers through the firewall to various of my production
sql servers. Furthermore, they know that none of these
ports has had any traffic in the last three months. So of
course they would like to close these access holes up
since they're not being used.
Most of these dead ports are 1433 which is incorrect
right? i.e. the web would not generally directly hit 1433
to access Sql Server? Plus isn't that a security risk?
I also see 1100, 1199, 7050 mapped in? Those aren't
standard ports used for anything Sql Server related,
right?"
replies in-line
"Cal" <anonymous@.discussions.microsoft.com> wrote in message
news:6e9e01c4ccc9$c6d001b0$a601280a@.phx.gbl...
> I hope this is okay, but I'm reposting this here as I
> didn't get any response in the Security forum:
> "I need to find out what tcp ports Sql Server 2000 needs.
> 1433 is the standard network-accessed port, right? And
> isn't it 80 that the web comes through?
Yes to both questions...
> The reason I'm asking is because our security group came
> by and showed me a list of ports mapped from our web
> servers through the firewall to various of my production
> sql servers. Furthermore, they know that none of these
> ports has had any traffic in the last three months. So of
> course they would like to close these access holes up
> since they're not being used.
> Most of these dead ports are 1433 which is incorrect
> right? i.e. the web would not generally directly hit 1433
> to access Sql Server? Plus isn't that a security risk?
The server listens on port 1433 and responds on a random port within a given
range.
> I also see 1100, 1199, 7050 mapped in? Those aren't
> standard ports used for anything Sql Server related,
> right?"
I can't answer what those specific ports are being used for, other utilities
can answer that...
for a better explanation of how SQL Server manages those ports see:
http://support.microsoft.com/kb/q287932/
Steve
Ports
What ports would I need to open for a web server in a DMZ to communicate
with an internal SQL server?
Peter,
If it is a standard install you would need to open TCP port 1433 (the
default instance) and/or UDP port 1434 on the same ip if you have any apps
that Sql needs to listen for. If Sql is a named instance the port is
dynamically assigned when the instance is first started unless you set an
alternate port during setup. You can also configure/customize these values
using the Client Network Utility.
Hope this helps.
|||Thanks for the advice!
"Brian Brown" <BrianBrown@.discussions.microsoft.com> wrote in message
news:74EABE7C-8E6B-4467-8728-6BEC92BF678E@.microsoft.com...
> Peter,
> If it is a standard install you would need to open TCP port 1433 (the
> default instance) and/or UDP port 1434 on the same ip if you have any apps
> that Sql needs to listen for. If Sql is a named instance the port is
> dynamically assigned when the instance is first started unless you set an
> alternate port during setup. You can also configure/customize these
values
> using the Client Network Utility.
> Hope this helps.
with an internal SQL server?
Peter,
If it is a standard install you would need to open TCP port 1433 (the
default instance) and/or UDP port 1434 on the same ip if you have any apps
that Sql needs to listen for. If Sql is a named instance the port is
dynamically assigned when the instance is first started unless you set an
alternate port during setup. You can also configure/customize these values
using the Client Network Utility.
Hope this helps.
|||Thanks for the advice!
"Brian Brown" <BrianBrown@.discussions.microsoft.com> wrote in message
news:74EABE7C-8E6B-4467-8728-6BEC92BF678E@.microsoft.com...
> Peter,
> If it is a standard install you would need to open TCP port 1433 (the
> default instance) and/or UDP port 1434 on the same ip if you have any apps
> that Sql needs to listen for. If Sql is a named instance the port is
> dynamically assigned when the instance is first started unless you set an
> alternate port during setup. You can also configure/customize these
values
> using the Client Network Utility.
> Hope this helps.
Ports
When replicating between 2 sql 2000 databases, what port is used? Is it
1433?
Best regards
TrondSQL Server uses
port 1433 for TCP and port 1434 forUDP
best Regards,
Chandra
http://chanduas.blogspot.com/
---
"Trond" wrote:
> When replicating between 2 sql 2000 databases, what port is used? Is it
> 1433?
> Best regards
> Trond
>
>
1433?
Best regards
TrondSQL Server uses
port 1433 for TCP and port 1434 forUDP
best Regards,
Chandra
http://chanduas.blogspot.com/
---
"Trond" wrote:
> When replicating between 2 sql 2000 databases, what port is used? Is it
> 1433?
> Best regards
> Trond
>
>
Ports
I hope this is okay, but I'm reposting this here as I
didn't get any response in the Security forum:
"I need to find out what tcp ports Sql Server 2000 needs.
1433 is the standard network-accessed port, right? And
isn't it 80 that the web comes through?
The reason I'm asking is because our security group came
by and showed me a list of ports mapped from our web
servers through the firewall to various of my production
sql servers. Furthermore, they know that none of these
ports has had any traffic in the last three months. So of
course they would like to close these access holes up
since they're not being used.
Most of these dead ports are 1433 which is incorrect
right? i.e. the web would not generally directly hit 1433
to access Sql Server? Plus isn't that a security risk?
I also see 1100, 1199, 7050 mapped in? Those aren't
standard ports used for anything Sql Server related,
right?"replies in-line
"Cal" <anonymous@.discussions.microsoft.com> wrote in message
news:6e9e01c4ccc9$c6d001b0$a601280a@.phx.gbl...
> I hope this is okay, but I'm reposting this here as I
> didn't get any response in the Security forum:
> "I need to find out what tcp ports Sql Server 2000 needs.
> 1433 is the standard network-accessed port, right? And
> isn't it 80 that the web comes through?
Yes to both questions...
> The reason I'm asking is because our security group came
> by and showed me a list of ports mapped from our web
> servers through the firewall to various of my production
> sql servers. Furthermore, they know that none of these
> ports has had any traffic in the last three months. So of
> course they would like to close these access holes up
> since they're not being used.
> Most of these dead ports are 1433 which is incorrect
> right? i.e. the web would not generally directly hit 1433
> to access Sql Server? Plus isn't that a security risk?
The server listens on port 1433 and responds on a random port within a given
range.
> I also see 1100, 1199, 7050 mapped in? Those aren't
> standard ports used for anything Sql Server related,
> right?"
I can't answer what those specific ports are being used for, other utilities
can answer that...
for a better explanation of how SQL Server manages those ports see:
http://support.microsoft.com/kb/q287932/
Steve
didn't get any response in the Security forum:
"I need to find out what tcp ports Sql Server 2000 needs.
1433 is the standard network-accessed port, right? And
isn't it 80 that the web comes through?
The reason I'm asking is because our security group came
by and showed me a list of ports mapped from our web
servers through the firewall to various of my production
sql servers. Furthermore, they know that none of these
ports has had any traffic in the last three months. So of
course they would like to close these access holes up
since they're not being used.
Most of these dead ports are 1433 which is incorrect
right? i.e. the web would not generally directly hit 1433
to access Sql Server? Plus isn't that a security risk?
I also see 1100, 1199, 7050 mapped in? Those aren't
standard ports used for anything Sql Server related,
right?"replies in-line
"Cal" <anonymous@.discussions.microsoft.com> wrote in message
news:6e9e01c4ccc9$c6d001b0$a601280a@.phx.gbl...
> I hope this is okay, but I'm reposting this here as I
> didn't get any response in the Security forum:
> "I need to find out what tcp ports Sql Server 2000 needs.
> 1433 is the standard network-accessed port, right? And
> isn't it 80 that the web comes through?
Yes to both questions...
> The reason I'm asking is because our security group came
> by and showed me a list of ports mapped from our web
> servers through the firewall to various of my production
> sql servers. Furthermore, they know that none of these
> ports has had any traffic in the last three months. So of
> course they would like to close these access holes up
> since they're not being used.
> Most of these dead ports are 1433 which is incorrect
> right? i.e. the web would not generally directly hit 1433
> to access Sql Server? Plus isn't that a security risk?
The server listens on port 1433 and responds on a random port within a given
range.
> I also see 1100, 1199, 7050 mapped in? Those aren't
> standard ports used for anything Sql Server related,
> right?"
I can't answer what those specific ports are being used for, other utilities
can answer that...
for a better explanation of how SQL Server manages those ports see:
http://support.microsoft.com/kb/q287932/
Steve
Ports
I hope this is okay, but I'm reposting this here as I
didn't get any response in the Security forum:
"I need to find out what tcp ports Sql Server 2000 needs.
1433 is the standard network-accessed port, right? And
isn't it 80 that the web comes through?
The reason I'm asking is because our security group came
by and showed me a list of ports mapped from our web
servers through the firewall to various of my production
sql servers. Furthermore, they know that none of these
ports has had any traffic in the last three months. So of
course they would like to close these access holes up
since they're not being used.
Most of these dead ports are 1433 which is incorrect
right? i.e. the web would not generally directly hit 1433
to access Sql Server? Plus isn't that a security risk?
I also see 1100, 1199, 7050 mapped in? Those aren't
standard ports used for anything Sql Server related,
right?"replies in-line
"Cal" <anonymous@.discussions.microsoft.com> wrote in message
news:6e9e01c4ccc9$c6d001b0$a601280a@.phx.gbl...
> I hope this is okay, but I'm reposting this here as I
> didn't get any response in the Security forum:
> "I need to find out what tcp ports Sql Server 2000 needs.
> 1433 is the standard network-accessed port, right? And
> isn't it 80 that the web comes through?
Yes to both questions...
> The reason I'm asking is because our security group came
> by and showed me a list of ports mapped from our web
> servers through the firewall to various of my production
> sql servers. Furthermore, they know that none of these
> ports has had any traffic in the last three months. So of
> course they would like to close these access holes up
> since they're not being used.
> Most of these dead ports are 1433 which is incorrect
> right? i.e. the web would not generally directly hit 1433
> to access Sql Server? Plus isn't that a security risk?
The server listens on port 1433 and responds on a random port within a given
range.
> I also see 1100, 1199, 7050 mapped in? Those aren't
> standard ports used for anything Sql Server related,
> right?"
I can't answer what those specific ports are being used for, other utilities
can answer that...
for a better explanation of how SQL Server manages those ports see:
http://support.microsoft.com/kb/q287932/
Steve
didn't get any response in the Security forum:
"I need to find out what tcp ports Sql Server 2000 needs.
1433 is the standard network-accessed port, right? And
isn't it 80 that the web comes through?
The reason I'm asking is because our security group came
by and showed me a list of ports mapped from our web
servers through the firewall to various of my production
sql servers. Furthermore, they know that none of these
ports has had any traffic in the last three months. So of
course they would like to close these access holes up
since they're not being used.
Most of these dead ports are 1433 which is incorrect
right? i.e. the web would not generally directly hit 1433
to access Sql Server? Plus isn't that a security risk?
I also see 1100, 1199, 7050 mapped in? Those aren't
standard ports used for anything Sql Server related,
right?"replies in-line
"Cal" <anonymous@.discussions.microsoft.com> wrote in message
news:6e9e01c4ccc9$c6d001b0$a601280a@.phx.gbl...
> I hope this is okay, but I'm reposting this here as I
> didn't get any response in the Security forum:
> "I need to find out what tcp ports Sql Server 2000 needs.
> 1433 is the standard network-accessed port, right? And
> isn't it 80 that the web comes through?
Yes to both questions...
> The reason I'm asking is because our security group came
> by and showed me a list of ports mapped from our web
> servers through the firewall to various of my production
> sql servers. Furthermore, they know that none of these
> ports has had any traffic in the last three months. So of
> course they would like to close these access holes up
> since they're not being used.
> Most of these dead ports are 1433 which is incorrect
> right? i.e. the web would not generally directly hit 1433
> to access Sql Server? Plus isn't that a security risk?
The server listens on port 1433 and responds on a random port within a given
range.
> I also see 1100, 1199, 7050 mapped in? Those aren't
> standard ports used for anything Sql Server related,
> right?"
I can't answer what those specific ports are being used for, other utilities
can answer that...
for a better explanation of how SQL Server manages those ports see:
http://support.microsoft.com/kb/q287932/
Steve
Ports
Hi
I have a SQL Server 2000 system with two instances. The
non-default instance needs to use port 1433, but the
default instance is using that one. Anyone know how to
change the ports the instances are using?
JoeUse the Server Network Utility, select the instance then
select the TCP/IP protocol and select properties. You can
set the ports from here.
-Sue
On Tue, 18 Nov 2003 07:43:56 -0800, "Joe"
<anonymous@.discussions.microsoft.com> wrote:
>Hi
>I have a SQL Server 2000 system with two instances. The
>non-default instance needs to use port 1433, but the
>default instance is using that one. Anyone know how to
>change the ports the instances are using?
>Joe|||In case your instances are running in a Microsoft server
cluster, both instances can listen on the same port since
they'll be using two different IP addresses.
Linchi
>--Original Message--
>Hi
>I have a SQL Server 2000 system with two instances. The
>non-default instance needs to use port 1433, but the
>default instance is using that one. Anyone know how to
>change the ports the instances are using?
>Joe
>.
>
I have a SQL Server 2000 system with two instances. The
non-default instance needs to use port 1433, but the
default instance is using that one. Anyone know how to
change the ports the instances are using?
JoeUse the Server Network Utility, select the instance then
select the TCP/IP protocol and select properties. You can
set the ports from here.
-Sue
On Tue, 18 Nov 2003 07:43:56 -0800, "Joe"
<anonymous@.discussions.microsoft.com> wrote:
>Hi
>I have a SQL Server 2000 system with two instances. The
>non-default instance needs to use port 1433, but the
>default instance is using that one. Anyone know how to
>change the ports the instances are using?
>Joe|||In case your instances are running in a Microsoft server
cluster, both instances can listen on the same port since
they'll be using two different IP addresses.
Linchi
>--Original Message--
>Hi
>I have a SQL Server 2000 system with two instances. The
>non-default instance needs to use port 1433, but the
>default instance is using that one. Anyone know how to
>change the ports the instances are using?
>Joe
>.
>
Subscribe to:
Posts (Atom)