| Groups | Blog | Home |
sql server clients : Please advice
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 [quoted text, click to view] "Rogers" <naissani@hotmail.com> wrote in message
news:envxKN%237HHA.5404@TK2MSFTNGP02.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 > >
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 [quoted text, click to view] "Rogers" <naissani@hotmail.com> wrote in message
news:u9ZnlOA8HHA.5752@TK2MSFTNGP04.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@btegitim.com> wrote in message > news:CD7E1583-74AA-4B14-9A8B-7169D13DD597@microsoft.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@hotmail.com> wrote in message >> news:envxKN%237HHA.5404@TK2MSFTNGP02.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 >>> >>> >> > >
No, webserver and database server are not in the domain, but they resolve
their names through the local IP address. Thanks Noor [quoted text, click to view] "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message news:98BD217F-2A4E-4078-8338-02264F82E127@microsoft.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@hotmail.com> wrote in message > news:%23fWEi6J8HHA.5316@TK2MSFTNGP04.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@btegitim.com> wrote in message >> news:2CEF3095-6465-4F8E-ABFB-A9CBAB6A1FEF@microsoft.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@hotmail.com> wrote in message >>> news:u9ZnlOA8HHA.5752@TK2MSFTNGP04.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@btegitim.com> wrote in message >>>> news:CD7E1583-74AA-4B14-9A8B-7169D13DD597@microsoft.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@hotmail.com> wrote in message >>>>> news:envxKN%237HHA.5404@TK2MSFTNGP02.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 >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> >
Yes, its true and I can ping the remote server.
[quoted text, click to view] "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message news:D28B1AE4-377A-4FCF-8AB9-8F7276C5FE5B@microsoft.com... > 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@hotmail.com> wrote in message > news:Our6ESK8HHA.3624@TK2MSFTNGP05.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@btegitim.com> wrote in message >> news:98BD217F-2A4E-4078-8338-02264F82E127@microsoft.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@hotmail.com> wrote in message >>> news:%23fWEi6J8HHA.5316@TK2MSFTNGP04.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@btegitim.com> wrote in message >>>> news:2CEF3095-6465-4F8E-ABFB-A9CBAB6A1FEF@microsoft.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@hotmail.com> wrote in message >>>>> news:u9ZnlOA8HHA.5752@TK2MSFTNGP04.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@btegitim.com> wrote in message >>>>>> news:CD7E1583-74AA-4B14-9A8B-7169D13DD597@microsoft.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@hotmail.com> wrote in message >>>>>>> news:envxKN%237HHA.5404@TK2MSFTNGP02.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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> >
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
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? [quoted text, click to view] "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message news:CD7E1583-74AA-4B14-9A8B-7169D13DD597@microsoft.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@hotmail.com> wrote in message > news:envxKN%237HHA.5404@TK2MSFTNGP02.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 >> >> >
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 [quoted text, click to view] "Rogers" <naissani@hotmail.com> wrote in message
news:%23fWEi6J8HHA.5316@TK2MSFTNGP04.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@btegitim.com> wrote in message > news:2CEF3095-6465-4F8E-ABFB-A9CBAB6A1FEF@microsoft.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@hotmail.com> wrote in message >> news:u9ZnlOA8HHA.5752@TK2MSFTNGP04.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@btegitim.com> wrote in message >>> news:CD7E1583-74AA-4B14-9A8B-7169D13DD597@microsoft.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@hotmail.com> wrote in message >>>> news:envxKN%237HHA.5404@TK2MSFTNGP02.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 >>>>> >>>>> >>>> >>> >>> >> > >
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 [quoted text, click to view] "Rogers" <naissani@hotmail.com> wrote in message
news:Our6ESK8HHA.3624@TK2MSFTNGP05.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@btegitim.com> wrote in message > news:98BD217F-2A4E-4078-8338-02264F82E127@microsoft.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@hotmail.com> wrote in message >> news:%23fWEi6J8HHA.5316@TK2MSFTNGP04.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@btegitim.com> wrote in message >>> news:2CEF3095-6465-4F8E-ABFB-A9CBAB6A1FEF@microsoft.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@hotmail.com> wrote in message >>>> news:u9ZnlOA8HHA.5752@TK2MSFTNGP04.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@btegitim.com> wrote in message >>>>> news:CD7E1583-74AA-4B14-9A8B-7169D13DD597@microsoft.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@hotmail.com> wrote in message >>>>>> news:envxKN%237HHA.5404@TK2MSFTNGP02.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 >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> > >
Thanks alot but how about Porta Number because on the same Server SQL Server
2000 is also installed and its also registered in SQL Native Client Configuration with 1433 port should I put the same 1433 Port Number for SQL Server 2005? or its dynamic? Thanks [quoted text, click to view] "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message news:2CEF3095-6465-4F8E-ABFB-A9CBAB6A1FEF@microsoft.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@hotmail.com> wrote in message > news:u9ZnlOA8HHA.5752@TK2MSFTNGP04.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@btegitim.com> wrote in message >> news:CD7E1583-74AA-4B14-9A8B-7169D13DD597@microsoft.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@hotmail.com> wrote in message >>> news:envxKN%237HHA.5404@TK2MSFTNGP02.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 >>>> >>>> >>> >> >> >
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 [quoted text, click to view] "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message news:2CEF3095-6465-4F8E-ABFB-A9CBAB6A1FEF@microsoft.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@hotmail.com> wrote in message > news:u9ZnlOA8HHA.5752@TK2MSFTNGP04.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@btegitim.com> wrote in message >> news:CD7E1583-74AA-4B14-9A8B-7169D13DD597@microsoft.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@hotmail.com> wrote in message >>> news:envxKN%237HHA.5404@TK2MSFTNGP02.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 >>>> >>>> >>> >> >> >
Don't see what you're looking for? Try a search.
|
March 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |