Re: Can't connect to SQL server in Windows XP SP2
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Thu, 22 Sep 2005 23:38:34 -0600
Sometimes you can tell from the full text of the error
messages. You could turn on failed login auditing to see if
the login is hitting the server and failing. You can also
monitor for login failures in Profiler. You won't get a lot
of information on the login failure but enough to see if the
client is hitting the server.
-Sue
On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
<christopher_pankhurst@xxxxxxxxxxx> wrote:
>Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
>set to windows or sql authentication. I believe I opened them with the
>correct TCP/UDP combination. I also told windows firewall about
>sqlserver.exe, however I suspect that is more for outbound connections.
>
>I understand the security reasons why the normal error message has to be
>vague about sql server does not exist or access denied. Is it possible to
>configure SQL server into a diagnostic mode where it will tell the client
>that the sql server does exist but it was just that access was denied? This
>would help me narrow down the problem.
>
>If not, how can I tell if it is networking/firewall type problem or an SQL
>server security problem?
>
>Chris Pankhurst
>
.
- Follow-Ups:
- Re: Can't connect to SQL server in Windows XP SP2
- From: Christopher Pankhurst
- Re: Can't connect to SQL server in Windows XP SP2
- References:
- Can't connect to SQL server in Windows XP SP2
- From: Christopher Pankhurst
- Can't connect to SQL server in Windows XP SP2
- Prev by Date: Can't connect to SQL server in Windows XP SP2
- Next by Date: Re: Network Drives
- Previous by thread: Can't connect to SQL server in Windows XP SP2
- Next by thread: Re: Can't connect to SQL server in Windows XP SP2
- Index(es):
Relevant Pages
|