Showing posts with label port. Show all posts
Showing posts with label port. Show all posts

Friday, March 23, 2012

How to tell which port

I am having remote server which I cannot log through term
server or any other method so i need to depend on sql
query analyzer to do most things.
I need to determine the port that server is using ?
is there any method to do so within sql query analyzer?
Any thoughts?
apok wrote:
> I am having remote server which I cannot log through term
> server or any other method so i need to depend on sql
> query analyzer to do most things.
> I need to determine the port that server is using ?
> is there any method to do so within sql query analyzer?
> Any thoughts?
If you're using TCP-IP, then the default port is 1433.
David Gugick
Imceda Software
www.imceda.com
|||No but with mutiple instances you dont know which one is
being used so in that case how do know which port is used.
[vbcol=seagreen]
>--Original Message--
>apok wrote:
term
>If you're using TCP-IP, then the default port is 1433.
>--
>David Gugick
>Imceda Software
>www.imceda.com
>.
>
|||Hi
Take a look at SQLPing
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
|||Assuming you haven't cycled your errorlog since the last time you
started SQL server you could parse the errorlog into a tmp table and
grab it from there. Like this:
create table #tmp
(
line varchar(4000),
cont int
)
go
insert into #tmp (line, cont)
exec master.dbo.sp_readerrorlog
go
select line from #tmp
where line like '%SQL Server listening on%'
But that wouldn't work if you'd cycled your errorlog. Another way you
could do it would be to read the reg key it's stored in. Like this:
exec master.dbo.xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\Microsoft SQL Server\<instance
name>\MSSQLServer\SuperSocketNetLib\Tcp',
N'TcpPort'
For a default instance the reg key is different. Don't remember what
exactly, but it's something like this:
exec master.dbo.xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\Microsoft SQL
Server\MSSQL\MSSQLServer\SuperSocketNetLib\Tcp',
N'TcpPort'
However, the xp_regread xproc is undocumented and therefore likely to
changed (and therefore not recommended). In fact Microsoft changed its
behavior slightly in SQL 2000 SP4. Now, you can only read from certain
reg keys (it's a security thing), although these particular ones are OK
(by default). Also, the reg path for the TCP port is different for SQL
2005 so I wouldn't rely on that method too long.
There's a SQLDMO property (Registry2.TcpPort) for getting the port
number a SQL server is listening on. So you could write the query from
a DOS shell in VBScript or JScript or something like that.
HTH.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
apok wrote:
[vbcol=seagreen]
>No but with mutiple instances you dont know which one is
>being used so in that case how do know which port is used.
>
>
>term
>

How to tell which port

I am having remote server which I cannot log through term
server or any other method so i need to depend on sql
query analyzer to do most things.
I need to determine the port that server is using ?
is there any method to do so within sql query analyzer?
Any thoughts?apok wrote:
> I am having remote server which I cannot log through term
> server or any other method so i need to depend on sql
> query analyzer to do most things.
> I need to determine the port that server is using ?
> is there any method to do so within sql query analyzer?
> Any thoughts?
If you're using TCP-IP, then the default port is 1433.
--
David Gugick
Imceda Software
www.imceda.com|||No but with mutiple instances you dont know which one is
being used so in that case how do know which port is used.
>--Original Message--
>apok wrote:
>> I am having remote server which I cannot log through
term
>> server or any other method so i need to depend on sql
>> query analyzer to do most things.
>> I need to determine the port that server is using ?
>> is there any method to do so within sql query analyzer?
>> Any thoughts?
>If you're using TCP-IP, then the default port is 1433.
>--
>David Gugick
>Imceda Software
>www.imceda.com
>.
>|||Hi
Take a look at SQLPing
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John|||This is a multi-part message in MIME format.
--070705010300050106000600
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Assuming you haven't cycled your errorlog since the last time you
started SQL server you could parse the errorlog into a tmp table and
grab it from there. Like this:
create table #tmp
(
line varchar(4000),
cont int
)
go
insert into #tmp (line, cont)
exec master.dbo.sp_readerrorlog
go
select line from #tmp
where line like '%SQL Server listening on%'
But that wouldn't work if you'd cycled your errorlog. Another way you
could do it would be to read the reg key it's stored in. Like this:
exec master.dbo.xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\Microsoft SQL Server\<instance
name>\MSSQLServer\SuperSocketNetLib\Tcp',
N'TcpPort'
For a default instance the reg key is different. Don't remember what
exactly, but it's something like this:
exec master.dbo.xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\Microsoft SQL
Server\MSSQL\MSSQLServer\SuperSocketNetLib\Tcp',
N'TcpPort'
However, the xp_regread xproc is undocumented and therefore likely to
changed (and therefore not recommended). In fact Microsoft changed its
behavior slightly in SQL 2000 SP4. Now, you can only read from certain
reg keys (it's a security thing), although these particular ones are OK
(by default). Also, the reg path for the TCP port is different for SQL
2005 so I wouldn't rely on that method too long.
There's a SQLDMO property (Registry2.TcpPort) for getting the port
number a SQL server is listening on. So you could write the query from
a DOS shell in VBScript or JScript or something like that.
HTH.
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
apok wrote:
>No but with mutiple instances you dont know which one is
>being used so in that case how do know which port is used.
>
>
>>--Original Message--
>>apok wrote:
>>
>>I am having remote server which I cannot log through
>>
>term
>
>>server or any other method so i need to depend on sql
>>query analyzer to do most things.
>>I need to determine the port that server is using ?
>>is there any method to do so within sql query analyzer?
>>Any thoughts?
>>
>>If you're using TCP-IP, then the default port is 1433.
>>--
>>David Gugick
>>Imceda Software
>>www.imceda.com
>>.
>>
--070705010300050106000600
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Assuming you haven't cycled your errorlog since the last time you
started SQL server you could parse the errorlog into a tmp table and
grab it from there. Like this:<br>
<br>
create table #tmp<br>
(<br>
line varchar(4000),<br>
cont int<br>
)<br>
go<br>
<br>
insert into #tmp (line, cont)<br>
exec master.dbo.sp_readerrorlog<br>
go<br>
<br>
select line from #tmp<br>
where line like '%SQL Server listening on%'<br>
<br>
But that wouldn't work if you'd cycled your errorlog. Another way you
could do it would be to read the reg key it's stored in. Like this:<br>
<br>
exec master.dbo.xp_regread<br>
N'HKEY_LOCAL_MACHINE',<br>
N'Software\Microsoft\Microsoft SQL Server\<instance
name>\MSSQLServer\SuperSocketNetLib\Tcp',<br>
N'TcpPort'<br>
<br>
For a default instance the reg key is different. Don't remember what
exactly, but it's something like this:<br>
<br>
exec master.dbo.xp_regread<br>
N'HKEY_LOCAL_MACHINE',<br>
N'Software\Microsoft\Microsoft SQL
Server\MSSQL\MSSQLServer\SuperSocketNetLib\Tcp',<br>
N'TcpPort'<br>
<br>
However, the xp_regread xproc is undocumented and therefore likely to
changed (and therefore not recommended). In fact Microsoft changed its
behavior slightly in SQL 2000 SP4. Now, you can only read from certain
reg keys (it's a security thing), although these particular ones are OK
(by default). Also, the reg path for the TCP port is different for SQL
2005 so I wouldn't rely on that method too long.<br>
<br>
There's a SQLDMO property (Registry2.TcpPort) for getting the port
number a SQL server is listening on. So you could write the query from
a DOS shell in VBScript or JScript or something like that.<br>
<br>
HTH.<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
apok wrote:
<blockquote cite="mid14e901c5196f$2e60d790$a501280a@.phx.gbl" type="cite">
<pre wrap="">No but with mutiple instances you dont know which one is
being used so in that case how do know which port is used.
</pre>
<blockquote type="cite">
<pre wrap="">--Original Message--
apok wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I am having remote server which I cannot log through
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!-->term
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">server or any other method so i need to depend on sql
query analyzer to do most things.
I need to determine the port that server is using ?
is there any method to do so within sql query analyzer?
Any thoughts?
</pre>
</blockquote>
<pre wrap="">If you're using TCP-IP, then the default port is 1433.
--
David Gugick
Imceda Software
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=www.imceda.com</a>">http://www.imceda.com">www.imceda.com</a>
.
</pre>
</blockquote>
</blockquote>
</body>
</html>
--070705010300050106000600--

How to tell which port

I am having remote server which I cannot log through term
server or any other method so i need to depend on sql
query analyzer to do most things.
I need to determine the port that server is using ?
is there any method to do so within sql query analyzer?
Any thoughts?apok wrote:
> I am having remote server which I cannot log through term
> server or any other method so i need to depend on sql
> query analyzer to do most things.
> I need to determine the port that server is using ?
> is there any method to do so within sql query analyzer?
> Any thoughts?
If you're using TCP-IP, then the default port is 1433.
David Gugick
Imceda Software
www.imceda.com|||No but with mutiple instances you dont know which one is
being used so in that case how do know which port is used.

>--Original Message--
>apok wrote:
term[vbcol=seagreen]
>If you're using TCP-IP, then the default port is 1433.
>--
>David Gugick
>Imceda Software
>www.imceda.com
>.
>|||Hi
Take a look at SQLPing
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John|||Assuming you haven't cycled your errorlog since the last time you
started SQL server you could parse the errorlog into a tmp table and
grab it from there. Like this:
create table #tmp
(
line varchar(4000),
cont int
)
go
insert into #tmp (line, cont)
exec master.dbo.sp_readerrorlog
go
select line from #tmp
where line like '%SQL Server listening on%'
But that wouldn't work if you'd cycled your errorlog. Another way you
could do it would be to read the reg key it's stored in. Like this:
exec master.dbo.xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\Microsoft SQL Server\<instance
name>\MSSQLServer\SuperSocketNetLib\Tcp',
N'TcpPort'
For a default instance the reg key is different. Don't remember what
exactly, but it's something like this:
exec master.dbo.xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\Microsoft SQL
Server\MSSQL\MSSQLServer\SuperSocketNetL
ib\Tcp',
N'TcpPort'
However, the xp_regread xproc is undocumented and therefore likely to
changed (and therefore not recommended). In fact Microsoft changed its
behavior slightly in SQL 2000 SP4. Now, you can only read from certain
reg keys (it's a security thing), although these particular ones are OK
(by default). Also, the reg path for the TCP port is different for SQL
2005 so I wouldn't rely on that method too long.
There's a SQLDMO property (Registry2.TcpPort) for getting the port
number a SQL server is listening on. So you could write the query from
a DOS shell in VBScript or JScript or something like that.
HTH.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
apok wrote:
[vbcol=seagreen]
>No but with mutiple instances you dont know which one is
>being used so in that case how do know which port is used.
>
>
>term
>sql

How to tell whether SQL Server is listening on port 1433 and port

If I run netstat -a on a machine with a default instance of SQL Server 2000 and the port has not been changed, should I see port 1433 and port 1434? Does it matter which SQL Server service pack has been applied?
Hi,
The port should be 1433.
You can the see the port SQl Serevr Listening by-
1. Open Server network utility
2. In the enabled protocols -- Select TCP /IP and click properties to get
the PORT number.
Note:
For Default Instance SQL Server listen on port 1433, which is static.
Thanks
Hari
MCDBA
"peter" <peter@.discussions.microsoft.com> wrote in message
news:17C8C6CA-4929-41B8-BA6E-2FEF6AAB91BD@.microsoft.com...
> If I run netstat -a on a machine with a default instance of SQL Server
2000 and the port has not been changed, should I see port 1433 and port
1434? Does it matter which SQL Server service pack has been applied?
>
|||Port 1433 is used by default only for the default (unnamed) instance
of the server. Named instances communicate over random prt numbers
unless you set them for port 1433 using the Server Network Utility.
Look under Program files and run the Svrnetcn.exe file that is in the
SQL Server Tools\Binn folder
See the article:
http://support.microsoft.com/default.aspx?kbid=814130
On Sun, 20 Jun 2004 08:02:18 +0530, "Hari Prasad"
<hari_prasad_k@.hotmail.com> wrote:

>Hi,
>The port should be 1433.
>You can the see the port SQl Serevr Listening by-
>1. Open Server network utility
>2. In the enabled protocols -- Select TCP /IP and click properties to get
>the PORT number.
>--
>Note:
>For Default Instance SQL Server listen on port 1433, which is static.
>Thanks
>Hari
>MCDBA
>
>
>"peter" <peter@.discussions.microsoft.com> wrote in message
>news:17C8C6CA-4929-41B8-BA6E-2FEF6AAB91BD@.microsoft.com...
>2000 and the port has not been changed, should I see port 1433 and port
>1434? Does it matter which SQL Server service pack has been applied?
>

How to tell whether SQL Server is listening on port 1433 and port

If I run netstat -a on a machine with a default instance of SQL Server 2000 and the port has not been changed, should I see port 1433 and port 1434? Does it matter which SQL Server service pack has been applied?Hi,
The port should be 1433.
You can the see the port SQl Serevr Listening by-
1. Open Server network utility
2. In the enabled protocols -- Select TCP /IP and click properties to get
the PORT number.
--
Note:
For Default Instance SQL Server listen on port 1433, which is static.
Thanks
Hari
MCDBA
"peter" <peter@.discussions.microsoft.com> wrote in message
news:17C8C6CA-4929-41B8-BA6E-2FEF6AAB91BD@.microsoft.com...
> If I run netstat -a on a machine with a default instance of SQL Server
2000 and the port has not been changed, should I see port 1433 and port
1434? Does it matter which SQL Server service pack has been applied?
>|||Hi Hari,
I can see port 1433 in the Server Network Utility. But I don't see port 1433 when I run netstat -a to check what port is active. I'm using Windows XP SP2 RC2 and have disabled Windows Firewall.
Thank you for your help,
Peter
"Hari Prasad" wrote:
> Hi,
> The port should be 1433.
> You can the see the port SQl Serevr Listening by-
> 1. Open Server network utility
> 2. In the enabled protocols -- Select TCP /IP and click properties to get
> the PORT number.
> --
> Note:
> For Default Instance SQL Server listen on port 1433, which is static.
> Thanks
> Hari
> MCDBA
>
>
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:17C8C6CA-4929-41B8-BA6E-2FEF6AAB91BD@.microsoft.com...
> > If I run netstat -a on a machine with a default instance of SQL Server
> 2000 and the port has not been changed, should I see port 1433 and port
> 1434? Does it matter which SQL Server service pack has been applied?
> >
> >
>
>|||Hi,
Login to SQL server using a query analyzer window and issue the below
command from command prompt
nbtstat -n
In the local address you iwl be able to see the server ip addree:1433
Otherwise :- , From command prompt Telnet and see whether the port 1433 is
accessible.
TELNET ipaddress 1433
If the port is accessible, automatically the connection will be accessible
else u will get an error.
Thanks
Hari
MCDBA
"peter" <peter@.discussions.microsoft.com> wrote in message
news:142340D1-70EB-4F27-BF82-E2C8ED172081@.microsoft.com...
> Hi Hari,
> I can see port 1433 in the Server Network Utility. But I don't see port
1433 when I run netstat -a to check what port is active. I'm using Windows
XP SP2 RC2 and have disabled Windows Firewall.
> Thank you for your help,
> Peter
> "Hari Prasad" wrote:
> > Hi,
> >
> > The port should be 1433.
> >
> > You can the see the port SQl Serevr Listening by-
> >
> > 1. Open Server network utility
> > 2. In the enabled protocols -- Select TCP /IP and click properties to
get
> > the PORT number.
> >
> > --
> >
> > Note:
> > For Default Instance SQL Server listen on port 1433, which is static.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> >
> > "peter" <peter@.discussions.microsoft.com> wrote in message
> > news:17C8C6CA-4929-41B8-BA6E-2FEF6AAB91BD@.microsoft.com...
> > > If I run netstat -a on a machine with a default instance of SQL Server
> > 2000 and the port has not been changed, should I see port 1433 and port
> > 1434? Does it matter which SQL Server service pack has been applied?
> > >
> > >
> >
> >
> >|||Port 1433 is used by default only for the default (unnamed) instance
of the server. Named instances communicate over random prt numbers
unless you set them for port 1433 using the Server Network Utility.
Look under Program files and run the Svrnetcn.exe file that is in the
SQL Server Tools\Binn folder
See the article:
http://support.microsoft.com/default.aspx?kbid=814130
On Sun, 20 Jun 2004 08:02:18 +0530, "Hari Prasad"
<hari_prasad_k@.hotmail.com> wrote:
>Hi,
>The port should be 1433.
>You can the see the port SQl Serevr Listening by-
>1. Open Server network utility
>2. In the enabled protocols -- Select TCP /IP and click properties to get
>the PORT number.
>--
>Note:
>For Default Instance SQL Server listen on port 1433, which is static.
>Thanks
>Hari
>MCDBA
>
>
>"peter" <peter@.discussions.microsoft.com> wrote in message
>news:17C8C6CA-4929-41B8-BA6E-2FEF6AAB91BD@.microsoft.com...
>> If I run netstat -a on a machine with a default instance of SQL Server
>2000 and the port has not been changed, should I see port 1433 and port
>1434? Does it matter which SQL Server service pack has been applied?
>>
>

How to tell whether SQL Server is listening on port 1433 and port

If I run netstat -a on a machine with a default instance of SQL Server 2000
and the port has not been changed, should I see port 1433 and port 1434? Do
es it matter which SQL Server service pack has been applied?Hi,
The port should be 1433.
You can the see the port SQl Serevr Listening by-
1. Open Server network utility
2. In the enabled protocols -- Select TCP /IP and click properties to get
the PORT number.
Note:
For Default Instance SQL Server listen on port 1433, which is static.
Thanks
Hari
MCDBA
"peter" <peter@.discussions.microsoft.com> wrote in message
news:17C8C6CA-4929-41B8-BA6E-2FEF6AAB91BD@.microsoft.com...
> If I run netstat -a on a machine with a default instance of SQL Server
2000 and the port has not been changed, should I see port 1433 and port
1434? Does it matter which SQL Server service pack has been applied?
>|||Port 1433 is used by default only for the default (unnamed) instance
of the server. Named instances communicate over random prt numbers
unless you set them for port 1433 using the Server Network Utility.
Look under Program files and run the Svrnetcn.exe file that is in the
SQL Server Tools\Binn folder
See the article:
http://support.microsoft.com/default.aspx?kbid=814130
On Sun, 20 Jun 2004 08:02:18 +0530, "Hari Prasad"
<hari_prasad_k@.hotmail.com> wrote:

>Hi,
>The port should be 1433.
>You can the see the port SQl Serevr Listening by-
>1. Open Server network utility
>2. In the enabled protocols -- Select TCP /IP and click properties to get
>the PORT number.
>--
>Note:
>For Default Instance SQL Server listen on port 1433, which is static.
>Thanks
>Hari
>MCDBA
>
>
>"peter" <peter@.discussions.microsoft.com> wrote in message
>news:17C8C6CA-4929-41B8-BA6E-2FEF6AAB91BD@.microsoft.com...
>2000 and the port has not been changed, should I see port 1433 and port
>1434? Does it matter which SQL Server service pack has been applied?
>

How to tell whether SQL Server is listening on port 1433 and p

Hi Hari,
I can see port 1433 in the Server Network Utility. But I don't see port 1433 when I run netstat -a to check what port is active. I'm using Windows XP SP2 RC2 and have disabled Windows Firewall.
Thank you for your help,
Peter
"Hari Prasad" wrote:

> Hi,
> The port should be 1433.
> You can the see the port SQl Serevr Listening by-
> 1. Open Server network utility
> 2. In the enabled protocols -- Select TCP /IP and click properties to get
> the PORT number.
> --
> Note:
> For Default Instance SQL Server listen on port 1433, which is static.
> Thanks
> Hari
> MCDBA
>
>
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:17C8C6CA-4929-41B8-BA6E-2FEF6AAB91BD@.microsoft.com...
> 2000 and the port has not been changed, should I see port 1433 and port
> 1434? Does it matter which SQL Server service pack has been applied?
>
>
Hi,
Login to SQL server using a query analyzer window and issue the below
command from command prompt
nbtstat -n
In the local address you iwl be able to see the server ip addree:1433
Otherwise :- , From command prompt Telnet and see whether the port 1433 is
accessible.
TELNET ipaddress 1433
If the port is accessible, automatically the connection will be accessible
else u will get an error.
Thanks
Hari
MCDBA
"peter" <peter@.discussions.microsoft.com> wrote in message
news:142340D1-70EB-4F27-BF82-E2C8ED172081@.microsoft.com...
> Hi Hari,
> I can see port 1433 in the Server Network Utility. But I don't see port
1433 when I run netstat -a to check what port is active. I'm using Windows
XP SP2 RC2 and have disabled Windows Firewall.[vbcol=seagreen]
> Thank you for your help,
> Peter
> "Hari Prasad" wrote:
get[vbcol=seagreen]
sql