Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

[DBNET]General Network Error. Check your network documentation.

Status
Not open for further replies.

Antzz

Programmer
Jan 17, 2001
298
US
Hi Guys,
I recently installed SQL Server 2005 but cannot access it from the network.

All help is appreciated.

R

Following is the text of the error message.

Unable to connect to server
Server Msg 11,Level 16, State 1
[Microsoft][ODBC SQL SERVER Driver][DBNET]General Network Error. Check your network documentation.
 
First, check your Service accounts and verify they are using Domain User accounts and not local machine accounts. Then go to the Surface Area Configuration tool (via Start -> Programs -> Microsoft SQL Server...) and make sure all your network protocols are set up and that the server is set up to allow Remote Access.

If you're still having problems after doing these things, post again.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Yes I tried the suggestions but to no avail.

I cannot log in using sa or any other local SQL user nor any domain user. I can log in locally with any user without any problem.
 
How are you getting to the server? Are you physically at it?
Have you checked network cable, ping, SQL server logs to make sure that it is listening on TCP port 1433. Are you sure the server is a memeber of the domain. All that good stuff..
Check the event view system log for NIC card errors.
 
There should not be any other issues since I can remotely log into the box. The server itself is a virtual machine.

I am sure it must be something pretty simple, but cannot put my fingers on it right now.
 
Can you post the solution for others who might run into your problem?

Thanks,


Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
The solution is pretty simple and I feel stupid posting it. The server needed to be rebooted.

I had assumed that the settings automatically take effect since I did not get an alert to reboot after setting up the permissions.

Thanks for all the feedback, guys!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top