Remote Connection to SQL Server 2005 over Windows Server 2003

Hi Fellows!
I am trying to establish a connection between SQL Server 2005 Server
which is setup on Windows Server 2003 along with Visual Studio 2005.
The problem is that when i try to connect it through management
studio using <servername>/databasename method , i become successfull
and got everything. However , if i use ipaddress scheme like
<ipaddress>/databasename , it failed by saying popular error "Error no
:26 Server is not available , ....." along with description "sqr
server might be need to enable for remote access"
I have checked all the ip configuration and also allowed the port
1433, 1444, 1500 (my own named isntance port) and 1743 (the port i
found from the Log of the server).
now the problem is that i am still unable to connect my client to my
server using ipaddress.
Can somebody sugggest me about this porblem.
i am really greatfull to you for this.
Regards,
UsmanBy <servername>/databasename, I suppose you meant
<servername>\<instancename>. The former should not have worked.
If <servername>\<instancename> works, <ipaddress>\<instancename> should work
too unless (1) <ipaddress> is not really the IP address of the server, (2)
<servername> is resolved by DNS/WINS/Host file to something other than
<ipaddress>, or (3) you have an alias <ipaddress>\<instancename> that points
to a nonexistent/nonactive instance.
BTW, I'm curious as to why you would want to use <ipaddress>\<instancename>?
I don't believe this is a common approach.
Linchi
"gripusa" wrote:
> Hi Fellows!
> I am trying to establish a connection between SQL Server 2005 Server
> which is setup on Windows Server 2003 along with Visual Studio 2005.
> The problem is that when i try to connect it through management
> studio using <servername>/databasename method , i become successfull
> and got everything. However , if i use ipaddress scheme like
> <ipaddress>/databasename , it failed by saying popular error "Error no
> :26 Server is not available , ....." along with description "sqr
> server might be need to enable for remote access"
> I have checked all the ip configuration and also allowed the port
> 1433, 1444, 1500 (my own named isntance port) and 1743 (the port i
> found from the Log of the server).
> now the problem is that i am still unable to connect my client to my
> server using ipaddress.
> Can somebody sugggest me about this porblem.
> i am really greatfull to you for this.
> Regards,
> Usman
>

Remote Connection to SQL Server 2005 on Windows 2003

Hi Fellows!
I am trying to connect a SQL Server 2005 Server setup on Windows Server 2003 and failing. I have checked few other related posts but i think so i am still unable to find the solution.
My configuration and problem is following;
I want to enable access for my SQL Server to my network as well as through internet using our Fix IP address server.
Configurations:
Server: Win XP Server 2003 along with VS 2005 and SQL Server 2005
Clients : WinXP Laptops (home addition) installed SQL Server Connectivity tools and Express addition and also community edition of Management Studio for Express edition.
I am able to connect the server when i try to use my servername but failed when i try to use ipaddress in the connection.
i tired with telnet, the same problem occurs as i can login by using the network machine name but unable to login by using the local or external ip address.
I have checked with my router configuration and i have allowd both the standard ip and the ip i have given to my named instance and also the port which i have seen in the server log , so i am still unable to find why i am not able to connect it.
Can some one will guide me, i will be really thankfull to him.

start>program>microsoft sqlserver 2005>configuration tools>sql server surface area configuration

>configuration for service and connection>remote connections

>check local and remote

>check both tcp/ip and named pipes

|||Thanks for your reply, i tried to use Surface area tool for my client but it is unable to connect to that client. Especially it also becomes difficult when i am gona operate across the network . (Actually server is in our headquarter and client is in other office).|||

hi,

kindly check if port 1433 is left opened in your firewall

regards,

joey

|||

Try adding sqlservr.exe (present in \MSSQL\Binn directory for the default instance and \MSSQL$instance_name\Binn directory for the named instance) in the list of allowed firewall exceptions on the Windows 2003 box.

Regards,

Rajesh

Remote Connection to SQL Server 2005 on Windows 2003

Hi Fellows!
I am trying to connect a SQL Server 2005 Server setup on Windows Server 2003 and failing. I have checked few other related posts but i think so i am still unable to find the solution.
My configuration and problem is following;
I want to enable access for my SQL Server to my network as well as through internet using our Fix IP address server.
Configurations:
Server: Win XP Server 2003 along with VS 2005 and SQL Server 2005
Clients : WinXP Laptops (home addition) installed SQL Server Connectivity tools and Express addition and also community edition of Management Studio for Express edition.
I am able to connect the server when i try to use my servername but failed when i try to use ipaddress in the connection.
i tired with telnet, the same problem occurs as i can login by using the network machine name but unable to login by using the local or external ip address.
I have checked with my router configuration and i have allowd both the standard ip and the ip i have given to my named instance and also the port which i have seen in the server log , so i am still unable to find why i am not able to connect it.
Can some one will guide me, i will be really thankfull to him.

start>program>microsoft sqlserver 2005>configuration tools>sql server surface area configuration

>configuration for service and connection>remote connections

>check local and remote

>check both tcp/ip and named pipes

|||Thanks for your reply, i tried to use Surface area tool for my client but it is unable to connect to that client. Especially it also becomes difficult when i am gona operate across the network . (Actually server is in our headquarter and client is in other office).

|||

hi,

kindly check if port 1433 is left opened in your firewall

regards,

joey

|||

Try adding sqlservr.exe (present in \MSSQL\Binn directory for the default instance and \MSSQL$instance_name\Binn directory for the named instance) in the list of allowed firewall exceptions on the Windows 2003 box.

Regards,

Rajesh