Post reply

SQL Connection Issues

  • September 15, 2008 at 9:48 am

    #71979

    Background:

    1. Client and server are on a Workgroup.

    2. When registering server in Ent. Mgr by IP address everything is all well.

    3. When registering server in Ent. Mgr by ServerName the registration fails.

    4. I am able to ping the server by name so it is not DNS issue.

    5. I am able to map drives to the server and IP registratio works so not permissions issue.

    6. Other clients on workgroup are able to register server successfully when using both IP and Named instance.

    7. Problem exists on 1 client.

    8. Server is configured to accept connections over NP and TCP.

    Any ideas?

  • September 15, 2008 at 10:06 am

    #871868

    What's the problem?

  • September 15, 2008 at 10:08 am

    #871872

    You might want to try updating MDAC on that one client to see if that fixes the issue.

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • September 15, 2008 at 10:13 am

    #871882

    The problem is with connecting to the server by instance name rather than IP Address. When registering by using the IP of the server (#2), the connection is successful. However, when registering by using the Instance Name (#3), the connection fails.

  • September 15, 2008 at 10:14 am

    #871884

    Thanks for the suggesstion David. I'll try updating MDAC and let you know what happens. Thanks

  • September 15, 2008 at 10:14 am

    #871886

    Check the local "hosts" file. Be sure there's not an overriding entry there. Though I'd think that would prevent other issues.

    What about an alias in the client network utility? A default to a different protocol in EM for some reason?

  • September 15, 2008 at 10:34 am

    #871906

    Thanks for the help guys. We've got the issue resolved now.

    Steve, your post helped send me in the right direction. On the client, there was an alias specified within the Client Network Utility with the same alias as the server. After removing this alias entry from the client workstation, the connection was established successfully. I'm not sure how the entry got there. I'm assuming it was a user error while installing EM on the client WS.

    Thanks again.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply