msde problems connecting to database

  • Problem with connecting clients to a msde database connection time outs error forms on clients, problem does not exist if the client is run from the same machine as the msde database can anyone help as this is becoming a pain. 🙂

  • Well, the first step is to make sure the timeout is due to physical location, not database performance. If you have a bad/slow network connection, getting lots of collisions, etc, that might explain why slower from a different machine. Most timeouts are data related, not good enough index plan or bad statistics. In addition, MSDE has a limit of the number of statements that can be executing at once, so it might just be queuing there.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

  • if you have a slow network maybe you should change the packet size. Also check the client and server net library. In slow networks TCP/IP works better than Net Beui

  • Make sure you are running TCP/IP on the clients and do a test ping to see how long a response takes.

  • Well You are probably using named pipes as the protocol. So if you want this to work,

    Create a drive mapping from the client to the server. That way you know for sure you can reach the MSDE machine via Named pipes.

    If this doesn't work, See if both machines have TCP/IP installed. Next see if you can ping the MSDE machine by name AND ip number on the client machine and vice versa.

    If that works you should get the client network utillity on the Client and delete the Named pipes protocol.

    Next Get the Server Network Utillity on the MSDE machine, and delete Named pipes.

    Then it really should work.

    If that doesn't work...........

    Check what authentication mode you are running on the MSDE machine. Trusted authentication will not work if the MSDE machine is a WIN 98 Machine......

  • Ya --- TCP/IP = no problem. what was your resolution?

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

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