Post reply

just swapped over to a new server. now some users cant connect

  • September 14, 2006 at 8:05 am

    #173940

    i have just moved my database to a new, faster server, exact replica of the database, permissions and all.

    Users connect to the database via a vb application and an odbc connection.

    All but two users can now connect.

    The two users are in all the correct user groups that permissions on the database, but when they try to set up the odbc connection they get this error

     

     

    i think it is odd that this window doesnt mention the username, as when i try to create an odbc connection to a server i have no rights to, it shows the username in question here. has anyone any ideas as to why they cant connect to the server? i have been on their pc's and can find nothing wrong, and they could connect to the old server fine, which had all the same permissions. The server is using windows authentication, and this is what i select when i tried to create the connection on their pc's. its only 2 users out of about 20.  thanks all for any help

  • September 14, 2006 at 9:27 am

    #660439

    The error is not visible. Can you post it again?

  • September 14, 2006 at 9:46 am

    #660445

     

    here it is again.

  • September 14, 2006 at 10:47 am

    #660459

    You need to decide how you want users to connect and check how your server is setup.  Change auth mode of SQL Server to "Mixed Mode"

  • September 14, 2006 at 11:40 am

    #660482

    Like the last poster stated, change your connection types to Windows and SQL on the Security tab in Server Properties through Enterprise Manager.

    OT: It would be useful for the original poster of a thread to be able to mark his question as answered...

  • September 15, 2006 at 4:59 am

    #660648

    its not supposed to be anything except windows auth. it worked like that on the old server, the new server is set up for windows auth, yet it does not work for these 2 users, but it does work for everyone else

  • September 15, 2006 at 7:28 am

    #660689

    not sure how helpful this will be, but it's not passing the username, The person may be able to connect no problem, but for some reason it's passing a NULL for the username.

    I would try removing the DSN connection, and recreate it from scratch. It's minor and could fix the problem. (don't forget to test the connection after you set it up)

    If that doesn't work, look at what those 2 computers have that the others don't. If there's a firewall double check that the communication to the server is not blocked.

    Kindest Regards,

    Jon Kress
    Site I maintain at work. (Password protected)

  • September 15, 2006 at 10:32 am

    #660778

    Perhaps you need to migrate the login information from the old server, or else recreate their logins on the new.

  • September 15, 2006 at 5:23 pm

    #660844

    To me that looks like one of two problems. The user's windows account doesn't have an sql login (got missed in the change over?) or the user is not connecting to the domain / using a domain login on that pc whilst accessing the database.

  • September 15, 2006 at 6:27 pm

    #660854

    Could it be the sid for the user is different on the new server. Have u tried sp_change_users_login

    Thanks

    Sreejith

  • September 16, 2006 at 1:18 am

    #660872

    I would check the client connection on each of the problem user's computers. Make sure they are set to use TCP/IP instead of Named Pipes.

Viewing 11 posts - 1 through 10 (of 10 total)

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