Showing posts with label network. Show all posts
Showing posts with label network. Show all posts

Thursday, March 29, 2012

cannot execute xp_cmdshell. Access is denied while copying data over the network

Hi,

I am having some trouble copying data over my workgroup network from my Windows 2003 Server Machine (machineA with SQL SERVER 2005) to one of my network Machine's drive(MachineB).
Here is the T-SQL code that I am trying to execute:

EXEC xp_cmdshell 'copy D:\Data\file.txt \\MachineB\Documents'

Whenever I tried to execute the above piece of code, I get the error message "Access is denied", but if I try to copy the file from the Command Prompt (cmd.exe) with the copy command, the file copies fine over the network.

I have already searched over the internet and I found out that loads of people have the same issue, and they were suggested something like this:
"Check in Services and make sure that the MSSQLServer service is run as a domain user and that domain user has rights to these network resources."

Well it sounds plausible, but I don't know what are the exact steps to do this. How do I know which user is running the MSSQL Server service? Are they referring to the user which I use to connect to my SQL Server Database engine throuhg the SQL Server Management Studio?
Also they are suggesting 'domain user', and as I said before I do not have domain network just regular simple workgroup network.

Here are some details of the user that I use to login. I generally login into my Windows 2003 Server machine with user called 'User1' and I use the same 'User1' to connect to SQL Server through the Management Studio Screen.
Should I create a user called 'User1' on my MachineB(Destination Machine)?

I would really appreciate, if someone can give me detailed steps explaning how to solve this problem.

Thank you very much once again.

Open the Surface Area Configuration Manager. Go to the features section. Make sure that xp_cmdshell is enabled. (It is turned off by default.) Then once you have enabled xp_cmdshell, make sure that the SQL Server service account has the appropriate permissions granted.|||Hi Michael,

Thank you very much for your reply. xp_cmdshell is already enabled. How do I check the permissions of SQL Server Srvice account? Is that the same account which I use to connect to SQL SERVER through Management Studio?

Thanks

|||No. It is the Windows account that the SQL Server service is running under. Specifically, you can find this within SQL Server Configuration Manager.|||

Michael Hotek wrote:

No. It is the Windows account that the SQL Server service is running under. Specifically, you can find this within SQL Server Configuration Manager.

Ok I went to the SQL SERVER Configuration Manager. Then I clicked on SQL SERVER 2005 Services in the left pane. On the right pane, it listen 5-6 services running like Intergration Service, Analysis Service, Reporting Service, and so on. One of them was SQL SERVER(MSSQLSERVER), so I think this must be the one that you were talking about. I right clicked on it-> Properties. Under the properties tab, I saw Log on as: Built-in Account (radio button) was checked and in the dropdown below it, Local System was selected. So basically the SQL Server Service is running under Local System. Now how do I figure out what user is associated with Local System?

Thank you once again for the help.Much appreciated.

|||Local system is the local machine account. That would be why you are getting an access denied on a network resource. The SID for localsystem is not valid external to the machine. In order to be able to execute that command you would need to create a Windows login and then use that login to run the SQL Server services. That login would have to have permissions on the network resource you are trying to write to.|||Thanks a lot Michael, that really makes sense .

Now for the extension based on your reply. Are there any disadvantages of using a Windows user to run the SQL Server services instead of a Local Machine account?

Thank you very very much for your prompt reply and insightful suggestion.

|||No, in fact, there are entire feature sets that you can't use in SQL Server if you are running under the localsystem account, replication being one of them. I don't run any SQL Server under a local machine account. I always run them under specific user accounts and in particular regular domain user accounts.|||I just did this and it worked like a charm. You someone already posted the answer. Go to SQL Server Configuration Manager. Right click on Sql Server, click properties and change the user account to run under a domain or local pc account. that has access to the share.

cannot execute xp_cmdshell. Access is denied while copying data over the network

Hi,

I am having some trouble copying data over my workgroup network from my Windows 2003 Server Machine (machineA with SQL SERVER 2005) to one of my network Machine's drive(MachineB).
Here is the T-SQL code that I am trying to execute:

EXEC xp_cmdshell 'copy D:\Data\file.txt \\MachineB\Documents'

Whenever I tried to execute the above piece of code, I get the error message "Access is denied", but if I try to copy the file from the Command Prompt (cmd.exe) with the copy command, the file copies fine over the network.

I have already searched over the internet and I found out that loads of people have the same issue, and they were suggested something like this:
"Check in Services and make sure that the MSSQLServer service is run as

a domain user and that domain user has rights to these network

resources."

Well it sounds plausible, but I don't know what are the exact steps to do this. How do I know which user is running the MSSQL Server service? Are they referring to the user which I use to connect to my SQL Server Database engine throuhg the SQL Server Management Studio?
Also they are suggesting 'domain user', and as I said before I do not have domain network just regular simple workgroup network.

Here are some details of the user that I use to login. I generally login into my Windows 2003 Server machine with user called 'User1' and I use the same 'User1' to connect to SQL Server through the Management Studio Screen.
Should I create a user called 'User1' on my MachineB(Destination Machine)?

I would really appreciate, if someone can give me detailed steps explaning how to solve this problem.

Thank you very much once again.Open the Surface Area Configuration Manager. Go to the features section. Make sure that xp_cmdshell is enabled. (It is turned off by default.) Then once you have enabled xp_cmdshell, make sure that the SQL Server service account has the appropriate permissions granted.|||Hi Michael,

Thank you very much for your reply. xp_cmdshell is already enabled. How do I check the permissions of SQL Server Srvice account? Is that the same account which I use to connect to SQL SERVER through Management Studio?

Thanks|||No. It is the Windows account that the SQL Server service is running under. Specifically, you can find this within SQL Server Configuration Manager.|||

Michael Hotek wrote:

No. It is the Windows account that the SQL Server service is running under. Specifically, you can find this within SQL Server Configuration Manager.

Ok I went to the SQL SERVER Configuration Manager. Then I clicked on SQL SERVER 2005 Services in the left pane. On the right pane, it listen 5-6 services running like Intergration Service, Analysis Service, Reporting Service, and so on. One of them was SQL SERVER(MSSQLSERVER), so I think this must be the one that you were talking about. I right clicked on it-> Properties. Under the properties tab, I saw Log on as: Built-in Account (radio button) was checked and in the dropdown below it, Local System was selected. So basically the SQL Server Service is running under Local System. Now how do I figure out what user is associated with Local System?

Thank you once again for the help.Much appreciated.|||Local system is the local machine account. That would be why you are getting an access denied on a network resource. The SID for localsystem is not valid external to the machine. In order to be able to execute that command you would need to create a Windows login and then use that login to run the SQL Server services. That login would have to have permissions on the network resource you are trying to write to.|||Thanks a lot Michael, that really makes sense .

Now for the extension based on your reply. Are there any disadvantages of using a Windows user to run the SQL Server services instead of a Local Machine account?

Thank you very very much for your prompt reply and insightful suggestion.|||No, in fact, there are entire feature sets that you can't use in SQL Server if you are running under the localsystem account, replication being one of them. I don't run any SQL Server under a local machine account. I always run them under specific user accounts and in particular regular domain user accounts.|||I just did this and it worked like a charm. You someone already posted the answer. Go to SQL Server Configuration Manager. Right click on Sql Server, click properties and change the user account to run under a domain or local pc account. that has access to the share.

cannot execute xp_cmdshell. Access is denied while copying data over the network

Hi,

I am havingsome trouble copying data over my workgroup network from my Windows2003 Server Machine (machineA with SQL SERVER 2005) to one of mynetwork Machine's drive(MachineB).
Here is the T-SQL code that I am trying to execute:

EXEC xp_cmdshell 'copy D:\Data\file.txt \\MachineB\Documents'

WheneverI tried to execute the above piece of code, I get the error message"Access is denied", but if I try to copy the file from the CommandPrompt (cmd.exe) with the copy command, the file copies fine over thenetwork.

I have already searched over the internet and I foundout that loads of people have the same issue, and they were suggestedsomething like this:
"Check in Services and make sure that the MSSQLServer service is run asa domain user and that domain user has rights to these networkresources."

Wellit sounds plausible, but I don't know what are the exact steps to dothis. How do I know which user is running the MSSQL Server service? Arethey referring to the user which I use to connect to my SQL ServerDatabase engine throuhg the SQL Server Management Studio?
Also they are suggesting 'domain user', and as I said before I do not have domain network just regular simple workgroup network.

