October 8, 2010 at 12:39 am
Morning
I have a problem on a site connecting via a wireless network from Microsoft SQL Server Management Studio to the clients server. It takes a long time (not sure where to see the timeout period for connecting). After it has timed out, and I connects instantly.
I have checked the protocols and they are all enabled, the firewall is set OK.
I am able to see the rest of the network without problems.
Could someone please shed some light on what could cause this.
I have an app where the initial connection to the database over the network (I put in a cable to eliminate wireless issues) also takes long, and for now have to assume that the to problems are related
Thanks
Hylton
October 8, 2010 at 3:26 am
Could be the Windows firewall - it may be blocking tcpip (first timeout) then letting you through on another protocol. You can check by going into the settings on the ssms connection connection screen and choosing a different protocol
October 8, 2010 at 3:53 am
Have already checked the firewall. UDP and IP ports both open and the SQL Server Browser is running too.
October 8, 2010 at 4:34 am
Have put in a query running on a timer to poll the database every 30 sec from the client app (over wireless network). This action alone takes over 30 secs Machines are less than 5 meters from each other. Ping time is < 2ms so I doubt it has anything to do with the network
Database engine is SQL Express 2008.
Anything else I can look at? Please use simpler terms to describe an action. I am not dba and new to troubleshooting SQL Server issues.
"Provider=SQLOLEDB.1;Password=Admin;Persist Security Info=True;User ID=Admin;Initial Catalog=MeatProcessSTD;Data Source=DATABASE\\SQLEXPRESS;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=HYLTON;Use Encryption for Data=False;Tag with column collation when possible=False"
Default code generated by ATL Consumer used in connection string.
What else can I look at / provide to put this thing to bed?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply