Results 1 to 9 of 9
  1. #1
    Join Date
    Jun 2006
    Posts
    8

    Unanswered: ODBC problem - see out, but can't see in

    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)

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    You don't have DHCP turned on on the server, do you?

  3. #3
    Join Date
    Jun 2006
    Posts
    8
    Just client not server. This machine isn't a domain controller. It logs into another domain and isn't part of a cluster.

  4. #4
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    On point 7, which machine (client or server) is rebooted to fix the problem? Also, can you check on the server using the Server Network Utility tool to see what protocols are supported there, and in what order? Do the same on the client using the Client Network Utility (cliconfg.exe, if it does not show up in Programs). Also check for aliases on the client (same utility, different tab).

  5. #5
    Join Date
    Jun 2006
    Posts
    8
    Server rebooted to fix problem.
    Server - Only protocol enabled is TCP/IP.
    Server - No aliases.
    Client - TCP/IP & Named Pipes
    Client - No aliases.

  6. #6
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Next time you get the error, check the exact wording of the message. If possible post it. I am out of ideas for the moment.

    There are no firewalls, or other filtering devices between the two machines, right?

  7. #7
    Join Date
    Jun 2006
    Posts
    8
    It worked fine till last night. I haven't applied any hotfixes to SQL server in months.

    The error was the same one that you get when you type the name of the server wrong or put in the wrong password - 'Server does not exist or access denied'.

    I can't verify it, but I think some network 'tweaking' has been happening in the area. I can just blame it on the network guys, but I need to be sure that there's nothing wrong with my server.

  8. #8
    Join Date
    Jun 2006
    Posts
    8
    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.

  9. #9
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    Did you try creating an Alias?

    Could be a DNS thing
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •