Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver Subject: Re: Unable to connect Client to SQL Server Date: Wed, 12 Mar 2014 21:16:57 +0100 Organization: Erland Sommarskog Lines: 29 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Info: mx05.eternal-september.org; posting-host="fd3d6d0229f14a752f017d8f9903addd"; logging-data="30785"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18q/kSwavEDKeLEU3qE4KnP" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:3GpVqADChcWVewBGRkXEV/XUG94= Xref: csiph.com comp.databases.ms-sqlserver:1724 Bruno Campanini (brunocam@libero.it) writes: > New things, with: > > sqlcmd -S P900 -U sa -P brunocam -l 50 > > I get > 1> and after Enter > 2> and so on > > I thing I get connected... and then? > How can I pass the parameter -l 50 from inside Access? Add "Connect Timeout=50" to the connection string. It appears that your network configuration is having, well, problems. I have experienced similar at home as well. I had some awful ping times between my laptop and my desktop. The easy way out was to disable IPv6, but I flatly refused, and spent some time fighting with my router about it. It works now, I think. The default connect timeout is 15 seconds, and that should be enough in normal environments. Great to hear that you were able to resolve the issue! -- Erland Sommarskog, Stockholm, esquel@sommarskog.se