connectivity

dears,
I've installed one sql server instance .
It is connecting through Named pipes only
Through TCP/IP its not connecting.
Only the default instance in the machine is connecting through all
protocols
Why is it like that ?
Please help me...chaluvadi specialists (sanujss@.gmail.com) writes:
> dears,
> I've installed one sql server instance .
> It is connecting through Named pipes only
> Through TCP/IP its not connecting.
> Only the default instance in the machine is connecting through all
> protocols
> Why is it like that ?
> Please help me...
Which versions of SQL Server are the two instances running?
How do you conclude that you cannot connect to the named instance
through TCP/IP?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||> I've installed one sql server instance .
> It is connecting through Named pipes only
> Through TCP/IP its not connecting.
> Only the default instance in the machine is connecting through all
> protocols
Let's get the obvious out of the way:
What is the possibility that there is a firewall between your client and
your server that is blocking TCP:1433?
--
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei

connections remote SQLExpress

how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to 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
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>sqlsql

connections remote SQLExpress

how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
....
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
......
...
thanks
You need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>
|||Since SQL Express installs with a named instance, you also need to 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
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>

connections remote SQLExpress

how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to 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
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>

connections remote SQLExpress

how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
....
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
......
...
thanks
You need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>
|||Since SQL Express installs with a named instance, you also need to 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
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>

connections remote SQLExpress

how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
--
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to 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
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but
>> it does not work.
>>
>> error:
>> ...
>> When connecting to SQL server 2005m this failure may be caused by the
>> fact the under the default settings SQL server does not allow remote
>> connections (provider SQL Network Interfaces, error 26 error, locating
>> server/instance specified).
>> .....
>> ...
>> thanks
>

Connection Timeout

I’ve 2 database servers. These servers communicate with the other’s databases
via TCP/IP with SQL authentication using VB, COM+ & ASP applications. Both
servers are running W2k & SQL2k, each with the latest SPs & hot fixes.
Neither server is a domain server. Server A also supports a VB application
the users access through Terminal Services sessions.
Recently we began experiencing a problem on server A. When logged on to the
server with an administrator account the user can connect to the other
server’s database through the VB applications & through SQL Query Analyzer.
However, when logged on as a user that isn’t an administrator, they cannot
connect to the other server; they get a Timeout Expired error message. This
occurs every time.
From server A when logged on as a standard user we can telnet to server B on
port 1433. We cannot odbcping nor use SQL Query Analyzer to connect to server
B. The IP address & the SQL user /password is included in all connections.
I ran Netmon on server B to see what was coming from server A. I only saw
ack messages. I’m not a Netmon expert, so interpreting these messages is a
little beyond me.
I also suspect the problem is on server A. Why else would one user be able
to connect & another not. Beyond that I’m lost.
The only error I see in any of the Event logs from server A is an error
described by KB 326912.
Thanks in advance for any ideas.
You need to make the connections from the client side and review them. See
if the tcp 3 way handshake is completing.
Q169292 The Basics of Reading TCP/IP Traces
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||I'm able to see a 3 Way Hand Shake & Graceful Close. There is also some Push
activity in the trace.
Examining this activity is iffy at best, because these are production
servers. My problem only occurs when the user on Server A is not an
administrator. Some of the activity in the capture could be the result of
other user activity. I think the trace I captured was during an isolated
period, but I cannot be assured of this. The Hand Shake & Grageful Close were
the 1st & last events in the capture.
"Kevin McDonnell [MSFT]" wrote:

> You need to make the connections from the client side and review them. See
> if the tcp 3 way handshake is completing.
> Q169292 The Basics of Reading TCP/IP Traces
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Is there a policy defined on the system that might explain why there is a
permission problem?
gpresult.exe will show you if any policies are in place.
Are there any security templates in use?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||I'm not aware of a policy that is set to do that.
I ran gpresult without learning much, which didn't surprise me since this is
a stand-alone server.
There are Local Policies, most are default values. I did read through all of
these & nothing stuck out as a possible culprit. Do you have any policies in
mind that may need further scrutiny?
Sam
"Kevin McDonnell [MSFT]" wrote:

