altena
asked on
SQL-Server refusing all outside ODBC connections
For reasons unknown to me, my Development-setup suddenly
refuses all and any ODBC logins from other machines.
The database accepts all requests from the local machine.
This happened a few hours after i finished my pre-release
"Now format that hard-disk and recover the whole system" excercise. (after which it all worked for a while.)
An "A" if you can help me fix this before next week.
(Then I'll recover the DB again)
tnx
refuses all and any ODBC logins from other machines.
The database accepts all requests from the local machine.
This happened a few hours after i finished my pre-release
"Now format that hard-disk and recover the whole system" excercise. (after which it all worked for a while.)
An "A" if you can help me fix this before next week.
(Then I'll recover the DB again)
tnx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Tnx for the commments, Ill look into it monday.
I use SQL-Security only, since only components log into
the database. User access to the components is protected
by NT-security.
By the way, here is my e-mail, we weem to be doing a lot
of the same work: AltenaR@Yahoo.com.
I use SQL-Security only, since only components log into
the database. User access to the components is protected
by NT-security.
By the way, here is my e-mail, we weem to be doing a lot
of the same work: AltenaR@Yahoo.com.
Do you receive any error messages or entries in SQL error log or NT event log?
ASKER
I checked the security mode today: It doesnt seem to matter how I set it.
Only Logins from within the Domain are accepted (Using SQL-Server Security). The easiest way to test seems to be with the ODBC manager.
Access Refused. (or success if in the domain itself)
I could use some more hints this week...
Only Logins from within the Domain are accepted (Using SQL-Server Security). The easiest way to test seems to be with the ODBC manager.
Access Refused. (or success if in the domain itself)
I could use some more hints this week...
Here's a suggestion:
1. From your client workstation, Ping the IP address of you SQL Server. If you there is no response, setup your network connections in your Server Manager and add the Domain/s where the client machines are logged on. You should make sure that you can receive any response from you Server if you try to Ping from the client workstation after the Network has been setup.
2. If the client machine can receive response from you Server, try to map a drive or directory from the client to your Server.
You might see a message that asks for a login name and/or password. Enter the login name and/or password that you are using to access or bring up your Server(SA or Administrator, perhaps).
3. After getting a mapped drive, open you Control Panel\ODBC. Check your ODBC Drivers if you have one for SQL Server (check the versions). I you have one, Add a Data Source to the System DSN\System Data Sources.
Specify the Data Source Name(and keep it). The Server field should have the IP Address of your Server. If your SQL Server allows Trusted connection, set the Trusted connection to TRUE.
4. Specify the Database name you wish to have access to from you SQL Server.
If it doesn't work still, I suspect two the ff: are the reasons.
1. Network Connections. Your machines can't Ping your SQL Server.
2. ODBC SQL Driver is corrupt or it is of incorrect version. Reinstall it.
I had the same similar problems few weeks ago. Luckily, I was able to restore it.
Good Luck!
1. From your client workstation, Ping the IP address of you SQL Server. If you there is no response, setup your network connections in your Server Manager and add the Domain/s where the client machines are logged on. You should make sure that you can receive any response from you Server if you try to Ping from the client workstation after the Network has been setup.
2. If the client machine can receive response from you Server, try to map a drive or directory from the client to your Server.
You might see a message that asks for a login name and/or password. Enter the login name and/or password that you are using to access or bring up your Server(SA or Administrator, perhaps).
3. After getting a mapped drive, open you Control Panel\ODBC. Check your ODBC Drivers if you have one for SQL Server (check the versions). I you have one, Add a Data Source to the System DSN\System Data Sources.
Specify the Data Source Name(and keep it). The Server field should have the IP Address of your Server. If your SQL Server allows Trusted connection, set the Trusted connection to TRUE.
4. Specify the Database name you wish to have access to from you SQL Server.
If it doesn't work still, I suspect two the ff: are the reasons.
1. Network Connections. Your machines can't Ping your SQL Server.
2. ODBC SQL Driver is corrupt or it is of incorrect version. Reinstall it.
I had the same similar problems few weeks ago. Luckily, I was able to restore it.
Good Luck!
ASKER
Tnx for your Effort.
an E-mail messgae is in the mail-box :-)
an E-mail messgae is in the mail-box :-)
If the machines are logged on to another Machine(Domain) othet than your SQL Server, check if mapping exists between the client machines and your SQL Server. Otherwise,
the machines will be logged on as 'guest' - or 'sa' if they have administrator priviliges to NT.
Hope this helps.