October 24, 2002 at 9:50 am
Thanks much Steve for your reply,
Your (or your sa's) answer strikes me as being a littlebit vague, i ran netstat -a myself and i couldn't get an ip address from that. Only if i run ipconfig i get the ip address of my own machine in the network.
Anyway, i guess this is a networking problem and not so much a SQL problem since my recently added MDAC datalink is also not working.
Anyone idea's how to solve this, any networking experts ??
the errormessage that i get is this:
[Microsoft].[ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or access denied
October 28, 2002 at 12:25 am
Finally solved it. For all the people who have similar problems, here is my solution (finally, finally, finally). Good luck with it.
Assuming that you've checked all the other stuff like firewalls, listening ports, ping the network etc. etc., here is what worked for us:
What you do is this. Install client tools of SQL server on a test machine in the same network on a machine that had never SQL server on it. Be sure that on the server authentication is set to both SQL and Windows authentication. Login in on the new machine (client) and use SQL authentication to connect with the Server and use username: sa and corresponding password (which you can set in the server under logins). If it is working, format your other client and install windows 2000 again. Install SQL server client tools (or server) and connect. You'll see it will work.
The registry is full of old settings.
Let me know it it worked,
Regards, D.J. de Groot
October 28, 2002 at 7:24 am
A reinstall of both Windows and SQL Server is certainly one way to make sure the hardware is working right. But it masks the problem. What really was set wrong? I suppose we won't know.
Steve Miller
October 28, 2002 at 11:14 am
It must have been a registry problem.
Anyway, i am very happy to be out of trouble now. 🙂
was starting to develop some grey hairs...
Bye deejay
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply