Re: Where did the connections come from?
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Thu, 12 Apr 2007 10:31:56 -0600
You'll need to use a network sniffer - the IP address of the failed
login isn't logged in SQL Server 2000, just SQL Server 2005.
-Sue
On Wed, 11 Apr 2007 11:04:01 -0700, bing
<bing@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks much for the reply. Good to know. But why I don't see any connecting
IP or hostname? In EM, under Management->SQL Server Logs, when I click a log
entry, here is all the information I can see.
SQL Server Error Log message
Source: logon
Date: 2007-04-11 09:49:40.22
Message: Login failed for user '(null)'. Reason: Not associated with a
trusted SQL server connection.
I'm not clear if SQL 2000 has any log level settings anywhere.
Bing
"Russell Fields" wrote:
The login failure entries should have the IP address of the machine from
which the login was attempted. Look up that IP address on your domain and
see whose machine it is.
From the command prompt, this may help:
nbtstat -a the.ip.addr.ess
RLF
"bing" <bing@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:72B6EC6E-DFBE-4A5D-ADA4-480FCCC95B05@xxxxxxxxxxxxxxxx
Hi,
We use SQL 2000 on Windows 2003. In Enterprise Manager, when I looked
through the SQL server logs, I found a lot login failures. But how can I
know where those login failure connections came from?
Thanks much in advance for any insight.
Bing
.
- Follow-Ups:
- Re: Where did the connections come from?
- From: bing
- Re: Where did the connections come from?
- References:
- Re: Where did the connections come from?
- From: Russell Fields
- Re: Where did the connections come from?
- Prev by Date: RE: Running into security issues when attempting to deploy a Report Mo
- Next by Date: Multiple roles?
- Previous by thread: Re: Where did the connections come from?
- Next by thread: Re: Where did the connections come from?
- Index(es):
Relevant Pages
|