Connecting to Sql Server

I have been using Named Pipes to connect to our SQL server for almost a year now. Sporadically, connection to the database is dropped, I have checked cabling, UPS, switch, disconnected every piece of POS hardware it is still will occur every great once in a while. It usually occurs when trying to get the date and time, however I have seen it happen immediatedly after scanning an item too, and a slightly differerent error occurs.

Mainly I wonder if changing to a TCP/IP connection would help. I have been unable to get a connection to form between the server and a client this way. The sql server Network Utility is setup for TCP/IP, uses port 1433, 1433 is open and not blocked by any kind of firewall. I have tried using the name of the server and the ip address but still no luck. Is it worth even trying to pursue this avenue or will it not make a difference

Patrick

Reply to
Patrick
Loading thread data ...

Set up static IP addys for each machine. Put the server IP in the alias box on the client util at each machine that accesses the dB. Uncheck auto on port assignment. Make sure TCP/IP is listed prior to Named pipes in the list. It makes a big difference. Now your pointing straight at a machine and not searching UNC. mt

Reply to
Masta T

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.