Hereare some details of the user that I use to login. I generally logininto my Windows 2003 Server machine with user called 'User1' and I usethe same 'User1' to connect to SQL Server through the Management StudioScreen.
Should I create a user called 'User1' on my MachineB(Destination Machine)?

I would really appreciate, if someone can give me detailed steps explaning how to solve this problem.

Thank you very much once again.Check out the SQL Server Surface Area Configuration under SQL Server 2005 configuration. xp_cmdshell is disabled by default. You need to enable it manually and give permissions.|||

ndinakar:

Check out the SQL Server Surface Area Configuration under SQL Server 2005 configuration. xp_cmdshell is disabled by default. You need to enable it manually and give permissions.

Thank you very much for your reply. xp_cmdshell is already enabled.

|||

modest:

"Check in Services and make sure that the MSSQLServer service is run as a domain user and that domain user has rights to these network resources."

Well it sounds plausible, but I don't know what are the exact steps to do this.

You're on the rigth waySmile goto Start->All Programs->Microsoft SQL Server2005-> Configuration Tools->SQL Server Configuration Manager->SQL Server 2005 Services->locate the service for the SQL2005 instance, should be "SQL Server (InstanceName)"->double click it-> on the Log On tab, you can see the start up account for the service. Just make sure this account has proper permission on the remote resource.

|||Yeah I did that and it says under buit-in account, the user is Local System. Now how do I find out which user is associated with Local System.

Thanks for the reply.|||

modest:

Yeah I did that and it says under buit-in account, the user is Local System. Now how do I find out which user is associated with Local System.

Thanks for the reply.

xp_cmdshell runs with SQL Server Agent permissions Microsoft have finally documented the permission requirements. Try the link below and follow the instructions. Hope this helps.

http://msdn2.microsoft.com/en-us/library/ms175046.aspx

|||

Caddre:

modest:

Yeah I did that and it says under buit-in account, the user is Local System. Now how do I find out which user is associated with Local System.

Thanks for the reply.

xp_cmdshell runs with SQL Server Agent permissions Microsoft have finally documented the permission requirements. Try the link below and follow the instructions. Hope this helps.

http://msdn2.microsoft.com/en-us/library/ms175046.aspx

Well I already have the proxy credential created for the User1 Windows account as I use that credential to execute the dtsRun command from the xp_cmdshell and that runs fine. The problem is when I am trying to copy something over the network. For example I can copy a file within my local machine by using the xp_cmdshell stored procedure, but it won;t work if the destination drive is a network drive.|||That is because you installed SQL Server with the local systems account when you do that and most developers do, SQL Server service and SQL Server Agent are without access to network resources. Try running replication service and you will see what I am talking about. Run a search for local systems account limitations in SQL Server BOL (books online). Hope this helps.|||

Caddre:

That is because you installed SQL Server with the local systems account when you do that and most developers do, SQL Server service and SQL Server Agent are without access to network resources. Try running replication service and you will see what I am talking about. Run a search for local systems account limitations in SQL Server BOL (books online). Hope this helps.

Thanks. Actually I was worried, if changing the startup user for SQLSERVER 2005 will affect my ASP/ASP.NET scripts or for that matter IIS6.0. Will this change be transparent to all the users on the machineand the other machine on my network which connect to the SQL SERVER onmy machine?|||It is not complicated just run full backup of all your databases and rerun setup and make sure you install SQL Server service and SQL Server Agent with two Domain accounts with network permissions. And no it will not affect your application if you do the above because if you run into permissions problem your backup will help if recreate the databases before the changes. But I don't think it will affect anything because you are just giving SQL Server service and the Agent network access. Hope this helps.|||

Caddre:

It is not complicated just run full backup of all your databases and rerun setup and make sure you install SQL Server service and SQL Server Agent with two Domain accounts with network permissions. And no it will not affect your application if you do the above because if you run into permissions problem your backup will help if recreate the databases before the changes. But I don't think it will affect anything because you are just giving SQL Server service and the Agent network access. Hope this helps.

Thanks Caddre very much. I just have one question based on your suggestion. What do you mean by domain accout? Do you mean like actual Domain Network on which my computer is connected? As I said in my first post, we have a workgroup network and not domain network. I know I am confusing with the word Domain. Does domain account mean, a new Windows user that I create on my machine? Or does it mean something lese?

Thank you once again.|||OK my bad create service accounts in your workgroup to run SQL Server service and SQL Server Agent and no you cannot run both on one account because the Agent can do a lot of automation in your application for you so it is good practice to run them on separate accounts. Hope this helps.

Thursday, March 22, 2012

Cannot deploy new report

I been not been uploading any new reports for a while but reporting services is running fine on our network.

I added a new report via Visual studio 2003 today but got the following error when trying to deploy

a connection cannot be made to the report server.

Im not sure if sql server 2000 user has been taken off as I was doing a spring clean and may have remove the vital user. This is just a worry, maybe not true.

What users shoulod I have on SQL server to enable deploying of reports, or has anyone come across this problem?

Many thanks in advance

Scott


If anyone else has this problem, I have figured it out for me..

The SSL needed re-importing. Work fine after this. When importing into IE I allowed the system to decided where to put it rather than selecting myself. Hope that helps anyone else

Scott

sql

Saturday, February 25, 2012

Cannot connect to SQL Servrer 2005 remotely using another account than sa

