Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
OwnedByTheMan
Starting Member
35 Posts |
 Posted - 2001-02-03 : 17:41:37
|
| I have had my SQL2000 Server running fine until a few days ago when I decided to reinstall Win2k Advanced Server on my other machine. In the redesign, I have broken, or perhaps highlighted an exisiting connection issue.Up until now, I had been assuming that all my database connectionwere taking place via TCP/IP. I am afraid I have to plead ignorance and never really spent much time messing with the network libraries. I find myself now, not being able to connect to the server from either of my machines. Perhaps the contrast in the problems with both the client machines will tewak someones memory and help me out (I have searched the archives and read all the messages I can regarding this and still am not sure where to run).Machine 1 is a DHCP addressed machine, originally in the same workgroup as the SQL server but now running standalone with only TCP/IP installed. It errors out with:ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.Machine 2 is the webserver. It too was also in the same workgroup and remains in a workgroup with the SQL server via TCP/IP. It errors with either "Client unable to establish connection (if NetBeui is removed) or a Named Pipe error if NetBeui is activated.What I think happened. I have always been running using named pipes even though I thought since TCP/IP was an installed protocol library, it was being used. Since the webserver and Machine 1 were previously part of the same workgroup with shared logins all around and named pipes over NETBEUI, connection and security wasn't as much an issue but now that I am forcing the connections over TCP/IP, I think I may have been missing a config option all along with regard to TCP/IP.Interestingly enough, even when I re-enable named pipes on the SQL box, the webserver, still in the same workgroup, still won't connect.I am researching and troubleshooting as I speak and hope someone out there has a pearl for me. Thanks in advance.--Doug |
|
|
|
|
|
|
|
Network library issues