I'm trying to make a mobile profile in Windows Server 2016, I created the user account on Active Directory Users and Computers and i set the path to profile like this: http://prntscr.com/hg8joh
Now I am trying to log in with that user account from a Windows 10 client but it shows the following error:
The security database on the server does not have a computer account
for the trust relationship of this station.
I can log in with the admin account and the both computers can do ping to each other so I do not know what to do. Help!
SOLVED POST
I think I just needed to put the Server IP on the Preferred DNS server on the client computer so now it's solved :D
Related
Computer account is not able to login to SQL Server 2017 Express on the same machine. We are getting an error on connection stating that the login failed due to not being able to open the specified database. The database exists and is query-able, the computer account has SYSADMIN role and is also mapped directly to the database.
We've tried using different connection strings, different bitnesses, different accounts(LocalServer, NetworkService, ...), different processes, different databases and different database roles. All network protocols are enabled too.
Really just need this to work with the computer account. We can't create a domain account or local windows account (which does work when tested). This usually works just fine but something is amiss.
The computer account never signs in locally. It's a limitation of the error message that it appears that it's the computer account connecting, as it's kind of a reverse-lookup of the account attempting the connection.
You need to create a login for the local account actually attempting the connection, which will be something like :
CREATE LOGIN [NT AUTHORITY\NETWORK SERVICE] FROM WINDOWS
or
CREATE LOGIN [NT Service\MSSQLServerOLAPService] FROM WINDOWS
I have SQL Server 2014 locally on my machine. Windows did an update and somehow my user account got corrupted. I created a new user account on my machine with admin privileges and SQL Server automatically added the new user account as a sys admin. I found this out when I logged onto SSMS with my old windows account. I also noticed that the new user account was added with a SQL Server authentication. I would like the new account to have Windows authentication but somehow that is grayed out. Does any one know why? Also, when I try to login with my new account and SQL Server Authentication, I am getting a "Can not connect to local error"
When you created the new account on your machine it was not created as an AD account. It was most likely created as a local user account on your machine. Since it is not tied to an AD Account, Windows Authentication is not an option as Active Directory is a requirement.
I figured it out. I just had to create another system admin account for myself with the new windows account and use that to log in.
A user is trying to connect to an Azure SQL Database via SQL Server Management Studio (SSMS v16.5.1).
The user's current IP address is not listed in the Azure SQL Server's firewall rules.
Because of this the user is shown the New Firewall Rule dialog.
When the user signs in using their Azure Active Directory (Azure AD) credentials they get an error message saying:
Account has no subscriptions
Clicking "Details" shows:
We experienced issues in connecting to Azure
Additional information:
login account does not have Azure subscriptions.
(Microsoft.SqlServer.Management.ApplicationAuthenticationManagement)
Why is the user getting this error message and how can they add a new firewall rule for their IP address?
Azure support have shared the below with me, based on an Azure documentation article.
Given an Azure SQL Server, only the Active Directory admin or SQL Server admin have permissions to add firewall rules at the server level.
The above error message (somewhat obscurely) indicates that the user is neither.
My personal experience also suggests that Azure AD accounts that are assigned as Subscription Co-administrators can also set firewall rules.
If, and only if, giving the user permissions is appropriate, this can be done by one of three ways:
Specifying the user as the SQL Server admin.
Setting the server's Active Directory admin to be an Azure Active Directory Group and making the user's AD account a member of this group.
Making the user a Co-administrator for the Subscription via https://manage.windowsazure.com/
Be sure to understand the security implications of each option before taking action.
Look at these two tutorials that will be live shortly (later on 1/13/2017):
https://learn.microsoft.com/en-us/azure/sql-database/sql-database-control-access-sql-authentication-get-started
https://learn.microsoft.com/en-us/azure/sql-database/sql-database-control-access-aad-authentication-get-started
These tutorials discuss using server and database level firewall rules with SQL Server authentication and Azure Active Directory authentication.
I hope these help,
Carl
In Azure Portal (https://portal.azure.com/#resource/subscriptions/{Your-GUID}/resourceGroups/AdminPortalDev/providers/Microsoft.Sql/servers/wjidentityserver/databases/{Your-DATABASE_SERVER}/overview )
Select your database
Select "Overview"
"Set server firewall" on the toolbar
Add client IP on the toolbar
Then you will be able to connect from the new IP address.
I was able to add the IP address without being administrator.
The steps in more details are described in https://learn.microsoft.com/en-us/azure/sql-database/sql-database-security-tutorial#create-a-server-level-firewall-rule-in-the-azure-portal.
Other question Client with IP addres is not allowed to access the server Azuredb describes more meaningful message and the same resolution.
I would like to connect to the company's SQL Server 2014, where I am working at, with my computer using windows authentication. I need this to deploy from my machine SSIS packages, without having to access remotely our server's machine.
I have been trying to add a login with my computer name plus my user as MY_COMPUTER\USER, but I keep getting an error, which tells me the it wasn't able to find the domain of my computer.
So, how can I connect my computer to our SQL Server using a windows authentication?
CREATE LOGIN [DomainName\Username] FROM WINDOWS WITH DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english]
Your local computer name isn't part of this at all. DomainName is the name of the windows network domain name that your SQL server would be joined to in this case. If your SQL server is not joined to a domain then that is a different scenario and I can't test but I would think you would use the computer name of the SQL Server in place of domain name and then the name of the local user....
Anyway, do you know your Domain Name?
DomainName\Username
If not joined to a domain try
SqlServerComputername\Username
We have a windows network domain joined with our SQL Server. I had already created a user for my computer on our windows network, but I wasn't logging in using the new user.
I'm facing a huge issue, I cannot work in our AD anymore, because windows cannot find the dsa.msc file.
Usually, I run Active Directory Users and Computers as my admin account. When entering credentials, I have the following:
If I connect my self from an other computer, this is working fine and I can deal with users & groups.
I've change my password, reinstall all that is related to AD managment, but I can't even imagine restaging my machine. I've deleted temp files also.
This is clearly not a account issue. Even my server team could not help.
From which computer are you trying to do this?
Is this a client computer or a server? Generally you cannot open dsa.msc from a client computer if the Remote Server Administration Tools are not installed on it.
Is this a Domain Controller?