Hi there,
I set up an SQL Server 2005 Enterprise Edition, so it is listening on
the network.
I can login successfully from a remote machine using osql:
osql -H sqlhost -U sa
Password: XXX
1>
However I created another user "test" (SQL Auth.) and also a database
which test should be allowed to access but test cannot login remotely
(test _can_ login locally, for example in the management studio)
osql -H sqlhost -U test -d db_test
Password: XXX
Login failed for user 'test'.
What is strange about it, is that it doesn't even show up in the logs
that it did not work. There is no mention of the user "test" in the
logs when the remote login fails.
Any idea what to check? What am I doing wrong? :-(
Regards,
marcNote that you should use -S server_name\instance_name.
Perhaps you are connecting to a local instance.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Marc" wrote:
> Hi there,
> I set up an SQL Server 2005 Enterprise Edition, so it is listening on
> the network.
> I can login successfully from a remote machine using osql:
> osql -H sqlhost -U sa
> Password: XXX
> 1>
> However I created another user "test" (SQL Auth.) and also a database
> which test should be allowed to access but test cannot login remotely
> (test _can_ login locally, for example in the management studio)
> osql -H sqlhost -U test -d db_test
> Password: XXX
> Login failed for user 'test'.
> What is strange about it, is that it doesn't even show up in the logs
> that it did not work. There is no mention of the user "test" in the
> logs when the remote login fails.
> Any idea what to check? What am I doing wrong? :-(
> Regards,
> marc
>|||When you are using 'osql -H sqlhost -U sa' without -S you are connecting to
the default instance on the local computer. Try it and run this to verify
select @.@.servername
go
Ben Nevarez, MCDBA, OCP
Database Administrator
"Ben Nevarez" wrote:
> Note that you should use -S server_name\instance_name.
> Perhaps you are connecting to a local instance.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Marc" wrote:
> > Hi there,
> > I set up an SQL Server 2005 Enterprise Edition, so it is listening on
> > the network.
> > I can login successfully from a remote machine using osql:
> >
> > osql -H sqlhost -U sa
> > Password: XXX
> > 1>
> >
> > However I created another user "test" (SQL Auth.) and also a database
> > which test should be allowed to access but test cannot login remotely
> > (test _can_ login locally, for example in the management studio)
> >
> > osql -H sqlhost -U test -d db_test
> > Password: XXX
> > Login failed for user 'test'.
> >
> > What is strange about it, is that it doesn't even show up in the logs
> > that it did not work. There is no mention of the user "test" in the
> > logs when the remote login fails.
> >
> > Any idea what to check? What am I doing wrong? :-(
> >
> > Regards,
> > marc
> >
> >|||Yes you are right! Thanks!!

Friday, February 24, 2012

Cannot connect to SQL Server through VPN

I established a VPN tunnel to my network at work to test merge replication.
While I am able to connect via VPN to my network and ping the server in
which the SQL server resides, I am not able to establish a connection to the
Sql Server to register in my Enterprise Manager. The error I get is "Sql
Server does not exist or Connection OPen [Connect()]. I am running Win2k
Pro in my home station, sp4, mdac 2.8 and ie6 with all updates. The server
is a win 2k Server with the same updates as my station. Sql Server in both
sides is 2000. The connection method is through DSL. Only two of close to
50 vpn subscribers in my network are experiencing this problem. The
firewall is a Watchguard 2500 firebox, router is a cisco router and the
switch is an HP switch. Some of the other subscribers are also DSL. My
gateway at home is a 2Gateway wireless portal.
Thanks for any help any of you may provide.Run the following command to make sure you can connect to the server through
the sql port, which is 1433 by default:
telnet servername_or_ip 1433
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
news:%23%23Hi0fwAEHA.1452@.TK2MSFTNGP09.phx.gbl...
> I established a VPN tunnel to my network at work to test merge
replication.
> While I am able to connect via VPN to my network and ping the server in
> which the SQL server resides, I am not able to establish a connection to
the
> Sql Server to register in my Enterprise Manager. The error I get is "Sql
> Server does not exist or Connection OPen [Connect()]. I am running Win2k
> Pro in my home station, sp4, mdac 2.8 and ie6 with all updates. The
server
> is a win 2k Server with the same updates as my station. Sql Server in
both
> sides is 2000. The connection method is through DSL. Only two of close
to
> 50 vpn subscribers in my network are experiencing this problem. The
> firewall is a Watchguard 2500 firebox, router is a cisco router and the
> switch is an HP switch. Some of the other subscribers are also DSL. My
> gateway at home is a 2Gateway wireless portal.
> Thanks for any help any of you may provide.
>|||Hi,
Can you create a Alias server using "CLient network utility with the
protocol as TCP/IP , IPaddress and Port number.
After that try connecting to SQL server using the Alias name you just
created.
Thanks
Hari
MCDBA
"Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
news:##Hi0fwAEHA.1452@.TK2MSFTNGP09.phx.gbl...
> I established a VPN tunnel to my network at work to test merge
replication.
> While I am able to connect via VPN to my network and ping the server in
> which the SQL server resides, I am not able to establish a connection to
the
> Sql Server to register in my Enterprise Manager. The error I get is "Sql
> Server does not exist or Connection OPen [Connect()]. I am running Win2k
> Pro in my home station, sp4, mdac 2.8 and ie6 with all updates. The
server
> is a win 2k Server with the same updates as my station. Sql Server in
both
> sides is 2000. The connection method is through DSL. Only two of close
to
> 50 vpn subscribers in my network are experiencing this problem. The
> firewall is a Watchguard 2500 firebox, router is a cisco router and the
> switch is an HP switch. Some of the other subscribers are also DSL. My
> gateway at home is a 2Gateway wireless portal.
> Thanks for any help any of you may provide.
>

Cannot connect to SQL Server through VPN

I established a VPN tunnel to my network at work to test merge replication.
While I am able to connect via VPN to my network and ping the server in
which the SQL server resides, I am not able to establish a connection to the
Sql Server to register in my Enterprise Manager. The error I get is "Sql
Server does not exist or Connection OPen [Connect()]. I am running Win2
k
Pro in my home station, sp4, mdac 2.8 and ie6 with all updates. The server
is a win 2k Server with the same updates as my station. Sql Server in both
sides is 2000. The connection method is through DSL. Only two of close to
50 vpn subscribers in my network are experiencing this problem. The
firewall is a Watchguard 2500 firebox, router is a cisco router and the
switch is an HP switch. Some of the other subscribers are also DSL. My
gateway at home is a 2Gateway wireless portal.
Thanks for any help any of you may provide.Run the following command to make sure you can connect to the server through
the sql port, which is 1433 by default:
telnet servername_or_ip 1433
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
news:%23%23Hi0fwAEHA.1452@.TK2MSFTNGP09.phx.gbl...
> I established a VPN tunnel to my network at work to test merge
replication.
> While I am able to connect via VPN to my network and ping the server in
> which the SQL server resides, I am not able to establish a connection to
the
> Sql Server to register in my Enterprise Manager. The error I get is "Sql
> Server does not exist or Connection OPen [Connect()]. I am running Wi
n2k
> Pro in my home station, sp4, mdac 2.8 and ie6 with all updates. The
server
> is a win 2k Server with the same updates as my station. Sql Server in
both
> sides is 2000. The connection method is through DSL. Only two of close
to
> 50 vpn subscribers in my network are experiencing this problem. The
> firewall is a Watchguard 2500 firebox, router is a cisco router and the
> switch is an HP switch. Some of the other subscribers are also DSL. My
> gateway at home is a 2Gateway wireless portal.
> Thanks for any help any of you may provide.
>|||Hi,
Can you create a Alias server using "CLient network utility with the
protocol as TCP/IP , IPaddress and Port number.
After that try connecting to SQL server using the Alias name you just
created.
Thanks
Hari
MCDBA
"Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
news:##Hi0fwAEHA.1452@.TK2MSFTNGP09.phx.gbl...
> I established a VPN tunnel to my network at work to test merge
replication.
> While I am able to connect via VPN to my network and ping the server in
> which the SQL server resides, I am not able to establish a connection to
the
> Sql Server to register in my Enterprise Manager. The error I get is "Sql
> Server does not exist or Connection OPen [Connect()]. I am running Wi
n2k
> Pro in my home station, sp4, mdac 2.8 and ie6 with all updates. The
server
> is a win 2k Server with the same updates as my station. Sql Server in
both
> sides is 2000. The connection method is through DSL. Only two of close
to
> 50 vpn subscribers in my network are experiencing this problem. The
> firewall is a Watchguard 2500 firebox, router is a cisco router and the
> switch is an HP switch. Some of the other subscribers are also DSL. My
> gateway at home is a 2Gateway wireless portal.
> Thanks for any help any of you may provide.
>|||Hari:
Thanks for replying but was one of the first things I've tried...
Any other Idea's?
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23qqDBDyAEHA.3248@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Can you create a Alias server using "CLient network utility with the
> protocol as TCP/IP , IPaddress and Port number.
> After that try connecting to SQL server using the Alias name you just
> created.
> Thanks
> Hari
> MCDBA
>
> "Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
> news:##Hi0fwAEHA.1452@.TK2MSFTNGP09.phx.gbl...
> replication.
> the
"Sql
Win2k
> server
> both
> to
>|||What port is your SQL server listening on? Check the router at home to
verify you can access that port.
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
news:OAtI5tUBEHA.576@.TK2MSFTNGP11.phx.gbl...
> Hari:
> Thanks for replying but was one of the first things I've tried...
> Any other Idea's?
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23qqDBDyAEHA.3248@.TK2MSFTNGP11.phx.gbl...
in
to
> "Sql
> Win2k
close
the
My
>|||My suggestion would be to make network traces on both the client and the
server. This will tell you if the traffic is ever reaching the server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Cannot connect to SQL Server through VPN

I established a VPN tunnel to my network at work to test merge replication.
While I am able to connect via VPN to my network and ping the server in
which the SQL server resides, I am not able to establish a connection to the
Sql Server to register in my Enterprise Manager. The error I get is "Sql
Server does not exist or Connection OPen [Connect()]. I am running Win2
k
Pro in my home station, sp4, mdac 2.8 and ie6 with all updates. The server
is a win 2k Server with the same updates as my station. Sql Server in both
sides is 2000. The connection method is through DSL. Only two of close to
50 vpn subscribers in my network are experiencing this problem. The
firewall is a Watchguard 2500 firebox, router is a cisco router and the
switch is an HP switch. Some of the other subscribers are also DSL. My
gateway at home is a 2Gateway wireless portal.
Thanks for any help any of you may provide.Run the following command to make sure you can connect to the server through
the sql port, which is 1433 by default:
telnet servername_or_ip 1433
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
news:%23%23Hi0fwAEHA.1452@.TK2MSFTNGP09.phx.gbl...
> I established a VPN tunnel to my network at work to test merge
replication.
> While I am able to connect via VPN to my network and ping the server in
> which the SQL server resides, I am not able to establish a connection to
the
> Sql Server to register in my Enterprise Manager. The error I get is "Sql
> Server does not exist or Connection OPen [Connect()]. I am running Wi
n2k
> Pro in my home station, sp4, mdac 2.8 and ie6 with all updates. The
server
> is a win 2k Server with the same updates as my station. Sql Server in
both
> sides is 2000. The connection method is through DSL. Only two of close
to
> 50 vpn subscribers in my network are experiencing this problem. The
> firewall is a Watchguard 2500 firebox, router is a cisco router and the
> switch is an HP switch. Some of the other subscribers are also DSL. My
> gateway at home is a 2Gateway wireless portal.
> Thanks for any help any of you may provide.
>|||Hi,
Can you create a Alias server using "CLient network utility with the
protocol as TCP/IP , IPaddress and Port number.
After that try connecting to SQL server using the Alias name you just
created.
Thanks
Hari
MCDBA
"Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
news:##Hi0fwAEHA.1452@.TK2MSFTNGP09.phx.gbl...
> I established a VPN tunnel to my network at work to test merge
replication.
> While I am able to connect via VPN to my network and ping the server in
> which the SQL server resides, I am not able to establish a connection to
the
> Sql Server to register in my Enterprise Manager. The error I get is "Sql
> Server does not exist or Connection OPen [Connect()]. I am running Wi
n2k
> Pro in my home station, sp4, mdac 2.8 and ie6 with all updates. The
server
> is a win 2k Server with the same updates as my station. Sql Server in
both
> sides is 2000. The connection method is through DSL. Only two of close
to
> 50 vpn subscribers in my network are experiencing this problem. The
> firewall is a Watchguard 2500 firebox, router is a cisco router and the
> switch is an HP switch. Some of the other subscribers are also DSL. My
> gateway at home is a 2Gateway wireless portal.
> Thanks for any help any of you may provide.
>|||Hari:
Thanks for replying but was one of the first things I've tried...
Any other Idea's?
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23qqDBDyAEHA.3248@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Can you create a Alias server using "CLient network utility with the
> protocol as TCP/IP , IPaddress and Port number.
> After that try connecting to SQL server using the Alias name you just
> created.
> Thanks
> Hari
> MCDBA
>
> "Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
> news:##Hi0fwAEHA.1452@.TK2MSFTNGP09.phx.gbl...
> replication.
> the
"Sql
Win2k
> server
> both
> to
>|||What port is your SQL server listening on? Check the router at home to
verify you can access that port.
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Paul Ohlemacher" <Paul.Ohlemacher@.execupay.com> wrote in message
news:OAtI5tUBEHA.576@.TK2MSFTNGP11.phx.gbl...
> Hari:
> Thanks for replying but was one of the first things I've tried...
> Any other Idea's?
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23qqDBDyAEHA.3248@.TK2MSFTNGP11.phx.gbl...
in
to
> "Sql
> Win2k
close
the
My
>

Cannot connect to SQL server over network after SP2

Hello,
I'll try my luck in this group before I re-install the whole thing.
I'm running MS SQL Server 2005 developer edition on the Windows Server
2003 Small Business Edition.
Few days ago I have updated to the SP2 via windows update.
Since then I cannot connect to the SQL server remotely (using
Management Studio).
- If I log remotely to the server box I can connect locally and all
looks fine.
However, from the network it does not work.
- The SQL Server browser is running..
- TCP & Named Pipes are enabled.
- No errors in the Event Viewer
- "Allow remote connections to this server" property is enabled
- Both firewalls (server & client) are off.
- Both authentication types (SQL auth / Windows auth) are not working
Has anyone had similar problem? Any ideas?
Thank you,
Damir Sudarevic
What is the error message you are getting? We just finished installing SP2
on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
log event at all? Or when trying to access the server from remote location
the computer refuses to see the SQL server?
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:

> Hello,
> I'll try my luck in this group before I re-install the whole thing.
> I'm running MS SQL Server 2005 developer edition on the Windows Server
> 2003 Small Business Edition.
> Few days ago I have updated to the SP2 via windows update.
> Since then I cannot connect to the SQL server remotely (using
> Management Studio).
> - If I log remotely to the server box I can connect locally and all
> looks fine.
> However, from the network it does not work.
> - The SQL Server browser is running..
> - TCP & Named Pipes are enabled.
> - No errors in the Event Viewer
> - "Allow remote connections to this server" property is enabled
> - Both firewalls (server & client) are off.
> - Both authentication types (SQL auth / Windows auth) are not working
>
> Has anyone had similar problem? Any ideas?
> Thank you,
> Damir Sudarevic
>
|||On Jun 27, 8:12 pm, Mohit K. Gupta
<MohitKGu...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> What is the error message you are getting? We just finished installingSP2
> on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> log event at all? Or when trying to access the server from remote location
> the computer refuses to see the SQL server?
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
>
>
>
>
Hi,
No error messages. The Management Studio (from remote clients - more
than one) simply hangs up.
The studio actually sees the server (in browse servers), but
connection can not be established.
If I log in remotely to the server box and start MS over there it
works fine.
Thanks.
|||Hangs up? SO you have to kill the SSMS and then you can use the computer,
only thing I had that is when our network guys mucked up the firewall
settings. Check for port 1433 connection.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:

> On Jun 27, 8:12 pm, Mohit K. Gupta
> <MohitKGu...@.discussions.microsoft.com> wrote:
> Hi,
> No error messages. The Management Studio (from remote clients - more
> than one) simply hangs up.
> The studio actually sees the server (in browse servers), but
> connection can not be established.
> If I log in remotely to the server box and start MS over there it
> works fine.
> Thanks.
>
|||On Jun 29, 1:28 pm, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:[vbcol=seagreen]
> Hangs up? SO you have to kill the SSMS and then you can use the computer,
> only thing I had that is when our network guys mucked up the firewall
> settings. Check for port 1433 connection.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
>
>
>
>
>
>
>
Works!
Thank you Mohit, it was (something) about the ports. Changed TCP ports
to Dynamic and everything started working. Not quite sure what is
dynamic vs 1433; but as long as it works...
Thanks again,
Damir

Cannot connect to SQL server over network after SP2

Hello,
I'll try my luck in this group before I re-install the whole thing.
I'm running MS SQL Server 2005 developer edition on the Windows Server
2003 Small Business Edition.
Few days ago I have updated to the SP2 via windows update.
Since then I cannot connect to the SQL server remotely (using
Management Studio).
- If I log remotely to the server box I can connect locally and all
looks fine.
However, from the network it does not work.
- The SQL Server browser is running..
- TCP & Named Pipes are enabled.
- No errors in the Event Viewer
- "Allow remote connections to this server" property is enabled
- Both firewalls (server & client) are off.
- Both authentication types (SQL auth / Windows auth) are not working
Has anyone had similar problem? Any ideas?
Thank you,
Damir SudarevicWhat is the error message you are getting? We just finished installing SP2
on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
log event at all? Or when trying to access the server from remote location
the computer refuses to see the SQL server?
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:

> Hello,
> I'll try my luck in this group before I re-install the whole thing.
> I'm running MS SQL Server 2005 developer edition on the Windows Server
> 2003 Small Business Edition.
> Few days ago I have updated to the SP2 via windows update.
> Since then I cannot connect to the SQL server remotely (using
> Management Studio).
> - If I log remotely to the server box I can connect locally and all
> looks fine.
> However, from the network it does not work.
> - The SQL Server browser is running..
> - TCP & Named Pipes are enabled.
> - No errors in the Event Viewer
> - "Allow remote connections to this server" property is enabled
> - Both firewalls (server & client) are off.
> - Both authentication types (SQL auth / Windows auth) are not working
>
> Has anyone had similar problem? Any ideas?
> Thank you,
> Damir Sudarevic
>|||On Jun 27, 8:12 pm, Mohit K. Gupta
<MohitKGu...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> What is the error message you are getting? We just finished installingSP2
> on SQL 2005 EE, and no problems at all. Does it contain Login Failed erro
r
> log event at all? Or when trying to access the server from remote locatio
n
> the computer refuses to see the SQL server?
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
>
>
>
>
>
>
>
>
>
Hi,
No error messages. The Management Studio (from remote clients - more
than one) simply hangs up.
The studio actually sees the server (in browse servers), but
connection can not be established.
If I log in remotely to the server box and start MS over there it
works fine.
Thanks.|||Hangs up? SO you have to kill the SSMS and then you can use the computer,
only thing I had that is when our network guys mucked up the firewall
settings. Check for port 1433 connection.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:

> On Jun 27, 8:12 pm, Mohit K. Gupta
> <MohitKGu...@.discussions.microsoft.com> wrote:
> Hi,
> No error messages. The Management Studio (from remote clients - more
> than one) simply hangs up.
> The studio actually sees the server (in browse servers), but
> connection can not be established.
> If I log in remotely to the server box and start MS over there it
> works fine.
> Thanks.
>|||On Jun 29, 1:28 pm, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:[vbcol=seagreen]
> Hangs up? SO you have to kill the SSMS and then you can use the computer,
> only thing I had that is when our network guys mucked up the firewall
> settings. Check for port 1433 connection.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Works!
Thank you Mohit, it was (something) about the ports. Changed TCP ports
to Dynamic and everything started working. Not quite sure what is
dynamic vs 1433; but as long as it works...
Thanks again,
Damir

Cannot connect to SQL server over network after SP2

Hello,
I'll try my luck in this group before I re-install the whole thing.
I'm running MS SQL Server 2005 developer edition on the Windows Server
2003 Small Business Edition.
Few days ago I have updated to the SP2 via windows update.
Since then I cannot connect to the SQL server remotely (using
Management Studio).
- If I log remotely to the server box I can connect locally and all
looks fine.
However, from the network it does not work.
- The SQL Server browser is running..
- TCP & Named Pipes are enabled.
- No errors in the Event Viewer
- "Allow remote connections to this server" property is enabled
- Both firewalls (server & client) are off.
- Both authentication types (SQL auth / Windows auth) are not working
Has anyone had similar problem? Any ideas?
Thank you,
Damir SudarevicWhat is the error message you are getting? We just finished installing SP2
on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
log event at all? Or when trying to access the server from remote location
the computer refuses to see the SQL server?
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:
> Hello,
> I'll try my luck in this group before I re-install the whole thing.
> I'm running MS SQL Server 2005 developer edition on the Windows Server
> 2003 Small Business Edition.
> Few days ago I have updated to the SP2 via windows update.
> Since then I cannot connect to the SQL server remotely (using
> Management Studio).
> - If I log remotely to the server box I can connect locally and all
> looks fine.
> However, from the network it does not work.
> - The SQL Server browser is running..
> - TCP & Named Pipes are enabled.
> - No errors in the Event Viewer
> - "Allow remote connections to this server" property is enabled
> - Both firewalls (server & client) are off.
> - Both authentication types (SQL auth / Windows auth) are not working
>
> Has anyone had similar problem? Any ideas?
> Thank you,
> Damir Sudarevic
>|||On Jun 27, 8:12 pm, Mohit K. Gupta
<MohitKGu...@.discussions.microsoft.com> wrote:
> What is the error message you are getting? We just finished installingSP2
> on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> log event at all? Or when trying to access the server from remote location
> the computer refuses to see the SQL server?
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
> > Hello,
> > I'll try my luck in this group before I re-install the whole thing.
> > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > 2003 Small Business Edition.
> > Few days ago I have updated to theSP2via windows update.
> > Since then Icannotconnectto the SQL server remotely (using
> > Management Studio).
> > - If I log remotely to the server box I canconnectlocally and all
> > looks fine.
> > However, from the network it does not work.
> > - The SQL Server browser is running..
> > - TCP & Named Pipes are enabled.
> > - No errors in the Event Viewer
> > - "Allow remote connections to this server" property is enabled
> > - Both firewalls (server & client) are off.
> > - Both authentication types (SQL auth / Windows auth) are not working
> > Has anyone had similar problem? Any ideas?
> > Thank you,
> > Damir Sudarevic
Hi,
No error messages. The Management Studio (from remote clients - more
than one) simply hangs up.
The studio actually sees the server (in browse servers), but
connection can not be established.
If I log in remotely to the server box and start MS over there it
works fine.
Thanks.|||Hangs up? SO you have to kill the SSMS and then you can use the computer,
only thing I had that is when our network guys mucked up the firewall
settings. Check for port 1433 connection.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:
> On Jun 27, 8:12 pm, Mohit K. Gupta
> <MohitKGu...@.discussions.microsoft.com> wrote:
> > What is the error message you are getting? We just finished installingSP2
> > on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> > log event at all? Or when trying to access the server from remote location
> > the computer refuses to see the SQL server?
> >
> > --
> > Mohit K. Gupta
> > B.Sc. CS, Minor Japanese
> > MCTS: SQL Server 2005
> >
> > "Damir" wrote:
> > > Hello,
> >
> > > I'll try my luck in this group before I re-install the whole thing.
> >
> > > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > > 2003 Small Business Edition.
> >
> > > Few days ago I have updated to theSP2via windows update.
> > > Since then Icannotconnectto the SQL server remotely (using
> > > Management Studio).
> >
> > > - If I log remotely to the server box I canconnectlocally and all
> > > looks fine.
> >
> > > However, from the network it does not work.
> >
> > > - The SQL Server browser is running..
> > > - TCP & Named Pipes are enabled.
> > > - No errors in the Event Viewer
> > > - "Allow remote connections to this server" property is enabled
> > > - Both firewalls (server & client) are off.
> > > - Both authentication types (SQL auth / Windows auth) are not working
> >
> > > Has anyone had similar problem? Any ideas?
> >
> > > Thank you,
> >
> > > Damir Sudarevic
> Hi,
> No error messages. The Management Studio (from remote clients - more
> than one) simply hangs up.
> The studio actually sees the server (in browse servers), but
> connection can not be established.
> If I log in remotely to the server box and start MS over there it
> works fine.
> Thanks.
>|||On Jun 29, 1:28 pm, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:
> Hangs up? SO you have to kill the SSMS and then you can use the computer,
> only thing I had that is when our network guys mucked up the firewall
> settings. Check for port 1433 connection.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
> > On Jun 27, 8:12 pm, Mohit K. Gupta
> > <MohitKGu...@.discussions.microsoft.com> wrote:
> > > What is the error message you are getting? We just finished installingSP2
> > > on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> > > log event at all? Or when trying to access the server from remote location
> > > the computer refuses to see the SQL server?
> > > --
> > > Mohit K. Gupta
> > > B.Sc. CS, Minor Japanese
> > > MCTS: SQL Server 2005
> > > "Damir" wrote:
> > > > Hello,
> > > > I'll try my luck in this group before I re-install the whole thing.
> > > > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > > > 2003 Small Business Edition.
> > > > Few days ago I have updated to theSP2via windows update.
> > > > Since then Icannotconnectto the SQL server remotely (using
> > > > Management Studio).
> > > > - If I log remotely to the server box I canconnectlocally and all
> > > > looks fine.
> > > > However, from the network it does not work.
> > > > - The SQL Server browser is running..
> > > > - TCP & Named Pipes are enabled.
> > > > - No errors in the Event Viewer
> > > > - "Allow remote connections to this server" property is enabled
> > > > - Both firewalls (server & client) are off.
> > > > - Both authentication types (SQL auth / Windows auth) are not working
> > > > Has anyone had similar problem? Any ideas?
> > > > Thank you,
> > > > Damir Sudarevic
> > Hi,
> > No error messages. The Management Studio (from remote clients - more
> > than one) simply hangs up.
> > The studio actually sees the server (in browse servers), but
> > connection can not be established.
> > If I log in remotely to the server box and start MS over there it
> > works fine.
> > Thanks.
Works!
Thank you Mohit, it was (something) about the ports. Changed TCP ports
to Dynamic and everything started working. Not quite sure what is
dynamic vs 1433; but as long as it works...
Thanks again,
Damir

Cannot connect to SQL Server database using ado.net after IP address has changed

Dear all,

I wasn't able to connect to my SQL server 2000 database (which reside in the network in a windows 2003 server) after the IP address of the server has changed and the server is shut down, moved and re-started.

I was able to connect to this server by using ADO using VB. I was able to register this server in my EM and was able to create ODBC connection. Just when using ADO.NET, I wasn't able to connect. Any ideas? Will there be any caching within ADO.NET still pointing to the old IP address?

Thank you for all the help in advance.There are a lot of variable possibilites here - -

are you using the same connection method in all scenarios (Windows/SQL authentication)?

Was the only change the IP address?
Was it working before the change?|||It was working before and I am using the same connection. What will the possible cause?
Thanks in advance.|||Have you rebooted your client? Could be the DNS/IP are cached on your client machine and need refreshing?|||I rebooted many many times and still didn't help. Any ideas?|||Someone else is having a similar problem. Have you tried using SQLProfiler to see if a connection attempt is been made and rejected or that no attempt has been made. If its the latter then that would point to .net.

Cannot connect to SQL Server 2005 Express with Management Studio Express

On my home machine without permanent network connections enabled, I cannot get the Management Studio connect to the database server. Always get this error:

Cannot connect ot MPLIAM\SQLEXPRESS

Additional Information:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, erro: 26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)

I have used the SQL Surface Area Configuration Tool to reset the defaults to allow remote connections, stopped and restarted the server, but still get the same message.

Please help.

Hi Michael,

I think this is a duplicate of another post from you, but I'll answer here too.

You don't say if you're actually trying to connect remotely or not. If you're connecting remotely, the issue is likely your firewall is blocking the connection. Check out the FAQ at the top of this forum for a link to the article that discuss the complete steps to allow remote connections.

Mike

|||

Can you ping \\MPLIAM?

Try usingthe IP address rather than the server name.

|||

Sorry. I lost the other post.

I'm just trying to connect on my own local machine to the server which is installed on my own local machine.

I have McAffee anti-virus software installed. There's no telling what that monstrosity is doing to shut down things -- all in the line of 'enhanced security', of course.

I am just about at my wits end trying to get this thing to work. I neglected to mention that when I first installed the server and the management studio, at least the latter connected to the former. Something changed somewhere along the way so that now it doesnt work. I've checked the Service in the Control Panel and it seems to be running. I even stopped and restarted it several times with no success. I used the config manager to configure the 'surface area' (love that one) so that remote connections are enabled. Still no luck.

What to do next?

|||

ping mpliam

Pinging MPLIAM [169.254.101.152] with 32 bytes of data:

Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128

Ping statistics for 169.254.101.152:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Using Server Name: 169.254.101.152 in the Managment Studio

'cannot connect to database'

Any other ideas ?

|||

(a) check whether the service started or not from Configuration Manager Window

(b) Check whether the protocols are enabled or not from SQL Configuration Manager window

(c) Check which all are the client protocol enabled

Madhu

|||

In the other thread I had suggest trying a connection via SQLCmd, just to rule out any Management Studio weirdness, are you able to do that? To reiterate, open a command prompt and type the following:

SQLCmd -S .\SQLEXPRESS -E -Q "SELECT @.@.Version"

This should return version information about your server if it works. If it fails, please post back the complete error message. As a second step should you encounter failure, please check the error log after the attempted connection to see if there is additional informaton there. The error log should be at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG.

It's interesting that you say this worked initially but connectons started failing later. This would indeed suggest that "something else" is impacting this, but I've no idea what. In general I wouldn't expect any AV program to prevent connections to SQL, but we should probably test this. As a temprorary troubleshooting step, disable McAffe and then try your connection again. Regardless of the result, turn McAffe back on once you've completed the test, but let us know if that impacts anything.

Finally, could you copy the test from the "Server" text box in the Management Studio Connection dialog and paste it into your reply?

Mike

|||

Thanks for your response, Mike.

I apologize for taking so long to respond. In any case, when I attempted at the Command Prompt:


SQLCmd -S .\SQLEXPRESS -E -Q "SELECT @.@.Version"

I received the following message (preceeded by a bunch of dashed lines):


Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

(1 rows affected)

The Error Log was quite extensive and, since I have been fooling with SQL Server quite a bit, I am uncertain which section pertains. But I interpret the above to indicate that the installation is working.

Here's a little bit of the most recent part of the Error Log:


2007-03-18 09:00:44.95 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2007-03-18 09:00:44.95 Server (c) 2005 Microsoft Corporation.
2007-03-18 09:00:44.95 Server All rights reserved.
2007-03-18 09:00:44.96 Server Server process ID is 552.
2007-03-18 09:00:44.96 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-18 09:00:44.96 Server This instance of SQL Server last reported using a process ID of 236 at 3/17/2007 10:54:30 PM (local) 3/18/2007 5:54:30 AM (UTC). This is an informational message only; no user action is required.
2007-03-18 09:00:44.98 Server Registry startup parameters:
2007-03-18 09:00:44.98 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-18 09:00:44.98 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-18 09:00:44.98 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-18 09:00:45.06 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-03-18 09:00:45.06 Server Detected 1 CPUs. This is an informational message; no user action is required.
2007-03-18 09:00:45.67 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-03-18 09:00:45.70 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-03-18 09:00:45.71 spid5s Starting up database 'master'.
2007-03-18 09:00:46.04 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
// .....

The Server Text Box from the Management Studio (if I understand your request) looks as follows:


Connect to Server

Server type: Database Engine (disabled)
Server name: MPLIAM\SQLEXPRESS
Authentication: Windows Atuhentication
User name: MBPLIAM\Michael B Pliam (disabled)
Password: (blank and disabled)

Attempting to connect results in:

Connect to Server
Cannot connect to MPLIAM\SQLEXPRESS.

Additional information:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

I will try to disable McAffee Virus Protection and get back to you if it makes any difference (Assuming that I can figure out how to disable it - it's sort of like getting rid of a bad cold.)

Thanks again for your help. Again, I wish to apologize for having lost this thread.

|||

You are correct that the output of SQLCmd indicates that SQL Express is working fine and can be accessed locally with no problems. This would suggest a specific problem with Management Studio. I don't see any problem with the information you supplied, but the error message indicates that the specific instance name you've supplied is incorrect.

Replace the value in the 'Server name' text box with .\SQLEXPRESS and see if that makes any difference. If this works, it would mean that your machine name is not actually MPLIAM. If it doesn't work, we may to punt this over to the tools guys to see if they have any ideas.

Mike

|||

Problem solved !

Using .\SQLEXPRESS instead of MPLIAM\SQLEXPRESS allowed the Management Studio to connect to the server.

I still do not understand what the problem was.

My 'host' machine is definitely 'MPLIAM'.

If I 'ping MPLIAM' from a Command Line prompt (as I believe I posted before), I receive the response:


Pinging MPLIAM [169.254.101.152] with 32 bytes of data:

Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128

Ping statistics for 169.254.101.152:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Further, MSDN provides C++ source code to determine the host machine name and volume. For those interested, see:

http://windowssdk.msdn.microsoft.com/en-us/library/ms738527.aspx

Running that program reveals

MPLIAM
3758647270

the host name and volume number respectively.

When Management Studio did connect (as noted above), the connection text box header has the following information:


Summary

.\SQLEXPRESS (SQL Server 9.0.1399 - MPLIAM\Michael B Pliam)
MPLIAM\SQLEXPRESS 5 Items(s)

Mike, I want to thank you for your patience in helping me to solve this problem. If my tone at times appeared intemperant, it was simply my frustration at being unable to get this program to work. As is usually the case, it was probably my fault that things were awry. I must have changed something without being aware of it. Once things go bad, I have a tendency to start changing everything in sight instead of cautiously exploring the nature of the problem.

Regards

|||

I'm glad that it's working. It's odd that the machine name is not being recognized, but if you're happy, I'm happy.

Mike

|||Hi,

I've been struggling with a similar problem. Wasn't able to connect remotely and everything was setup correctly on the Surface Area Configuration. I could connect locally though, but not remotely. Used the exact same Windows User each time, and no firewall in between client and server. The eventual resolution was something really simple and stupid on my part.

The SQL Server browser service wasn't running, all that I did was start it and suddenly I could connect remotely... which is strange because I've never had this issue with any other SQL server I've worked with...

anyway hope it helps...

Cannot connect to SQL Server 2005 Express with Management Studio Express

On my home machine without permanent network connections enabled, I cannot get the Management Studio connect to the database server. Always get this error:

Cannot connect ot MPLIAM\SQLEXPRESS

Additional Information:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, erro: 26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)

I have used the SQL Surface Area Configuration Tool to reset the defaults to allow remote connections, stopped and restarted the server, but still get the same message.

Please help.

Hi Michael,

I think this is a duplicate of another post from you, but I'll answer here too.

You don't say if you're actually trying to connect remotely or not. If you're connecting remotely, the issue is likely your firewall is blocking the connection. Check out the FAQ at the top of this forum for a link to the article that discuss the complete steps to allow remote connections.

Mike

|||

Can you ping \\MPLIAM?

Try usingthe IP address rather than the server name.

|||

Sorry. I lost the other post.

I'm just trying to connect on my own local machine to the server which is installed on my own local machine.

I have McAffee anti-virus software installed. There's no telling what that monstrosity is doing to shut down things -- all in the line of 'enhanced security', of course.

I am just about at my wits end trying to get this thing to work. I neglected to mention that when I first installed the server and the management studio, at least the latter connected to the former. Something changed somewhere along the way so that now it doesnt work. I've checked the Service in the Control Panel and it seems to be running. I even stopped and restarted it several times with no success. I used the config manager to configure the 'surface area' (love that one) so that remote connections are enabled. Still no luck.

What to do next?

|||

ping mpliam

Pinging MPLIAM [169.254.101.152] with 32 bytes of data:

Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128

Ping statistics for 169.254.101.152:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Using Server Name: 169.254.101.152 in the Managment Studio

'cannot connect to database'

Any other ideas ?

|||

(a) check whether the service started or not from Configuration Manager Window

(b) Check whether the protocols are enabled or not from SQL Configuration Manager window

(c) Check which all are the client protocol enabled

Madhu

|||

In the other thread I had suggest trying a connection via SQLCmd, just to rule out any Management Studio weirdness, are you able to do that? To reiterate, open a command prompt and type the following:

SQLCmd -S .\SQLEXPRESS -E -Q "SELECT @.@.Version"

This should return version information about your server if it works. If it fails, please post back the complete error message. As a second step should you encounter failure, please check the error log after the attempted connection to see if there is additional informaton there. The error log should be at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG.

It's interesting that you say this worked initially but connectons started failing later. This would indeed suggest that "something else" is impacting this, but I've no idea what. In general I wouldn't expect any AV program to prevent connections to SQL, but we should probably test this. As a temprorary troubleshooting step, disable McAffe and then try your connection again. Regardless of the result, turn McAffe back on once you've completed the test, but let us know if that impacts anything.

Finally, could you copy the test from the "Server" text box in the Management Studio Connection dialog and paste it into your reply?

Mike

|||

Thanks for your response, Mike.

I apologize for taking so long to respond. In any case, when I attempted at the Command Prompt:


SQLCmd -S .\SQLEXPRESS -E -Q "SELECT @.@.Version"

I received the following message (preceeded by a bunch of dashed lines):


Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

(1 rows affected)

The Error Log was quite extensive and, since I have been fooling with SQL Server quite a bit, I am uncertain which section pertains. But I interpret the above to indicate that the installation is working.

Here's a little bit of the most recent part of the Error Log:


2007-03-18 09:00:44.95 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2007-03-18 09:00:44.95 Server (c) 2005 Microsoft Corporation.
2007-03-18 09:00:44.95 Server All rights reserved.
2007-03-18 09:00:44.96 Server Server process ID is 552.
2007-03-18 09:00:44.96 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-18 09:00:44.96 Server This instance of SQL Server last reported using a process ID of 236 at 3/17/2007 10:54:30 PM (local) 3/18/2007 5:54:30 AM (UTC). This is an informational message only; no user action is required.
2007-03-18 09:00:44.98 Server Registry startup parameters:
2007-03-18 09:00:44.98 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-18 09:00:44.98 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-18 09:00:44.98 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-18 09:00:45.06 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-03-18 09:00:45.06 Server Detected 1 CPUs. This is an informational message; no user action is required.
2007-03-18 09:00:45.67 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-03-18 09:00:45.70 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-03-18 09:00:45.71 spid5s Starting up database 'master'.
2007-03-18 09:00:46.04 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
// .....

The Server Text Box from the Management Studio (if I understand your request) looks as follows:


Connect to Server

Server type: Database Engine (disabled)
Server name: MPLIAM\SQLEXPRESS
Authentication: Windows Atuhentication
User name: MBPLIAM\Michael B Pliam (disabled)
Password: (blank and disabled)

Attempting to connect results in:

Connect to Server
Cannot connect to MPLIAM\SQLEXPRESS.

Additional information:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

I will try to disable McAffee Virus Protection and get back to you if it makes any difference (Assuming that I can figure out how to disable it - it's sort of like getting rid of a bad cold.)

Thanks again for your help. Again, I wish to apologize for having lost this thread.

|||

You are correct that the output of SQLCmd indicates that SQL Express is working fine and can be accessed locally with no problems. This would suggest a specific problem with Management Studio. I don't see any problem with the information you supplied, but the error message indicates that the specific instance name you've supplied is incorrect.

Replace the value in the 'Server name' text box with .\SQLEXPRESS and see if that makes any difference. If this works, it would mean that your machine name is not actually MPLIAM. If it doesn't work, we may to punt this over to the tools guys to see if they have any ideas.

Mike

|||

Problem solved !

Using .\SQLEXPRESS instead of MPLIAM\SQLEXPRESS allowed the Management Studio to connect to the server.

I still do not understand what the problem was.

My 'host' machine is definitely 'MPLIAM'.

If I 'ping MPLIAM' from a Command Line prompt (as I believe I posted before), I receive the response:


Pinging MPLIAM [169.254.101.152] with 32 bytes of data:

Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128
Reply from 169.254.101.152: bytes=32 time<1ms TTL=128

Ping statistics for 169.254.101.152:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Further, MSDN provides C++ source code to determine the host machine name and volume. For those interested, see:

http://windowssdk.msdn.microsoft.com/en-us/library/ms738527.aspx

Running that program reveals

MPLIAM
3758647270

the host name and volume number respectively.

When Management Studio did connect (as noted above), the connection text box header has the following information:


Summary

.\SQLEXPRESS (SQL Server 9.0.1399 - MPLIAM\Michael B Pliam)
MPLIAM\SQLEXPRESS 5 Items(s)

Mike, I want to thank you for your patience in helping me to solve this problem. If my tone at times appeared intemperant, it was simply my frustration at being unable to get this program to work. As is usually the case, it was probably my fault that things were awry. I must have changed something without being aware of it. Once things go bad, I have a tendency to start changing everything in sight instead of cautiously exploring the nature of the problem.

Regards

|||

I'm glad that it's working. It's odd that the machine name is not being recognized, but if you're happy, I'm happy.

Mike

|||Hi,

I've been struggling with a similar problem. Wasn't able to connect remotely and everything was setup correctly on the Surface Area Configuration. I could connect locally though, but not remotely. Used the exact same Windows User each time, and no firewall in between client and server. The eventual resolution was something really simple and stupid on my part.

The SQL Server browser service wasn't running, all that I did was start it and suddenly I could connect remotely... which is strange because I've never had this issue with any other SQL server I've worked with...

anyway hope it helps...

Sunday, February 19, 2012

Cannot connect to SQL Server

Recently had to reload laptop (XP) and can no longer connect to SQL
Server. Nothing has changed on network side of things - only my
laptop. I have made sure I have SQL SP3 and latest MDAC. I can ping
the server's IP without problem. The username and password is correct.
It's hard to say without any information on the error but have you
tried creating an alias for the server using the Client Network
Utility? Can you ping the server name (not IP)? Are you getting login
failures or connectivity errors?
-Sue
On 25 Oct 2004 12:55:40 -0700, dfulton@.ctap.com (dfulton) wrote:

>Recently had to reload laptop (XP) and can no longer connect to SQL
>Server. Nothing has changed on network side of things - only my
>laptop. I have made sure I have SQL SP3 and latest MDAC. I can ping
>the server's IP without problem. The username and password is correct.

Cannot connect to SQL Server

Recently had to reload laptop (XP) and can no longer connect to SQL
Server. Nothing has changed on network side of things - only my
laptop. I have made sure I have SQL SP3 and latest MDAC. I can ping
the server's IP without problem. The username and password is correct.It's hard to say without any information on the error but have you
tried creating an alias for the server using the Client Network
Utility? Can you ping the server name (not IP)? Are you getting login
failures or connectivity errors?
-Sue
On 25 Oct 2004 12:55:40 -0700, dfulton@.ctap.com (dfulton) wrote:

>Recently had to reload laptop (XP) and can no longer connect to SQL
>Server. Nothing has changed on network side of things - only my
>laptop. I have made sure I have SQL SP3 and latest MDAC. I can ping
>the server's IP without problem. The username and password is correct.

Cannot connect to SQL Express from WEB Application on internet

Hi,

I have installed SQl express 2005 SP1 and then configured it to accept remote connections which works within my internal network. I can connect other client stations within our internal network.

However, when i try to connect to the database using a VB.net web application, the application cannot connect to the database.

I have a hardware firewall which configured to foward port TCP 1433 and UDP 1434 to the SQL express server.

I have also carried out a telnet communication to ports 1433 and 1434 and able to communicate on port 1433 and get an error message cannot connect to host on port 1434.

What am i doing wrong?

Thanks

To make Remote Connections available on SQL Server Express Edition, you need to do the following steps:

Enable the Remote Connections using the SQL Server Surface Area Configuration:|||

I have already done all of the above that you have mentioned.

I am able to romtely access the sql instance within my internal network but not from the internet.

here is the connection string that i am using:

appSettings>

<add key="Provider" value="Nothing" />

<add key="Data Source" value= "(IP of wan port)\(ip of database server)\SQLEXPRESS" />
<add key="Initial Catalog" value="Test" />
<add key="User ID" value="admin" />
<add key="Password" value="pasword" />

the error message i get is:

System.Exception: SQL Server does not exist or access denied. at WebApplication1.DALBase.OpenConnection()

|||See this http://msdn2.microsoft.com/en-us/library/ms175483.aspx to enable so.|||

Review if is opened the SQL Server ports in your Database Server Firewall and in the Proxy Server Firewall.

Thursday, February 16, 2012

Cannot connect to SQL 2000 remotely

On the server, from the Start menu, point to All Programs, point to
Microsoft SQL Server, and then click Server Network Utility. That utility
should help you understand if SQL Server is using the IPX/SPX or TCP/IP
protocols, which might indicate a problem. On the client there is a similar
program, the Client Network Utility. Obviously the client and server should
be using the same protocols.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
> I'm trying to install a bespoke application for a new client, and am
> embarassed by not being able to connect to their DB Server.
> The server and clients are XP all running on a workgroup called OFFICE
> File access is not problem and the DB Server name appears in a dropdown
> box of SQL servers on the network - e.g. when trying to create an ODBC
> DSN.
> The SQL Server is now configured to accept Windows and SQL authentication
> connection requests - and restarted.
> I have switched off or uninstalled everything that looks like a firewall
> on both server and clients.
> When trying to set up local ODBC DSN to connect as sa, I can connect no
> problem, but from one of the client laptops I just get the error:
> "Access denied or SQL Server does not exist"
> Can anyone tell me where else to look or what else to try?
> Is there a step by step procedure which could take me to the cause of the
> problem?
> The network is a wireless Lan - and IPX/SPX is featuring in the network
> stack. Could that be something to do with it?
> Any help very very much appreaciated!
> Thank you
> Clive (London UK)
>
>
>
>
Glad to help. I recognize customers stress and confusion as a problem that
we (Microsoft) often cause... and have an obligation to resolve.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:O7J9R4pzHHA.3400@.TK2MSFTNGP03.phx.gbl...
> Apologies for flame throwing. Default of DisableNetworkProtocols WAS the
> problem, but in any case
> thank for taking the time and trouble to get back to me Rick.
> Clive Elsworth
>
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
>

Tuesday, February 14, 2012

Cannot connect to remote SQL 2k5 server in local network

My SQL 2005 Dev Edition hosted on WinXP.
However my another WinXP in the same network cannot connect to the SQL 2k5
using ODBC
Got this error:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Info:
Host machine:
OS: WinXP SP2
Firewall: Opened 1433 TCP, 1434 UDP
SQL Server 2005 Dev Edit.
Instance Name: Winxp-hongpc\SQL2K5
Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
Inside TCP/IP setting:
IP1:
Active = Yes
Enabled = Yes
IP Address = 192.168.1.100
TCP Dynamic Ports = [blank]
TCP Port = 1433
IP2:
Active = Yes
Enabled = No
IP Address = 127.0.0.1
TCP Dynamic Ports = 0
TCP Port = [blank]
IPAll:
TCP Dynamic Ports: [blank]
TCP Port: 1433
Anyone helps?
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.
|||Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.
|||I retried and I found that I can connect using named piped, so what is the
problem for TCP/IP
"Jason Chan" <no@.email.com> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gb l...
Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.
|||"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gb l...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Try these:
http://support.microsoft.com/search/...de=a&x=11&y=16
http://tinyurl.com/7ef8v
steve.
|||As mentioned, 127.0.0.1 is the loopback adapter. Essentially that's the
network card connecting to itself. This comes with the network card and is
intended for troubleshooting. It's only avalable if you are connecting from
the same computer, so in your case you can just ignore it.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gb l...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>

Cannot connect to remote SQL 2k5 server in local network

My SQL 2005 Dev Edition hosted on WinXP.
However my another WinXP in the same network cannot connect to the SQL 2k5
using ODBC
Got this error:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Info:
Host machine:
OS: WinXP SP2
Firewall: Opened 1433 TCP, 1434 UDP
SQL Server 2005 Dev Edit.
Instance Name: Winxp-hongpc\SQL2K5
Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
Inside TCP/IP setting:
IP1:
Active = Yes
Enabled = Yes
IP Address = 192.168.1.100
TCP Dynamic Ports = [blank]
TCP Port = 1433
IP2:
Active = Yes
Enabled = No
IP Address = 127.0.0.1
TCP Dynamic Ports = 0
TCP Port = [blank]
IPAll:
TCP Dynamic Ports: [blank]
TCP Port: 1433
Anyone helps?"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||I retried and I found that I can connect using named piped, so what is the
problem for TCP/IP
"Jason Chan" <no@.email.com> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
>> My SQL 2005 Dev Edition hosted on WinXP.
>> However my another WinXP in the same network cannot connect to the SQL
>> 2k5
>> using ODBC
>> Got this error:
>> Connection failed:
>> SQLState: '01000'
>> SQL Server Error: 53
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 17
>> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
>> access denied.
>> Info:
>> Host machine:
>> OS: WinXP SP2
>> Firewall: Opened 1433 TCP, 1434 UDP
>> SQL Server 2005 Dev Edit.
>> Instance Name: Winxp-hongpc\SQL2K5
>> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
>> Inside TCP/IP setting:
>> IP1:
>> Active = Yes
>> Enabled = Yes
>> IP Address = 192.168.1.100
>> TCP Dynamic Ports = [blank]
>> TCP Port = 1433
>> IP2:
>> Active = Yes
>> Enabled = No
>> IP Address = 127.0.0.1
>> TCP Dynamic Ports = 0
>> TCP Port = [blank]
>> IPAll:
>> TCP Dynamic Ports: [blank]
>> TCP Port: 1433
>> Anyone helps?
>>
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Try these:
http://support.microsoft.com/search/default.aspx?spid=2855&query=sql+server+error+53&catalog=LCID%3D1033&pwt=true&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=11&y=16
http://tinyurl.com/7ef8v
steve.|||As mentioned, 127.0.0.1 is the loopback adapter. Essentially that's the
network card connecting to itself. This comes with the network card and is
intended for troubleshooting. It's only avalable if you are connecting from
the same computer, so in your case you can just ignore it.
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
>> My SQL 2005 Dev Edition hosted on WinXP.
>> However my another WinXP in the same network cannot connect to the SQL
>> 2k5
>> using ODBC
>> Got this error:
>> Connection failed:
>> SQLState: '01000'
>> SQL Server Error: 53
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 17
>> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
>> access denied.
>> Info:
>> Host machine:
>> OS: WinXP SP2
>> Firewall: Opened 1433 TCP, 1434 UDP
>> SQL Server 2005 Dev Edit.
>> Instance Name: Winxp-hongpc\SQL2K5
>> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
>> Inside TCP/IP setting:
>> IP1:
>> Active = Yes
>> Enabled = Yes
>> IP Address = 192.168.1.100
>> TCP Dynamic Ports = [blank]
>> TCP Port = 1433
>> IP2:
>> Active = Yes
>> Enabled = No
>> IP Address = 127.0.0.1
>> TCP Dynamic Ports = 0
>> TCP Port = [blank]
>> IPAll:
>> TCP Dynamic Ports: [blank]
>> TCP Port: 1433
>> Anyone helps?
>>
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>