GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Windows authentication problem
ProLiant Deployment and Provisioning
1847264
Members
4695
Online
110263
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2005 06:52 PM
09-01-2005 06:52 PM
Windows authentication problem
I have a network setup in which there are two domain controllers. There are 234 clients which logs to one of the domains. Both the servers are trusted as the users can log on to both the domains alternately.
The network also contains another Sql database server which is a part of this domain. I would like to keep this server in a workgroup which is not a part of this domain
I have found that when the server is changed from domain state to a workgroup the clients which connects the sql server are not able to connect even though they are in a same network.
The clients when tries to browse the server requsts a username and password which allows the users to connect the sql server.
I would like to give the users access to this server without a login prompt and would not like to share any of the drives as its contains the database.
Please give me a solution for the above senario.
The network also contains another Sql database server which is a part of this domain. I would like to keep this server in a workgroup which is not a part of this domain
I have found that when the server is changed from domain state to a workgroup the clients which connects the sql server are not able to connect even though they are in a same network.
The clients when tries to browse the server requsts a username and password which allows the users to connect the sql server.
I would like to give the users access to this server without a login prompt and would not like to share any of the drives as its contains the database.
Please give me a solution for the above senario.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2005 06:58 PM
09-06-2005 06:58 PM
Re: Windows authentication problem
Hi Sreedhar! There is two types of SQL authentication process - NT-based and own sql user database. Join SQL server to domain and enable NT authorization. Enjoy!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2005 04:02 AM
09-08-2005 04:02 AM
Re: Windows authentication problem
Sreedhar:
Part of the problem is that your SQL DB Server was set up for either mixed Authentication or Windows based Authentication. Since you took it out of the domain, it has no user database to look at except the local users.
If you create users on the local machine with exactly the same name and passwords as their domain accounts, SQL should allow the users to get right in since it is looking at the currently logged in account info for that user and his/her workstation and as long as it matches with the local info.... viola.
To keep the users from accessing any of the drives directly, make sure you remove any security permissions to any shares that would give them access.
Alternatively, you can put the DB box back into the domain as Ruslan suggests, but that defeats the purpose of wanting it OUTSIDE of the domain.
Steven
Part of the problem is that your SQL DB Server was set up for either mixed Authentication or Windows based Authentication. Since you took it out of the domain, it has no user database to look at except the local users.
If you create users on the local machine with exactly the same name and passwords as their domain accounts, SQL should allow the users to get right in since it is looking at the currently logged in account info for that user and his/her workstation and as long as it matches with the local info.... viola.
To keep the users from accessing any of the drives directly, make sure you remove any security permissions to any shares that would give them access.
Alternatively, you can put the DB box back into the domain as Ruslan suggests, but that defeats the purpose of wanting it OUTSIDE of the domain.
Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2005 10:26 PM
09-11-2005 10:26 PM
Re: Windows authentication problem
I have found the solution. The following user's should be created in the server as local users with the same password inorder to get the access.
The problem is solved.
Thanks for the help for those who have given me a resonable reply
The problem is solved.
Thanks for the help for those who have given me a resonable reply
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP