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
>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
[quoted text clipped - 11 lines]
>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?
Rogers - 30 May 2007 14:59 GMT
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
> Try using the client network utility, create an alias using
> TCP/IP and use the IP address for the server, uncheck the
[quoted text clipped - 19 lines]
>>me
>>an error for 1433 port, can you guide me?
mrdenny - 30 May 2007 20:13 GMT
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.

Signature
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)
> 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
[quoted text clipped - 29 lines]
> >>me
> >>an error for 1433 port, can you guide me?