If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Microsoft SQL Server > Cant see SQL Server with Client ODBC

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 08-18-10, 06:59
HelpMePlease HelpMePlease is offline
Registered User
 
Join Date: May 2003
Location: UK
Posts: 233
Cant see SQL Server with Client ODBC

I have installed SQL Server 2008 on Windows Server 2003 OS and when I go to the client machine and try to access via an ODBC Driver I can not see any of the SQL Server 2008or any of its databases.

I have on the server checked the SQL Server Browser is running.
Shared Memory = Enabled
TCP/IP = Enabled
SQL Server is running

I have with cmdprompt run OSQL -L and I cannot see the MS Server intance which I belive to be MSSQLServer that I checked in services where it is Started.

Any ideas?
HelpMePlease
Reply With Quote
  #2 (permalink)  
Old 08-18-10, 09:40
MCrowley MCrowley is offline
Wage drone 24601
 
Join Date: Jan 2003
Location: Massachusetts
Posts: 4,899
Maybe Microsoft learned something about security in the last few upgrades. Try this instead;
Code:
osql /Syourservernamehere /E

Last edited by MCrowley; 08-18-10 at 09:41. Reason: Fixed code tag
Reply With Quote
  #3 (permalink)  
Old 08-18-10, 09:53
HelpMePlease HelpMePlease is offline
Registered User
 
Join Date: May 2003
Location: UK
Posts: 233
Quote:
Originally Posted by MCrowley View Post
Maybe Microsoft learned something about security in the last few upgrades. Try this instead;
Code:
osql /Syourservernamehere /E
I get a message saying Login failed for user
Reply With Quote
  #4 (permalink)  
Old 08-18-10, 10:41
MCrowley MCrowley is offline
Wage drone 24601
 
Join Date: Jan 2003
Location: Massachusetts
Posts: 4,899
Go to the SQL Server machine, and if you have login failure auditing on, then you should see a record of the login failure in SQL Server's errorlog. If you have login failure auditing on, and there is no mention in the errorlog of the actual login failure, then this is likely a firewall problem.
Reply With Quote
  #5 (permalink)  
Old 08-18-10, 15:29
HelpMePlease HelpMePlease is offline
Registered User
 
Join Date: May 2003
Location: UK
Posts: 233
I don't think I have an option for Audit although I am not 100% sure where I should chek this?
I am using SQL server 2008 standard.
Reply With Quote
  #6 (permalink)  
Old 08-18-10, 15:37
MCrowley MCrowley is offline
Wage drone 24601
 
Join Date: Jan 2003
Location: Massachusetts
Posts: 4,899
In SSMS right click on the server in the Object Explorer. Go to properties, then security. Login auditing should be in the middle somewhere.
Reply With Quote
  #7 (permalink)  
Old 08-18-10, 15:44
HelpMePlease HelpMePlease is offline
Registered User
 
Join Date: May 2003
Location: UK
Posts: 233
Ok in with you on there I have:

Windows Authentication Checked
and
Failed Logins Only Checked

Where can I view the report on this?

Thanks for your patience
Reply With Quote
  #8 (permalink)  
Old 08-18-10, 18:34
HelpMePlease HelpMePlease is offline
Registered User
 
Join Date: May 2003
Location: UK
Posts: 233
I have located the error log report using

EXEC sp_readerrorlog

Is this the correct way of doing so?
Reply With Quote
  #9 (permalink)  
Old 08-19-10, 08:25
smivers10 smivers10 is offline
Registered User
 
Join Date: Aug 2010
Posts: 1
I seem to be having the same problem.
Reply With Quote
  #10 (permalink)  
Old 08-19-10, 09:56
MCrowley MCrowley is offline
Wage drone 24601
 
Join Date: Jan 2003
Location: Massachusetts
Posts: 4,899
sp_readerrorlog is good enough. Try to log in from the remote client, then check the errorlog to see if a new failed login record comes up.
Reply With Quote
  #11 (permalink)  
Old 09-01-10, 14:11
HelpMePlease HelpMePlease is offline
Registered User
 
Join Date: May 2003
Location: UK
Posts: 233
Quote:
Originally Posted by smivers10 View Post
Got it working, thanks guys.
What did you do to get it working?
Reply With Quote
  #12 (permalink)  
Old 09-01-10, 16:54
77george77 77george77 is offline
Registered User
 
Join Date: Sep 2010
Posts: 1
Quote:
Originally Posted by MCrowley View Post
Go to the SQL Server machine, and if you have login failure auditing on, then you should see a record of the login failure in SQL Server's errorlog. If you have login failure auditing on, and there is no mention in the errorlog of the actual login failure, then this is likely a firewall problem.
Thanks MCrowley, this actually helps me out a lot.
Reply With Quote
  #13 (permalink)  
Old 09-01-10, 21:14
chris1946 chris1946 is offline
Registered User
 
Join Date: Sep 2010
Location: NH
Posts: 1
Quote:
Originally Posted by MCrowley View Post
Go to the SQL Server machine, and if you have login failure auditing on, then you should see a record of the login failure in SQL Server's errorlog. If you have login failure auditing on, and there is no mention in the errorlog of the actual login failure, then this is likely a firewall problem.
Thanks - Yup, dang firewall issue with me. That helped a lot.
Amazing how things change and start going wrong when you have ZERO configuration management in your environment and work with a bunch of cowboys! (and yes, I'm part of the problem too)
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On