> Is there a policy defined on the system that might explain why there is a
> permission problem?
> gpresult.exe will show you if any policies are in place.
> Are there any security templates in use?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Clients need "access this computer from the network" permission in order to
establish a connection.
Can the same client map a drive to the server?
Does the problem happen with Named Pipes as well as TCP/IP?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||I checked the 'Access this computer from the Network' local policy. It
includes Users.
The user connects to Server A through a Terminal Services Connection.
Mapping a drive isn't an option I've pursued.
Since these are standalone servers I don't know how to connect from one to
the other using named pipes. (One is in Atlanta & the other in Washington DC.
They communicate via Internet. Force Encryption is on.) If I enter the
www.servername.com of Server B, I think that uses TCP/IP. I tried it in Query
Analyzer & got the Timeout message.
I installed FileMon from www.SysInternal.com on Server A. I saw some files
that were not found, but the system reverted to Winnt\system32 for the same
files & was succesful. I didn't see any unsuccessful attempts logged for the
User. This leads me to suppose it isn't a file permission problem.
I restarted Server A last night, but this didn't accompolish anything either.
Sam
"Kevin McDonnell [MSFT]" wrote:

> Clients need "access this computer from the network" permission in order to
> establish a connection.
> Can the same client map a drive to the server?
> Does the problem happen with Named Pipes as well as TCP/IP?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||I would run Microsoft Network Monitor from the Terminal Server machine to
trace the traffic to SQL.
Compare the admin trace to the user trace.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||I have the traces. I was able to run them when there wasn't any other
activity between the systems.
Both traces are escentially the the same except in the admin trace I see
more TDS protocol packets. Both start with the 3 Way Hand Shake & end with
the Graceful Close. The 1st 12 packets of each trace are the same. Then the
admin trace has 12 TDS protocol packets with a description beginning with
'UNKNOWN EPM ACK Len ='. The trace that fails does not have any of these
packets.
The user trace does have some TDS protocol packets, but for some reason that
the trace doesn't show, it doesn't continue with the TDS packets the admin
trace has.
Sam
"Kevin McDonnell [MSFT]" wrote:

> I would run Microsoft Network Monitor from the Terminal Server machine to
> trace the traffic to SQL.
> Compare the admin trace to the user trace.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Hi Sam,
Sounds like you made a good capture. Unfortunately, the best way to
resolve this would be to open a case and have a SQL Engineer review the
traces. It would be too difficult to diagnose the traces in this forum.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connection Timeout

I’ve 2 database servers. These servers communicate with the other’s data
bases
via TCP/IP with SQL authentication using VB, COM+ & ASP applications. Both
servers are running W2k & SQL2k, each with the latest SPs & hot fixes.
Neither server is a domain server. Server A also supports a VB application
the users access through Terminal Services sessions.
Recently we began experiencing a problem on server A. When logged on to the
server with an administrator account the user can connect to the other
server’s database through the VB applications & through SQL Query Analyzer
.
However, when logged on as a user that isn’t an administrator, they cannot
connect to the other server; they get a Timeout Expired error message. This
occurs every time.
From server A when logged on as a standard user we can telnet to server B on
port 1433. We cannot odbcping nor use SQL Query Analyzer to connect to serve
r
B. The IP address & the SQL user /password is included in all connections.
I ran Netmon on server B to see what was coming from server A. I only saw
ack messages. I’m not a Netmon expert, so interpreting these messages is a
little beyond me.
I also suspect the problem is on server A. Why else would one user be able
to connect & another not. Beyond that I’m lost.
The only error I see in any of the Event logs from server A is an error
described by KB 326912.
Thanks in advance for any ideas.You need to make the connections from the client side and review them. See
if the tcp 3 way handshake is completing.
Q169292 The Basics of Reading TCP/IP Traces
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I'm able to see a 3 Way Hand Shake & Graceful Close. There is also some Push
activity in the trace.
Examining this activity is iffy at best, because these are production
servers. My problem only occurs when the user on Server A is not an
administrator. Some of the activity in the capture could be the result of
other user activity. I think the trace I captured was during an isolated
period, but I cannot be assured of this. The Hand Shake & Grageful Close wer
e
the 1st & last events in the capture.
"Kevin McDonnell [MSFT]" wrote:

