Client Connectivity Problem

Question

I have a workgroup server with windows server 2003 runs SQL Server 2000.

Some of my network clients can connect to the database successfully, and the others can't and that's my problem.

The error is (SQL Server does not exist or access is denied).

Please help me.

Answer 1

Hi,

If you use Windows Authentication and you have a domain controller, so, you have to grant access to your Active Directory users to connect to your SQL Server otherwise their access will be rejected.

If you are using SQL Server Authentication, check your users have the access rights to connect to your SQL Server.

If all above are correct check your clients' firewalls and make sure it configured correctly.

Cheers,

Soheil

---

MCP, MCTS, MCITP

Answer 2

Hi, thanks for getting back to me.

I do use Windows Authentication, but I don't have a domain controller (I Wish) it just a workgroup network.

Due to my client's firewalls, I need some details about what you meant.

Answer 3

Hmm,

In this case my personal suggestion is using SQL Server authentication. Anyway, this thread might be useful: http://stackoverflow.com/questions/7963153/how-to-connect-to-sql-server-2008-r2-on-same-workgroup-on-intranet

Cheers

---

MCP, MCTS, MCITP

Answer 4

Hello,

In a workgroup network, SQL Server authentification is the UNIQUE solution.

Have a nice day

---

Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

Answer 5

Thanks everybody.

But I am sorry, I think you missed the point:

I HAVE A CLIENT THAT CAN CONNECT SUCCESSFULLY TO THE DATABASE.

THE OTHER CLIENT CAN'T, AND THE MESSAGE IT ISSUES IS "SQL SERVER DOESN'T EXIST OR ACCESS IS DENIED"..

So clearly the problem is related to the other client and not the server.

I really appreciate your efforts to help me. But please try again.

Answer 6

Hello,

You have to search what are the differences between the computers which can connect and the computers which cannot connect on the 2 levels :

- the full edition/version of the operating systems of both computers ( for example Windows XP 32 bits Pro SP3 with language English ).You have differences between Pro and Home versions ( between Pro : no problem but with Home , beurk... ). XP and 2000 : no problem.Vista especially Home : a disaster, less problems with Windows 7 home/Pro

- the firewalls on the computer hosting SQL Server and the both computers trying to connect to your SQL Server instance must have the same ports ( for TCP and UDP ) configured in the same way for each of the 3 computers.

Be careful with some Antivirus suites which block some ports without no warning.

We are waiting for your feedback to try to help you more efficiently.

Have a nice day

---

Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

Answer 7

SQL Server (in server machine) normally use TCP port 1433 and TCP/UDP port 1434 for connectivity. However, in client side it is different. Clients connect to SQL Server using a random port between 1024~5000. So, check the following:

1. You can connect to SQL Server from one client, hence, your SQL Server machine's firewall cannot be the issue.
2. In the faulty machine check network connectivity if it is successful by pinging SQL Server machine.
3. In the faculty machine's firewall (windows firewall or any Internet Security suit's firewall settings) you have to allow traffic from *ANY* to 1433 and 1433 to *ANY* where *ANY* is a port greater than 1024.
4. Apply the similar settings for TCP/UDP 1434 port.
5. Again, check if the user is defined correctly in SQL Server machine.

Cheers

---

MCP, MCTS, MCITP