 | |
Please advice
microsoft.public.sqlserver.clients microsoft.public.sqlserver.clients
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Re: Please advice -
09-05-2007
, 11:40 PM
|
I assume you are talking about a connection string like the following: "data source = <sql_server_computer_name\instance_name>; initial catalog = database_name>; uid =<some_username>; pwd = <some_password>" - Are you working in a domain? - Are your clients and your SQL Server in the same domain? - Can they resolve their names? (How about DNS?) If all of them are in a domain and every component are able to resolve others' names then use my sample connection string. And of course then you better use "integrated security = yes" instead of the "uid and pwd" This is the recommended method to use a system by Microsoft. -- Ekrem Önsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:%23fWEi6J8HHA.5316 (AT) TK2MSFTNGP04 (DOT) phx.gbl... Hi Ekrem, In the webserver (connection string) I am using IPAddress\Instance and in that box I don't have SQL Server 2005 "SQL Native Client Configuration" installed, any idea how I can resolve this IpAddress\Instance name? Thanks "Ekrem Önsoy" <ekrem (AT) btegitim (DOT) com> wrote in message news:2CEF3095-6465-4F8E-ABFB-A9CBAB6A1FEF (AT) microsoft (DOT) com... First of all, be sure that you and ping that machine and then be sure that it can ping yours. Then: You should use Aliases instead of using IP addresses. You can create an alias for a server from SQL Server Configuration Manager. Go to "SQL Native Client Configuration" node and expand it. On the "Aliases" right click and "New Alias...". Give it a new, a port number, select TCP\IP as protocol and type remote server's IP address into the Address editbox. And then go to your SSMS and type "<alias_name>\instance_name" and connect. -- Ekrem Önsoy "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:u9ZnlOA8HHA.5752 (AT) TK2MSFTNGP04 (DOT) phx.gbl... Thanks for your reply but quick question again for u When I try to connect from Microsoft SQL Server Management Studio remotely through ServerName\InstanceName it works perfacly fine but when I try to connect through IPAddress\InstanceName didn't work and if I try to connect locally through IPAddress\InstanceName it works so remote connectevety issue... any idea? "Ekrem Önsoy" <ekrem (AT) btegitim (DOT) com> wrote in message news:CD7E1583-74AA-4B14-9A8B-7169D13DD597 (AT) microsoft (DOT) com... Hello Rogers, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Surface Area Configuration. Select your instance and expand it. Go to Remote Connections and check it out if TCP\IP is selected. After that, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Configuration Manager. Expand SQL Server 2005 Network Configuration. Select your instance and from the right pane, make sure TCP\IP is enabled and configure it from its properties to make your SQL Server to be connectable by your client application or whatever. -- Ekrem Önsoy "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:envxKN%237HHA.5404 (AT) TK2MSFTNGP02 (DOT) phx.gbl... I can't connect from client to Server. Here is the Server configuration Settings:- sp_configure Min Max Config Run allow updates 0 1 0 0 clr enabled 0 1 0 0 cross db ownership chaining 0 1 0 0 default language 0 9999 0 0 max text repl size (B) 0 2147483647 65536 65536 nested triggers 0 1 1 1 remote access 0 1 1 1 remote admin connections 0 1 1 1 remote login timeout (s) 0 2147483647 20 20 remote proc trans 0 1 0 0 remote query timeout (s) 0 2147483647 600 600 server trigger recursion 0 1 1 1 show advanced options 0 1 0 0 user options 0 32767 0 0 select @@version Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) Please advice |
#2
| |||
| |||
|
|
Have you tried connecting to your SQL Server by using "ip_address\instance_name" in the connection string? Try and let me know the result. But first be sure that you can ping to SQL Server from your remote machine and vice versa. -- Ekrem Önsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:Our6ESK8HHA.3624 (AT) TK2MSFTNGP05 (DOT) phx.gbl... No, webserver and database server are not in the domain, but they resolve their names through the local IP address. Thanks Noor "Ekrem Önsoy" <ekrem (AT) btegitim (DOT) com> wrote in message news:98BD217F-2A4E-4078-8338-02264F82E127 (AT) microsoft (DOT) com... I assume you are talking about a connection string like the following: "data source = <sql_server_computer_name\instance_name>; initial catalog = <database_name>; uid =<some_username>; pwd = <some_password>" - Are you working in a domain? - Are your clients and your SQL Server in the same domain? - Can they resolve their names? (How about DNS?) If all of them are in a domain and every component are able to resolve others' names then use my sample connection string. And of course then you better use "integrated security = yes" instead of the "uid and pwd" This is the recommended method to use a system by Microsoft. -- Ekrem Önsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:%23fWEi6J8HHA.5316 (AT) TK2MSFTNGP04 (DOT) phx.gbl... Hi Ekrem, In the webserver (connection string) I am using IPAddress\Instance and in that box I don't have SQL Server 2005 "SQL Native Client Configuration" installed, any idea how I can resolve this IpAddress\Instance name? Thanks "Ekrem Önsoy" <ekrem (AT) btegitim (DOT) com> wrote in message news:2CEF3095-6465-4F8E-ABFB-A9CBAB6A1FEF (AT) microsoft (DOT) com... First of all, be sure that you and ping that machine and then be sure that it can ping yours. Then: You should use Aliases instead of using IP addresses. You can create an alias for a server from SQL Server Configuration Manager. Go to "SQL Native Client Configuration" node and expand it. On the "Aliases" right click and "New Alias...". Give it a new, a port number, select TCP\IP as protocol and type remote server's IP address into the Address editbox. And then go to your SSMS and type "<alias_name>\instance_name" and connect. -- Ekrem Önsoy "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:u9ZnlOA8HHA.5752 (AT) TK2MSFTNGP04 (DOT) phx.gbl... Thanks for your reply but quick question again for u When I try to connect from Microsoft SQL Server Management Studio remotely through ServerName\InstanceName it works perfacly fine but when I try to connect through IPAddress\InstanceName didn't work and if I try to connect locally through IPAddress\InstanceName it works so remote connectevety issue... any idea? "Ekrem Önsoy" <ekrem (AT) btegitim (DOT) com> wrote in message news:CD7E1583-74AA-4B14-9A8B-7169D13DD597 (AT) microsoft (DOT) com... Hello Rogers, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Surface Area Configuration. Select your instance and expand it. Go to Remote Connections and check it out if TCP\IP is selected. After that, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Configuration Manager. Expand SQL Server 2005 Network Configuration. Select your instance and from the right pane, make sure TCP\IP is enabled and configure it from its properties to make your SQL Server to be connectable by your client application or whatever. -- Ekrem Önsoy "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:envxKN%237HHA.5404 (AT) TK2MSFTNGP02 (DOT) phx.gbl... I can't connect from client to Server. Here is the Server configuration Settings:- sp_configure Min Max Config Run allow updates 0 1 0 0 clr enabled 0 1 0 0 cross db ownership chaining 0 1 0 0 default language 0 9999 0 0 max text repl size (B) 0 2147483647 65536 65536 nested triggers 0 1 1 1 remote access 0 1 1 1 remote admin connections 0 1 1 1 remote login timeout (s) 0 2147483647 20 20 remote proc trans 0 1 0 0 remote query timeout (s) 0 2147483647 600 600 server trigger recursion 0 1 1 1 show advanced options 0 1 0 0 user options 0 32767 0 0 select @@version Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) Please advice |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Hello Rogers, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Surface Area Configuration. Select your instance and expand it. Go to Remote Connections and check it out if TCP\IP is selected. After that, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Configuration Manager. Expand SQL Server 2005 Network Configuration. Select your instance and from the right pane, make sure TCP\IP is enabled and configure it from its properties to make your SQL Server to be connectable by your client application or whatever. -- Ekrem Önsoy "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:envxKN%237HHA.5404 (AT) TK2MSFTNGP02 (DOT) phx.gbl... I can't connect from client to Server. Here is the Server configuration Settings:- sp_configure Min Max Config Run allow updates 0 1 0 0 clr enabled 0 1 0 0 cross db ownership chaining 0 1 0 0 default language 0 9999 0 0 max text repl size (B) 0 2147483647 65536 65536 nested triggers 0 1 1 1 remote access 0 1 1 1 remote admin connections 0 1 1 1 remote login timeout (s) 0 2147483647 20 20 remote proc trans 0 1 0 0 remote query timeout (s) 0 2147483647 600 600 server trigger recursion 0 1 1 1 show advanced options 0 1 0 0 user options 0 32767 0 0 select @@version Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) Please advice |
#5
| |||
| |||
|
|
First of all, be sure that you and ping that machine and then be sure that it can ping yours. Then: You should use Aliases instead of using IP addresses. You can create an alias for a server from SQL Server Configuration Manager. Go to "SQL Native Client Configuration" node and expand it. On the "Aliases" right click and "New Alias...". Give it a new, a port number, select TCP\IP as protocol and type remote server's IP address into the Address editbox. And then go to your SSMS and type "<alias_name>\instance_name" and connect. -- Ekrem Önsoy "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:u9ZnlOA8HHA.5752 (AT) TK2MSFTNGP04 (DOT) phx.gbl... Thanks for your reply but quick question again for u When I try to connect from Microsoft SQL Server Management Studio remotely through ServerName\InstanceName it works perfacly fine but when I try to connect through IPAddress\InstanceName didn't work and if I try to connect locally through IPAddress\InstanceName it works so remote connectevety issue... any idea? "Ekrem Önsoy" <ekrem (AT) btegitim (DOT) com> wrote in message news:CD7E1583-74AA-4B14-9A8B-7169D13DD597 (AT) microsoft (DOT) com... Hello Rogers, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Surface Area Configuration. Select your instance and expand it. Go to Remote Connections and check it out if TCP\IP is selected. After that, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Configuration Manager. Expand SQL Server 2005 Network Configuration. Select your instance and from the right pane, make sure TCP\IP is enabled and configure it from its properties to make your SQL Server to be connectable by your client application or whatever. -- Ekrem Önsoy "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:envxKN%237HHA.5404 (AT) TK2MSFTNGP02 (DOT) phx.gbl... I can't connect from client to Server. Here is the Server configuration Settings:- sp_configure Min Max Config Run allow updates 0 1 0 0 clr enabled 0 1 0 0 cross db ownership chaining 0 1 0 0 default language 0 9999 0 0 max text repl size (B) 0 2147483647 65536 65536 nested triggers 0 1 1 1 remote access 0 1 1 1 remote admin connections 0 1 1 1 remote login timeout (s) 0 2147483647 20 20 remote proc trans 0 1 0 0 remote query timeout (s) 0 2147483647 600 600 server trigger recursion 0 1 1 1 show advanced options 0 1 0 0 user options 0 32767 0 0 select @@version Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) Please advice |
#6
| |||
| |||
|
|
First of all, be sure that you and ping that machine and then be sure that it can ping yours. Then: You should use Aliases instead of using IP addresses. You can create an alias for a server from SQL Server Configuration Manager. Go to "SQL Native Client Configuration" node and expand it. On the "Aliases" right click and "New Alias...". Give it a new, a port number, select TCP\IP as protocol and type remote server's IP address into the Address editbox. And then go to your SSMS and type "<alias_name>\instance_name" and connect. -- Ekrem Önsoy "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:u9ZnlOA8HHA.5752 (AT) TK2MSFTNGP04 (DOT) phx.gbl... Thanks for your reply but quick question again for u When I try to connect from Microsoft SQL Server Management Studio remotely through ServerName\InstanceName it works perfacly fine but when I try to connect through IPAddress\InstanceName didn't work and if I try to connect locally through IPAddress\InstanceName it works so remote connectevety issue... any idea? "Ekrem Önsoy" <ekrem (AT) btegitim (DOT) com> wrote in message news:CD7E1583-74AA-4B14-9A8B-7169D13DD597 (AT) microsoft (DOT) com... Hello Rogers, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Surface Area Configuration. Select your instance and expand it. Go to Remote Connections and check it out if TCP\IP is selected. After that, Go to Start\Programs\Microsoft SQL Server 2005\Configuration Tools\SQL Server Configuration Manager. Expand SQL Server 2005 Network Configuration. Select your instance and from the right pane, make sure TCP\IP is enabled and configure it from its properties to make your SQL Server to be connectable by your client application or whatever. -- Ekrem Önsoy "Rogers" <naissani (AT) hotmail (DOT) com> wrote in message news:envxKN%237HHA.5404 (AT) TK2MSFTNGP02 (DOT) phx.gbl... I can't connect from client to Server. Here is the Server configuration Settings:- sp_configure Min Max Config Run allow updates 0 1 0 0 clr enabled 0 1 0 0 cross db ownership chaining 0 1 0 0 default language 0 9999 0 0 max text repl size (B) 0 2147483647 65536 65536 nested triggers 0 1 1 1 remote access 0 1 1 1 remote admin connections 0 1 1 1 remote login timeout (s) 0 2147483647 20 20 remote proc trans 0 1 0 0 remote query timeout (s) 0 2147483647 600 600 server trigger recursion 0 1 1 1 show advanced options 0 1 0 0 user options 0 32767 0 0 select @@version Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) Please advice |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.