Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Cannot connect using mixed authentication Expand / Collapse
Author
Message
Posted Monday, April 15, 2013 7:53 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Saturday, August 23, 2014 6:13 PM
Points: 144, Visits: 524
We are attempting to deploy a SQL Server Express 2012 application in a network using Workgroup networking, and as a result are having to use SQL Server logins rather than Integrated security. All works as it should when connected to the PC running SQL Server. However when we attempt to connect from another Win7 workstation using ODBC, we either get timeout errors, or we get the message that SQL Server actively rejected our connection attempt (we are using Native Client 11 as the ODBC driver, both on the SQL Server PC, and on the network PC). We are also getting Error 8 - "The SQL Server Browser service was unable to process a client request" logged in the Application Log on the SQL Server PC in some attempts, but not in others. Any suggestions on what might be causing the problem? We've done this sort of configuration previously using SQL Server Express 2008 and gotten it to work, but we been banging our heads on this for 3 weeks now, and exhausted all of our usual bag of tricks. Thanks in advance.

Wendell


Wendell
Colorful Colorado
You can't see the view if you don't climb the mountain!
Post #1442558
Posted Monday, April 15, 2013 11:52 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 6:54 PM
Points: 1,193, Visits: 1,666
Any errors in the SQL Server log? Also, what happens when you try
telnet servername 1433
from the Win7 machine? It should allow the connection and give you a blinking prompt, otherwise it will just fail to connect and you'll know its a firewall or network connectivity issue.
Post #1442595
Posted Tuesday, April 23, 2013 4:34 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Saturday, August 23, 2014 6:13 PM
Points: 144, Visits: 524
Well, it seems it has to be a connectivity issue. I disabled all the firewalls (the machine attempting to connect has two - Windows and Kaspersky), and still cannot get telnet to work. However it works just fine on port 80. I suspect it is some sort of setting in the DLink router, but what it is remains a mystery. I'll post the cause if we ever find it.

Wendell
Colorful Colorado
You can't see the view if you don't climb the mountain!
Post #1445714
Posted Wednesday, April 24, 2013 8:46 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, August 18, 2014 9:23 AM
Points: 46, Visits: 232
Hi WendellB,

Know this was yesterday, but as a thought have you checked through all of the config tool settings around the protocols and the ports? I recall having a weird problem with Express where the browser wouldn't pass off to it when it was running on a dynamic port and you might be seeing the same sort of thing. Of course you might not too, but it's worth a shot :)
Post #1446032
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse