Answered by:
remote login failed for user 'SAID\Guest'

Question
-
Hi All,
I have two connected computers via router, running under same home group. Each is a i3 pc running win 7. SQL Server 2008 is installed on one as server (back end) and Access 2007 on the other as client (front end), where tables in Access database were migrated to SQL Server via SQL Server Migration Assistant for Access (when Access database was located on server before it was moved to client). To try to access data on server, I went through 'SQL Server does not exist or access denied' problem, then after attempts to fix network parameters I got the message 'login failed for user 'SAID\Guest', where 'SAID' is the server name and 'Guest' is an account name that has been created on server as a result of my try to access data. First account was turned off, then I turned it on, while the server was (and still) under an administrative account. SQL Server authentication was 'Windows only', then I turned it to 'Windows and SQL Server', followed by restart of SQL Server. Message still persists. Any solution? Bear in mind I need to remain on server under the administrative account.
Best regards.
Prof. Dr. Said El Noshokaty
Wednesday, September 3, 2014 10:16 PM
Answers
-
Hi Prof,
We can create a SQL Server login based on a Windows principal(Windows authentication) or create a login that is saved on a SQL Server database(SQL Server authentication). So, please ensure you have create the correct login for the end user. For more informaton, please see:
Create a Login: http://msdn.microsoft.com/en-us/library/aa337562.aspxIn addition, maybe the UAC setting will casue this issue. Please run as administrator when you open SQL Server Management Studio. Please also take a look at the followng document:
Configure the remote access Server Configuration Option: http://msdn.microsoft.com/en-us/library/ms191464.aspx
Configure the Windows Firewall to Allow SQL Server Access: http://msdn.microsoft.com/en-us/library/cc646023.aspxElvis Long
TechNet Community Support- Proposed as answer by Papy Normand Wednesday, September 10, 2014 6:36 PM
- Marked as answer by Elvis Long Monday, September 15, 2014 7:18 AM
Wednesday, September 10, 2014 9:57 AM -
Hello ,
When you are trying to connect with Windows authentication on a computer belonging to a home group , you must have the same user ( Guest ) with the same password on both computer.
If you are using a SQL Server login named Guest , it is not enabled ( default configuration ) for any SQL Server instance. So you may connect but only with an enabled SQL Server login on the SQL Server instance you want to connect.
Have a nice day
Mark Post as helpful if it provides any help.Otherwise,leave it as it is.
- Proposed as answer by Elvis Long Wednesday, September 10, 2014 9:46 AM
- Edited by Papy Normand Wednesday, September 10, 2014 6:37 PM typo error corrected : it was guest instead gust
- Marked as answer by Elvis Long Monday, September 15, 2014 7:18 AM
Tuesday, September 9, 2014 7:38 PM
All replies
-
Hello ,
When you are trying to connect with Windows authentication on a computer belonging to a home group , you must have the same user ( Guest ) with the same password on both computer.
If you are using a SQL Server login named Guest , it is not enabled ( default configuration ) for any SQL Server instance. So you may connect but only with an enabled SQL Server login on the SQL Server instance you want to connect.
Have a nice day
Mark Post as helpful if it provides any help.Otherwise,leave it as it is.
- Proposed as answer by Elvis Long Wednesday, September 10, 2014 9:46 AM
- Edited by Papy Normand Wednesday, September 10, 2014 6:37 PM typo error corrected : it was guest instead gust
- Marked as answer by Elvis Long Monday, September 15, 2014 7:18 AM
Tuesday, September 9, 2014 7:38 PM -
Hi Prof,
We can create a SQL Server login based on a Windows principal(Windows authentication) or create a login that is saved on a SQL Server database(SQL Server authentication). So, please ensure you have create the correct login for the end user. For more informaton, please see:
Create a Login: http://msdn.microsoft.com/en-us/library/aa337562.aspxIn addition, maybe the UAC setting will casue this issue. Please run as administrator when you open SQL Server Management Studio. Please also take a look at the followng document:
Configure the remote access Server Configuration Option: http://msdn.microsoft.com/en-us/library/ms191464.aspx
Configure the Windows Firewall to Allow SQL Server Access: http://msdn.microsoft.com/en-us/library/cc646023.aspxElvis Long
TechNet Community Support- Proposed as answer by Papy Normand Wednesday, September 10, 2014 6:36 PM
- Marked as answer by Elvis Long Monday, September 15, 2014 7:18 AM
Wednesday, September 10, 2014 9:57 AM -
Dear Mr. Long and Mr. Norman,
Thank you for your excellent replies. It was very helpful. In SQL Server, as soon as I created a login name "SAID\Guest", with enabled login, every thing went OK. The remaining problem now is that the Windows icon representing internet access is now marked with red "x" in the two computers, although Internet Explorer is working fine. Also, Outlook stopped receiving mail in the two computers (send is OK), although Webmail is receiving fine. I'm sure this has nothing to do with login problem. Most probably it resulted from fixing some network parameters. I do not know exactly what parameter (s) caused this problem. Any idea? The following are the parameters I changed:
a) Via cliconfig.exe, I enabled both TCP\IP and Pipeline protocols and shared memory,
b) Via server network configuration, I enabled same protocols,
c) Via regedit.exe, I enabled IP routing,
d) Via WF.msc, I changed win firewall inbound rules to allow TCP connection to port 1433.
Two weeks ago I have reached the quota of disk space specified at the Internet service provider, which has been increased now. Do you think this has to do with the Outlook problem? If yes, what to do?
Best regards.
Prof. Dr. Said El Noshokaty
- Edited by Prof. Dr. Said El Noshokaty Friday, September 26, 2014 2:23 AM
Thursday, September 25, 2014 6:39 PM