> You need to make the connections from the client side and review them. Se
e
> if the tcp 3 way handshake is completing.
> Q169292 The Basics of Reading TCP/IP Traces
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Is there a policy defined on the system that might explain why there is a
permission problem?
gpresult.exe will show you if any policies are in place.
Are there any security templates in use?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I'm not aware of a policy that is set to do that.
I ran gpresult without learning much, which didn't surprise me since this is
a stand-alone server.
There are Local Policies, most are default values. I did read through all of
these & nothing stuck out as a possible culprit. Do you have any policies in
mind that may need further scrutiny?
Sam
"Kevin McDonnell [MSFT]" wrote:

> Is there a policy defined on the system that might explain why there is a
> permission problem?
> gpresult.exe will show you if any policies are in place.
> Are there any security templates in use?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Clients need "access this computer from the network" permission in order to
establish a connection.
Can the same client map a drive to the server?
Does the problem happen with Named Pipes as well as TCP/IP?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I checked the 'Access this computer from the Network' local policy. It
includes Users.
The user connects to Server A through a Terminal Services Connection.
Mapping a drive isn't an option I've pursued.
Since these are standalone servers I don't know how to connect from one to
the other using named pipes. (One is in Atlanta & the other in Washington DC
.
They communicate via Internet. Force Encryption is on.) If I enter the
www.servername.com of Server B, I think that uses TCP/IP. I tried it in Quer
y
Analyzer & got the Timeout message.
I installed FileMon from www.SysInternal.com on Server A. I saw some files
that were not found, but the system reverted to Winnt\system32 for the same
files & was succesful. I didn't see any unsuccessful attempts logged for the
User. This leads me to suppose it isn't a file permission problem.
I restarted Server A last night, but this didn't accompolish anything either
.
Sam
"Kevin McDonnell [MSFT]" wrote:

> Clients need "access this computer from the network" permission in order t
o
> establish a connection.
> Can the same client map a drive to the server?
> Does the problem happen with Named Pipes as well as TCP/IP?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||I would run Microsoft Network Monitor from the Terminal Server machine to
trace the traffic to SQL.
Compare the admin trace to the user trace.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I have the traces. I was able to run them when there wasn't any other
activity between the systems.
Both traces are escentially the the same except in the admin trace I see
more TDS protocol packets. Both start with the 3 Way Hand Shake & end with
the Graceful Close. The 1st 12 packets of each trace are the same. Then the
admin trace has 12 TDS protocol packets with a description beginning with
'UNKNOWN EPM ACK Len ='. The trace that fails does not have any of these
packets.
The user trace does have some TDS protocol packets, but for some reason that
the trace doesn't show, it doesn't continue with the TDS packets the admin
trace has.
Sam
"Kevin McDonnell [MSFT]" wrote:

> I would run Microsoft Network Monitor from the Terminal Server machine to
> trace the traffic to SQL.
> Compare the admin trace to the user trace.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Hi Sam,
Sounds like you made a good capture. Unfortunately, the best way to
resolve this would be to open a case and have a SQL Engineer review the
traces. It would be too difficult to diagnose the traces in this forum.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

CONNECTION PROBLEM ON WIN2003

