Sql Error (17) Server does not exist or access denied

My Host name is perfect there are not issues with host name as far as i believe. But for some reason when i try to make the ODBC connection i am getting the following error.

Can somebody help me please?

The error is - Sql Error (17) Server does not exist or access denied.

Thank You, Vinay

Hi. Maybe I have a similar problem. You can find attached the settings I normally use to connect to database from the server machine and it works. If I try exactly the same from a client PC connected to the same local network it gives Sql Error (17)

Someone can help me?

Thanks Fulvio

Can somebody have a look and please provide the solutions?please

My Host name is perfect there are not issues with host name as far as i believe. But for some reason when i try to make the ODBC connection i am getting the following error.

Can somebody help me please?

The error is - Sql Error (17) Server does not exist or access denied.

Thank You, Vinay> Hi. Maybe I have a similar problem. You can find attached the settings I normally use to connect to database from the server machine and it works. If I try exactly the same from a client PC connected to the same local network it gives Sql Error (17)

Someone can help me?

Thanks Fulvio> Hi. Maybe I have a similar problem. You can find attached the settings I normally use to connect to database from the server machine and it works. If I try exactly the same from a client PC connected to the same local network it gives Sql Error (17)

Someone can help me?

Thanks Fulvio> Hi. Maybe I have a similar problem. You can find attached the settings I normally use to connect to database from the server machine and it works. If I try exactly the same from a client PC connected to the same local network it gives Sql Error (17)

Someone can help me?

Thanks Fulvio> Hi. Maybe I have a similar problem. You can find attached the settings I normally use to connect to database from the server machine and it works. If I try exactly the same from a client PC connected to the same local network it gives Sql Error (17)

Someone can help me?

Thanks Fulvio

Vin@HEIDISQL, please calm down, this is not a premium support service you're paying for. I'm sure the guy who writes HeidiSQL in his spare time won't find that encouraging, esp. when you didn't care providing any detail (not even the database engine).

From Fulvio's followup I guess you are connecting to SQL Server. What details have you filled in in the session manager?

P.S. Is your reference to ODBC a typo? HeidiSQL doesn't support ODBC.

Fulvio, SERVER-PC\SISTEMI is a Windows Domain name. I'm not sure you can use that to connect using TCP/IP. Can you try with standard subdomain.domain syntax?

Hi Kalvaro. Thanks for your reply. What do you mean by subdomain.domain syntax? May I have an example? In the meanwhile I tried with 192.168.1.3\SISTEMI as hostname leaving flag on Use Windows Authentication

It gives another error: SQL Error (18456): Accesso non riuscito per l'utente 'Server-Pc\Guest'

I suppose that I must replace Guest with my user name that's UTENTE-PC but it doesn't work anyway

Bye. Fulvio

WINDOWSDOMAIN\MACHINE is the legacy Windows NT syntax, invented before the internet was a widespread service. Somewhere around the early 2000s Microsoft developed a new syntax that was compatible with internet DNS: MACHINE.WINDOWSDOMAIN.TOPLEVELDOMAIN.

You can see that you can e.g. ping to the latter but not the former.

I guess you can type either SISTEMI or 192.168.1.3 but not both.

Hi. When I type 192.168.1.3\SISTEMI or SERVER-PC\SISTEMI the error is 18456, it seems that connection to server is successful but user or password are wrong. Running Microsoft SQL Management Studio from server machine I found that host name is SERVER-PC\SISTEMI, Windows authentication is on, user name is Server-PC\Server (attached pic). I tried the same with HeidiSQL on client machine but it continue to give error 18456. Now I'm almost sure that hostname is correct, just need to understand which user I have to type....

Thanks

Fulvio

sorry, forgot to load picture

Vin@HEIDISQL, please calm down, this is not a premium support service you're paying for. I'm sure the guy who writes HeidiSQL in his spare time won't find that encouraging, esp. when you didn't care providing any detail (not even the database engine).

From Fulvio's followup I guess you are connecting to SQL Server. What details have you filled in in the session manager?

P.S. Is your reference to ODBC a typo? HeidiSQL doesn't support ODBC.> Vin@HEIDISQL, please calm down, this is not a premium support service you're paying for. I'm sure the guy who writes HeidiSQL in his spare time won't find that encouraging, esp. when you didn't care providing any detail (not even the database engine).

From Fulvio's followup I guess you are connecting to SQL Server. What details have you filled in in the session manager?

P.S. Is your reference to ODBC a typo? HeidiSQL doesn't support ODBC.> Vin@HEIDISQL, please calm down, this is not a premium support service you're paying for. I'm sure the guy who writes HeidiSQL in his spare time won't find that encouraging, esp. when you didn't care providing any detail (not even the database engine).

From Fulvio's followup I guess you are connecting to SQL Server. What details have you filled in in the session manager?

P.S. Is your reference to ODBC a typo? HeidiSQL doesn't support ODBC.> Vin@HEIDISQL, please calm down, this is not a premium support service you're paying for. I'm sure the guy who writes HeidiSQL in his spare time won't find that encouraging, esp. when you didn't care providing any detail (not even the database engine).

From Fulvio's followup I guess you are connecting to SQL Server. What details have you filled in in the session manager?

P.S. Is your reference to ODBC a typo? HeidiSQL doesn't support ODBC.> Vin@HEIDISQL, please calm down, this is not a premium support service you're paying for. I'm sure the guy who writes HeidiSQL in his spare time won't find that encouraging, esp. when you didn't care providing any detail (not even the database engine).

From Fulvio's followup I guess you are connecting to SQL Server. What details have you filled in in the session manager?

P.S. Is your reference to ODBC a typo? HeidiSQL doesn't support ODBC.

Hello Team - I fixed the issue my self. I install the driver and fixed it.

Thanks for your advise. Vinay

When I type 192.168.1.3\SISTEMI or SERVER-PC\SISTEMI the error is 18456, it seems that connection to server is successful but user or password are wrong. Running Microsoft SQL Management Studio from server machine I found that host name is SERVER-PC\SISTEMI, Windows authentication is on, user name is Server-PC\Server (attached pic).

I work inside an Active Directory every day and I guess I've been unsure all the time about what 192.168.1.3, SERVER-PC and SERVER-PC are/mean (well, 192.168.1.3 is clearly an IP address) but after seeing your latest screenshot I think it's:

• SERVER-PC -> Host name
• SERVER-PC -> SQL Server instance

If that's the case you're doing it right from he beginning. If you can connect from Management Studio, I don't know why HeidiSQL fails with error 17. Sorry!

Hello Team - I fixed the issue my self. I install the driver and fixed it.

What driver do you mean? Did the issue eventually have anything to do with HeidiSQL?