|
Home > Archive > SQL Server Connection > April 2004 > URGENT: MSDE TCP Problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
URGENT: MSDE TCP Problem
|
|
| Snehal Tiwari 2004-04-27, 6:34 am |
| I have installed MSDE 2000 on an XP Prof. box. I am able to connet to
this instance locally from the server, but when i try to connect to it
from other machines, i get an error stating
Server does not exist or access denied
I have traced this problem to msde not listening on port 1433 on my
server machine.
I have inspected the 'Server Error Log' and it says
SQL server listening on Shared Memory, Named Pipes.
What i know is TCP should be listed here, but problem is how do i get
it listed?
I have installed client tools from the sql server CD and using the
'Client Network Utility' i have enabled TCP/IP and Named Pipes
protocols. The port listed for TCP is 1433.
Using PortQry tool i have also checked that no other application has
taken up the 1433 port. I dont get any error during msde startup that
port is unavailable.
I dont seem to understand why msde is not listening on TCP 1433. Any
ideas on how i can force it to do that.
Thanking in advance for your inputs
Snehal
| |
| Sue Hoegemeier 2004-04-27, 9:35 am |
| You need to enable TCP/IP on the server end, not just the
client. You can use the server network utility,
svrnetcn.exe.
The utility can be found in the Tools\Binn directory of your
installation path.
-Sue
On 27 Apr 2004 03:33:06 -0700, snehaltiwari@yahoo.com
(Snehal Tiwari) wrote:
>I have installed MSDE 2000 on an XP Prof. box. I am able to connet to
>this instance locally from the server, but when i try to connect to it
>from other machines, i get an error stating
>
>Server does not exist or access denied
>
>I have traced this problem to msde not listening on port 1433 on my
>server machine.
>I have inspected the 'Server Error Log' and it says
>
>SQL server listening on Shared Memory, Named Pipes.
>
>What i know is TCP should be listed here, but problem is how do i get
>it listed?
>
>I have installed client tools from the sql server CD and using the
>'Client Network Utility' i have enabled TCP/IP and Named Pipes
>protocols. The port listed for TCP is 1433.
>
>Using PortQry tool i have also checked that no other application has
>taken up the 1433 port. I dont get any error during msde startup that
>port is unavailable.
>
>I dont seem to understand why msde is not listening on TCP 1433. Any
>ideas on how i can force it to do that.
>
>Thanking in advance for your inputs
>Snehal
| |
| Rand Boyd [MSFT] 2004-04-27, 9:35 am |
| Go to Start - Run and type in svrnetcn. This will bring up the Server
Network Utility. Verify that TCP/IP is enabled. If it does not launch this
way, search the computer for svrnetcn.exe.
Rand
This posting is provided "as is" with no warranties and confers no rights.
| |
| Snehal Tiwari 2004-04-28, 2:34 am |
| Thanks for your help Rand & Sue
I did forget to mention in my post yesterday that i had already
enabled TCP using 'Server Network Utility'.
Here is what i did:
1) TCP was enabled on server to listen on port 1433 (but TCP did not
start)
log says
SQL server listening on Shared Memory, Named Pipes.
Client unable to connect
2) Changed the TCP port to 0 & restarted MSDE (TCP started)
log says
SQL server listening on 192.168.1.81:1204, 127.0.0.1:1204.
SQL server listening on TCP, Shared Memory, Named Pipes.
Client unable to connect
3) Changed the TCP port to 1433 again & restarted MSDE (TCP started)
log says
SQL server listening on 192.168.1.81:1433, 127.0.0.1:1433.
SQL server listening on TCP, Shared Memory, Named Pipes.
Client able to connect
This is quite strange but working for me now.
|
|
|
|
|