hi
i have sqlserver that running on windows 2003
i have connecton to this server from an other computer
and i need tcp/ip connection to this sql server
but i cant connect to this sql with this port
when i use netstat -an i dont see this port(1433) on protocal list and
also
icant telnet to this server with this port
can you tell me how can i solve this problem
* note : tcp/ip protecol is enabled
Is there a firewall between you and the server? If so, make sure port
1433 is open, most firewall setups these days block that port for
security.
|||Perhaps, it is not listening on 1433. Go to the errorlog for the SQL
instance and verify the TCP port it is listening on, or use TcpView.exe from
www.sysinternals.com, though TcpView doesn't always display the port number
of a listening server.
Also from this other computer, to be sure, I'd try (or use whatever the
listening port):
cmd>osql.exe -Stcp:<IP address>,1433 -Uuser -Ppassword
If it doesn't work, remote desktop to the server, and try the above locally.
Linchi
"Savas Ates" <savas@.indexinteractive.com> wrote in message
news:uuP7jp$0FHA.3892@.TK2MSFTNGP12.phx.gbl...
> hi
> i have sqlserver that running on windows 2003
> i have connecton to this server from an other computer
> and i need tcp/ip connection to this sql server
> but i cant connect to this sql with this port
> when i use netstat -an i dont see this port(1433) on protocal list
> and also
> icant telnet to this server with this port
> can you tell me how can i solve this problem
> * note : tcp/ip protecol is enabled
>
>
|||I asked my ISP and they said there is no firewall or blocking on this port..
They also said they cant reach on this port and something wrong with sql
set up.. On my local pc i wrote netstat (there is no problem on my local
sql) i didnt see 1433 port.. Therefore i checked my port number from server
utilities from sql server it was 1433.. What can it be ?
"Savas Ates" <savas@.indexinteractive.com>, haber iletisinde unlar
yazd:uuP7jp$0FHA.3892@.TK2MSFTNGP12.phx.gbl...
> hi
> i have sqlserver that running on windows 2003
> i have connecton to this server from an other computer
> and i need tcp/ip connection to this sql server
> but i cant connect to this sql with this port
> when i use netstat -an i dont see this port(1433) on protocal list
> and also
> icant telnet to this server with this port
> can you tell me how can i solve this problem
> * note : tcp/ip protecol is enabled
>
>

CONNECTION PROBLEM ON WIN2003

hi
i have sqlserver that running on windows 2003
i have connecton to this server from an other computer
and i need tcp/ip connection to this sql server
but i cant connect to this sql with this port
when i use netstat -an i dont see this port(1433) on protocal list and
also
icant telnet to this server with this port
can you tell me how can i solve this problem
* note : tcp/ip protecol is enabledIs there a firewall between you and the server? If so, make sure port
1433 is open, most firewall setups these days block that port for
security.|||Perhaps, it is not listening on 1433. Go to the errorlog for the SQL
instance and verify the TCP port it is listening on, or use TcpView.exe from
www.sysinternals.com, though TcpView doesn't always display the port number
of a listening server.
Also from this other computer, to be sure, I'd try (or use whatever the
listening port):
cmd>osql.exe -Stcp:<IP address>,1433 -Uuser -Ppassword
If it doesn't work, remote desktop to the server, and try the above locally.
Linchi
"Savas Ates" <savas@.indexinteractive.com> wrote in message
news:uuP7jp$0FHA.3892@.TK2MSFTNGP12.phx.gbl...
> hi
> i have sqlserver that running on windows 2003
> i have connecton to this server from an other computer
> and i need tcp/ip connection to this sql server
> but i cant connect to this sql with this port
> when i use netstat -an i dont see this port(1433) on protocal list
> and also
> icant telnet to this server with this port
> can you tell me how can i solve this problem
> * note : tcp/ip protecol is enabled
>
>|||I asked my ISP and they said there is no firewall or blocking on this port..
They also said they cant reach on this port and something wrong with sql
set up.. On my local pc i wrote netstat (there is no problem on my local
sql) i didnt see 1433 port.. Therefore i checked my port number from server
utilities from sql server it was 1433.. What can it be ?
"Savas Ates" <savas@.indexinteractive.com>, haber iletisinde unlar
yazd:uuP7jp$0FHA.3892@.TK2MSFTNGP12.phx.gbl...
> hi
> i have sqlserver that running on windows 2003
> i have connecton to this server from an other computer
> and i need tcp/ip connection to this sql server
> but i cant connect to this sql with this port
> when i use netstat -an i dont see this port(1433) on protocal list
> and also
> icant telnet to this server with this port
> can you tell me how can i solve this problem
> * note : tcp/ip protecol is enabled
>
>