Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I need some assistance from network experts who also are familiar with SQL 2000.
On the server end, Windows 2000 Server I have a couple SQL back end databases. Windows 2000 Server is at Service Pack 2 and SQL 2000 is patched up to date.
On the client end, Windows 98SE. Two clients loaded, the Novell NetWare 32 Client v3.32 SP2 and the Client for Microsoft Networks. A supervisor (has his own accounts) and operators (share a generic account) are receiving the error: "Primary SQL Server Not available-000. Please contact your network administrator. After acknowledging the error, a red x over the mapped drive in my computer is seen. If you go to a Dos prompt the server can be pinged by name and by ip address. Restarting the computer solves the problem. End users are being instructed now to do full restarts at shift change. Previously, they would click "Close all programs and log on as a different user. It appears this is causing the problem as well as closing and restarting the fron end Access 97 application. Steps taken so far:
Client:
1> Applied MDAC 2.7 SP1
2> Disabled power save on enbedded nic
3> Verified duplex settings are the same on switch and on computer.
4> Swapped out motherboard on computer just in case the enbedded nic was the problem.
5> Loaded NetBeui.
6> Re-terminated cabling at wallplate.The interesting thing about this is the end user has never had a problem accessing resources on the NetWare server, never.
Please advise if you feel you can help. As far as SP3 on the server, can't do it as the other admins of the server don't want to bring it up to that patch level yet. By the way this is the only computer on the LAN having problems.

test the cable in the wall. Make sure the dns settings are correct. If only this wkst swap it with another to confirm the internal cabling as the issue. Otherwise the problem will go with the workstation. And then you will know where to look for sure.

If your referring to an expensive cable tester, I don't have a budget for it. As far as swapping the computer with another like computer, I took a like computer and imaged it to the network with Ghost. I then dumped the image on the computer that has been problematic. Sorry, I am not hauling a heavy computer around to swap out. I will check the DNS settings, but I think they are good. Another thing with the cabling issue, why no problems with the NetWare server, but problems with the Windows 2000 server?

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |