Re: SQL Port issue

Tech-Archive recommends: Fix windows errors by optimizing your registry

If the SQL Servers ERRORLOG file shows that SQL is listening on port 1433 and
you can not access port 1433 on the SQL Server then there is a firewall
blocking the connection somewhere. If you are trying to connect via the
internet (without going through a VPN) then your ISP may be blocking the
connection.
--
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)


"Rogers" wrote:

I did but still it saying SQL Server doesn't exist or access denied, is
there any way I can check why which port is blocking because 3389 is working
fine but only 1433 port is not working, like I mentioned in my earlier email
that I can do Telnet with 3389 but not works through 1433, is there any
diagnosis commands which I can use to figure it out the problem?

I would really appreciate if any one let me know the any helpful idea.

Thanks



"Sue Hoegemeier" <Sue_H@xxxxxxxxxxxxx> wrote in message
news:3cnp53t9lblrgvr69lraeda3s2j81at4e3@xxxxxxxxxx
Try using the client network utility, create an alias using
TCP/IP and use the IP address for the server, uncheck the
dynamically determine port and specify the port SQL Server
is using.

-Sue

On Mon, 28 May 2007 10:43:10 -0400, "Rogers"
<naissani@xxxxxxxxxxx> wrote:

I have Windows 2003 Server and installed SQL Server 2000 Sp 4 behind the
firewall. I open the Portal 3389 TCP, 1433 TCP, 1434 UPD. when I try to
connect SQL Server from my local box it says SQL Server doesn't exists or
access denied.

when I run the following query in my local box.

telnet 201.121.161.82 3389 (the window got clear that means this port is
working fine.)

telnet 201.121.161.82 1433 (Connecting To 201.121.161.82...Could not open
connection to the host, on port 1433: Connect failed)

I am wondering if I open both the port on the Server then why its giving
me
an error for 1433 port, can you guide me?





.

Relevant Pages

  • Re: SQL2005: Cannot connect error 11001
    ... I believe the complete Windows auth user access is too complicate, ... which trusted connection is meant? ... it would still be listening on the old port. ... Microsoft, SQL Server Books Online ...
    (microsoft.public.sqlserver.connect)
  • Re: Installing Sql Server Express on Vista Home Premium
    ... It seems that your SQL Server instances are Named Instances, ... Default Instances uses 1433 TCP port by default as a Static Port but not the ... If you change your Connection String as following, ...
    (microsoft.public.sqlserver.setup)
  • Re: Sql Remote Connection issue
    ... port 1433 TCP Allow ... Copyright 2006 Microsoft Corporation. ... osql does not support all features of SQL Server 2005. ... Sqlcmd: Error: Microsoft SQL Native Client: An error has occurred while establishing a connection to the server. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Server 2005 Connection Problems
    ... - it is't completely clear what the SQL Server Browser is for. ... connection reqest was being rejected. ... I think the problem is still likely the the port is blocked by some ... firewall between the server and that client. ...
    (microsoft.public.sqlserver.setup)
  • Re: Cannot connect to SQL Express on 2003 Machine from XP machine
    ... enable network communication ... make sure that the port isn't blocked ... "An error has occurred while establishing connection to the server. ... When connecting to SQL Server 2005, this failure may be caused by the ...
    (microsoft.public.sqlserver)