July 11, 2007 at 6:59 am
Windows 2000 Advanced Server (latest service pack)
SQL Server 2000 Enterprise Edition (8.00.2187)
1. Server can see other machines in network through Windows Explorer
2. Server can connect to other machines in network through ODBC
3. Other machine can't connect to my server through ODBC
4. Other machine can browse shared folders on server through Windows Explorer
5. Worked fine yesterday, ODBC went out sometime before midnight last night
6. No events pointing to problems in the event log.
7. Problem is fixed with reboot.
8. Automatic updates is turned off
9. All updates were downloaded and installed about 1 1/12 weeks ago.
10. Server can be seen through Enterprise manager on server
11. Query analyzer cannot connect from remote machine
12. Query analyzer can connect if ran from server
What should I be looking for to make sure that this doesn't happen again? (I know that there has been more updates since then)
July 11, 2007 at 7:28 am
Many places could have been wrong including a nearby router could have been the root issue. Problem is no way to really say how to prevent the unknown.
July 11, 2007 at 7:31 am
That's what my opinion is also, but I need to be able to say that it wasn't anything wrong with my server.
July 11, 2007 at 10:58 am
Well you cannot prove a negative, all you can do is check the EventLogs and any other log information you have available around the event. If you have nothing then the only thing can do is state it is under monitoring (which you should be doing) and all possibilities are being considered but nothing has turned up yet.
July 11, 2007 at 11:17 am
Thanks for the reply. Just trying to make sure I wasn't missing anything obvious. I didn't want to be quick to blame someone else.
July 11, 2007 at 2:25 pm
try ODBCping from external machine in aloop. See is there are discontinuities ;0
* Noel
July 12, 2007 at 6:22 am
I looked on my 7 and 2000 machines and I can't find ODBCping anywhere. I looked on my client installs also, nothing. I did some short research and found that it's not installed with 2005, so I'm not going to look there. Where do I get this utility?
July 16, 2007 at 7:59 am
I can't find anything wrong with my machine. Everywhere I looked pointed to a problem with the firewall or a network problem. Since the reboot fixed everything and I haven't seen a problem since I am going to assume that there was some firewall changes or something like that.
Thanks for all the help everyone gave. Hopefully this problem will not come back.
July 16, 2007 at 12:18 pm
Check the older versions of errorlog to confirm that TCP/IP protocol was functioning. If TCP/IP was not functioning, the SP4 install may have failed (with no error message) and the solution is to re-install SP4.
Since a reboot corrected the problem, this bug is probably not the cause but is just FYI:
SYMPTOMS
If you try to connect a clustered named instance of SQL Server through a firewall, and you use only the instance name (for example, SQL_Virtual_Name\Instance_Name) in the connection string, the connection fails.
WORKAROUND
Connect using a TCP IP and port number such as 10.218.122.161,1871
Bug description at http://support.microsoft.com/default.aspx?scid=kb;%5bLN%5d;318432
SQL = Scarcely Qualifies as a Language
July 16, 2007 at 12:42 pm
My server is stand-alone - nonclustered. SP4 was installed a long time ago and ODBC has been working fine before and after the install.
I set the Client Network Utility to TCP/IP years ago and have not changed it.
I double-checked and it still isn't changed.
Thanks for your suggestion.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply