connect from ASP app: authentication

Showing posts with label authentication. Show all posts

Sunday, March 25, 2012

Can't Generate SSPI

Hi,
I'm trying to configure a Windows Authentication SQL Server user and I get a
message that the compuetr can;t generate an SSPI connection. The Enterprise
Manager then won't connect to the SQL Server. The VS.NET 2003 enviroment, w
hich is the user preferred
connection enviroment to the SQL Server also won't connect.
The user has SQL Server 2000 Develop edition SP3a installed on the computer
and we are trying to connect to a SQL Server 2000 Enterprise edition SP3a. T
he user also has on his computer VS6 and VS.NET 2003.
Does any one know the cause of this problems?
Thanks,Try these links:
http://www.sqlservercentral.com/col...kb;en-us;811889
Ray Higdon MCSE, MCDBA, CCNA
--
"Shai Goldberg" <gshai(removethis)@.shamir.co.il> wrote in message
news:B52289F3-1E9F-410F-B49C-BCB73C80D1AD@.microsoft.com...
> Hi,
> I'm trying to configure a Windows Authentication SQL Server user and I get
a message that the compuetr can;t generate an SSPI connection. The
Enterprise Manager then won't connect to the SQL Server. The VS.NET 2003
enviroment, which is the user preferred connection enviroment to the SQL
Server also won't connect.
> The user has SQL Server 2000 Develop edition SP3a installed on the
computer and we are trying to connect to a SQL Server 2000 Enterprise
edition SP3a. The user also has on his computer VS6 and VS.NET 2003.
> Does any one know the cause of this problems?
> Thanks,|||Thanks,sql

Wednesday, March 7, 2012

Can't Create and Connect to a new Database (.mdf file)

Unfortunately I was sent to this product by my Hosting Site since all I was trying to do was Create and Manage a User Login with authentication to my subsites in MS Frontpage. (rant: Why doesn't Frontpage support this technology?)

Anyway, I have now spent (wasted?) 8 hours downloading, installing, and tyring to configure SQL Express along with MS Visual Web Developer Express for ASP.NET 2.0 ... For the life of me I can't find detailed configuration informatin and setup information to build a SIMPLE database to connect to the VW product. Folk: this HAS to be simpler to do than what you present in the product! This is way too difficult to deal with compare with frontpage.

Is there a simple "how to" link someplace that is specific enough to preclude me from uninstalling this entire suite ?

Hi Cody,

Sounds like you've already put some effort into this, so I really hate to redirect you again, but I believe it will be worth your while to go over and check out ASP.net web. This site is all about web development using ASP.NET and Visual Web Developer. You will find a number of resources on the site which I think should help you. Of particular interest, I think, will be the How Do I video series and the ASP.NET 2.0 Quickstart tutorials. Both of these are available from the Learn tab if the links above don't work and contain samples about handling logins.

Hope this gets you moving in the right direction.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

Friday, February 24, 2012

Can't connect using sa login and don't have any other administrator logins

I connected successfully in SQL Server Management studio using the 'sa' login and changed the authentication mode to Windows NT because I could not connect using my windows login but now I can't get any connection at all because 'sa' is no longer trusted.

I changed the loginmode registry setting to 2 and rebooted my PC but this has made no difference.

Can anyone help me get the 'sa' login back?

Unless you explicitly removed the default privileges (members of sysadmin) to builtin\Administrators, you should be able to connect to SQL Server using a Windows account that is member of the machine administrator s group.

NOTE: If you are using Windows Vista, you probably have UAC enabled, and you will need to use a full administrator token before connecting to SQL Server in the way I described above. You can use the right-click menu in Windows to “Run as Administrator” in order to get an unrestricted token before connecting to SQL Server.

Let us know if this information helped.

-Raul Garcia

SDE/T

SQL Server Engine

|||

I am on Windows XP, the engine is SQL Server 2000 and I am using SQL Server 2005 Management Studio. The problem started when I upgraded the software we are developing to the latest version which I suspect may have removed the existing SQL Server logins which did have full rights. It also changed the login mode from Windows Authentication to System Administration. My big mistake was to change the mode back to Windows Authentication in SQL Server Management Studio before checking the other logins and it was then that the problems started. My windows username has administrative rights but I still couldn't connect to the server using windows login.

I tried just now changing the LoginMode in the registry back to 1 and starting windows again but I still can't log in with 'sa'. I did notice that the default user registry key is set to 'guest' but don't know if that makes any difference.

I think that I may have to resort to re-installing SQL Server 2005. I would prefer not to do that but It doesn't really matter if I lose my local database as I do have a copy of it elsewhere.

Can you think of any other solutions?

|||

Try switching the LoginMode value in the registry to 2 (if I remember correctly, 2 should mean "Mixed mode"), restart SQL Server and try to connect with the SA login again.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thanks, that worked perfectly.

FYI...

The reason it didn't work the first time is that I changed it in registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\MSSQLServer\LoginMode

which I assume is the key for SQL Server Management Studio 2005 but I didn't realise that there was another key, i.e.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\LoginMode

which would be for the SQL Server 2000 engine.

Anyway, I have learned my lesson now and am going to add my windows login.

Can't connect to the sql server

I have machine A hosting SQL Server XXX, and B tries to access XXX. XXX
use mixed authentication mode. A and B are in the same LAN and
workgroup.
B use Sql Server username and passoword to access the XXX sql server.
In ADO.Net and Visual Studio .Net, if I first register the Server A on
Visual Studio .Net IDE, then I can connect to XXX by the pre-set sql
server username and password, otherwise it failed.
Or, if I first connect to Server A by visiting network connections to
give A's windows username and password, then I can connect to XXX by
the pre-set sql server username and password.
However, if I don't first gain access A, then I can't connect XXX by
the pre-set sql server username and password.
What's the problem here?
Thanks;Can you describe your installation more fully? Which edition of SQL
Server 2005 (I assume it's SQL Server 2005) are you using? Which CTP?
Thanks
Andrew Watt
MVP - InfoPath
On 9 Oct 2005 11:55:29 -0700, zhenghong04@.yahoo.com wrote:

>I have machine A hosting SQL Server XXX, and B tries to access XXX. XXX
>use mixed authentication mode. A and B are in the same LAN and
>workgroup.
>B use Sql Server username and passoword to access the XXX sql server.
>In ADO.Net and Visual Studio .Net, if I first register the Server A on
>Visual Studio .Net IDE, then I can connect to XXX by the pre-set sql
>server username and password, otherwise it failed.
>Or, if I first connect to Server A by visiting network connections to
>give A's windows username and password, then I can connect to XXX by
>the pre-set sql server username and password.
>However, if I don't first gain access A, then I can't connect XXX by
>the pre-set sql server username and password.
>What's the problem here?
>Thanks;

Can't connect to the sql server

I have machine A hosting SQL Server XXX, and B tries to access XXX. XXX
use mixed authentication mode. A and B are in the same LAN and
workgroup.
B use Sql Server username and passoword to access the XXX sql server.
In ADO.Net and Visual Studio .Net, if I first register the Server A on
Visual Studio .Net IDE, then I can connect to XXX by the pre-set sql
server username and password, otherwise it failed.
Or, if I first connect to Server A by visiting network connections to
give A's windows username and password, then I can connect to XXX by
the pre-set sql server username and password.
However, if I don't first gain access A, then I can't connect XXX by
the pre-set sql server username and password.
What's the problem here?
Thanks;
Can you describe your installation more fully? Which edition of SQL
Server 2005 (I assume it's SQL Server 2005) are you using? Which CTP?
Thanks
Andrew Watt
MVP - InfoPath
On 9 Oct 2005 11:55:29 -0700, zhenghong04@.yahoo.com wrote:

>I have machine A hosting SQL Server XXX, and B tries to access XXX. XXX
>use mixed authentication mode. A and B are in the same LAN and
>workgroup.
>B use Sql Server username and passoword to access the XXX sql server.
>In ADO.Net and Visual Studio .Net, if I first register the Server A on
>Visual Studio .Net IDE, then I can connect to XXX by the pre-set sql
>server username and password, otherwise it failed.
>Or, if I first connect to Server A by visiting network connections to
>give A's windows username and password, then I can connect to XXX by
>the pre-set sql server username and password.
>However, if I don't first gain access A, then I can't connect XXX by
>the pre-set sql server username and password.
>What's the problem here?
>Thanks;

Can't connect to SQL server in Windows XP SP2

Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
set to windows or sql authentication. I believe I opened them with the
correct TCP/UDP combination. I also told windows firewall about
sqlserver.exe, however I suspect that is more for outbound connections.
I understand the security reasons why the normal error message has to be
vague about sql server does not exist or access denied. Is it possible to
configure SQL server into a diagnostic mode where it will tell the client
that the sql server does exist but it was just that access was denied? This
would help me narrow down the problem.
If not, how can I tell if it is networking/firewall type problem or an SQL
server security problem?
Chris Pankhurst
Sometimes you can tell from the full text of the error
messages. You could turn on failed login auditing to see if
the login is hitting the server and failing. You can also
monitor for login failures in Profiler. You won't get a lot
of information on the login failure but enough to see if the
client is hitting the server.
-Sue
On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:

>Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
>set to windows or sql authentication. I believe I opened them with the
>correct TCP/UDP combination. I also told windows firewall about
>sqlserver.exe, however I suspect that is more for outbound connections.
>I understand the security reasons why the normal error message has to be
>vague about sql server does not exist or access denied. Is it possible to
>configure SQL server into a diagnostic mode where it will tell the client
>that the sql server does exist but it was just that access was denied? This
>would help me narrow down the problem.
>If not, how can I tell if it is networking/firewall type problem or an SQL
>server security problem?
>Chris Pankhurst
>
|||Thanks, I'm not sure how to turn on login auditing, but using profiler is a
good idea. I wonder why I didn't think of it.
Chris Pankhurst
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.4ax.com... [vbcol=seagreen]
> Sometimes you can tell from the full text of the error
> messages. You could turn on failed login auditing to see if
> the login is hitting the server and failing. You can also
> monitor for login failures in Profiler. You won't get a lot
> of information on the login failure but enough to see if the
> client is hitting the server.
> -Sue
> On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
> <christopher_pankhurst@.hotmail.com> wrote:
is[vbcol=seagreen]
This[vbcol=seagreen]
SQL
>
|||For login audits, in Enterprise Manager, right click on the
server and select properties. Go to the Security tab and you
can set the audit level for logins (success, failure or
all). You need to restart the service for the settings to
take effect.
-Sue
On Mon, 26 Sep 2005 08:32:32 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:

>Thanks, I'm not sure how to turn on login auditing, but using profiler is a
>good idea. I wonder why I didn't think of it.
>Chris Pankhurst
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.4ax.com.. .
>is
>This
>SQL
>

Can't connect to SQL server in Windows XP SP2

Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
set to windows or sql authentication. I believe I opened them with the
correct TCP/UDP combination. I also told windows firewall about
sqlserver.exe, however I suspect that is more for outbound connections.
I understand the security reasons why the normal error message has to be
vague about sql server does not exist or access denied. Is it possible to
configure SQL server into a diagnostic mode where it will tell the client
that the sql server does exist but it was just that access was denied? This
would help me narrow down the problem.
If not, how can I tell if it is networking/firewall type problem or an SQL
server security problem?
Chris PankhurstSometimes you can tell from the full text of the error
messages. You could turn on failed login auditing to see if
the login is hitting the server and failing. You can also
monitor for login failures in Profiler. You won't get a lot
of information on the login failure but enough to see if the
client is hitting the server.
-Sue
On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:

>Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
>set to windows or sql authentication. I believe I opened them with the
>correct TCP/UDP combination. I also told windows firewall about
>sqlserver.exe, however I suspect that is more for outbound connections.
>I understand the security reasons why the normal error message has to be
>vague about sql server does not exist or access denied. Is it possible to
>configure SQL server into a diagnostic mode where it will tell the client
>that the sql server does exist but it was just that access was denied? This
>would help me narrow down the problem.
>If not, how can I tell if it is networking/firewall type problem or an SQL
>server security problem?
>Chris Pankhurst
>|||Thanks, I'm not sure how to turn on login auditing, but using profiler is a
good idea. I wonder why I didn't think of it.
Chris Pankhurst
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.
4ax.com...
> Sometimes you can tell from the full text of the error
> messages. You could turn on failed login auditing to see if
> the login is hitting the server and failing. You can also
> monitor for login failures in Profiler. You won't get a lot
> of information on the login failure but enough to see if the
> client is hitting the server.
> -Sue
> On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
> <christopher_pankhurst@.hotmail.com> wrote:
>
is[vbcol=seagreen]
This[vbcol=seagreen]
SQL[vbcol=seagreen]
>|||For login audits, in Enterprise Manager, right click on the
server and select properties. Go to the Security tab and you
can set the audit level for logins (success, failure or
all). You need to restart the service for the settings to
take effect.
-Sue
On Mon, 26 Sep 2005 08:32:32 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:

>Thanks, I'm not sure how to turn on login auditing, but using profiler is a
>good idea. I wonder why I didn't think of it.
>Chris Pankhurst
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.
4ax.com...
>is
>This
>SQL
>

Tuesday, February 14, 2012

cant connect to my databse in lan

Hi all!

I am using MSSQL 2005 and asp.net .I have made a web application that needs to be run in LAN.The authentication used is windows authentication.The problem is that when in LAN I cannot connect to the database The sqlexception error shows that the connection is closed.Is there any thing that i am missing?Any configurations i need to make??Is this the issue of remote connections?? Please help!!I am new and dont knw much abt it .Thanks!!

Quote:

Originally Posted by dotnetgal

Hi all!

yes you have to setup the Security of SQL Server to accept Mix Authentication|||

Quote:

Originally Posted by ck9663

yes you have to setup the Security of SQL Server to accept Mix Authentication

hello !!

Thanks for the reply.But how am i to set it up to accept Mix Authentication?|||

Quote:

Originally Posted by dotnetgal

hello !!

Thanks for the reply.But how am i to set it up to accept Mix Authentication?

open enterprise manager. right click on your server. choose properties. a dialog box will appear. choose Securtiy. on Server Authentication, choose SQL Server and Windows authentication mode|||

Quote:

Originally Posted by ck9663

open enterprise manager. right click on your server. choose properties. a dialog box will appear. choose Securtiy. on Server Authentication, choose SQL Server and Windows authentication mode

thanks!!I did it but dtill the problem persists!!Any idea?

Sunday, February 12, 2012

Can't connect to database due to Windows authentication

I am using SQLServer 2000 and for reasons unknown the name of the server got
changed so that it did not match the name of the machine. I discovered this
when our application could not connect to the database.
I changed the servername using:
exec sp_dropserver 'SSM_6000_A', 'droplogins'
exec sp_addserver 'SSM_6000_C', 'local'
I stopped and started the server and when I checked the name of the server
using
SELECT @.@.SERVERNAME
I got the correct name, SSM_6000_C
I still could not connect to the database but I thought I had to recreate
the logins.
I deleted one of the users and logins and tried to recreate it and I get the
error:
"ERROR15401: WindowsNT user or group 'user-name' not found. Check
the name again."
The server is on our network. I can go to folders, etc. on the network once
I log in using my network account.
What is wrong?
Is there someplace within SQLServer that did not get the server name change?
Where can I check?
I went to a DTS package and was configuring a query in an Execute SQL Task
and the server name was the old name.
Thanks for your help!!
GloriaTo create new logins you can use EM, but login are only existing windows
user names, so if you use windows only authentication, you can add only
existing windows user names for new logins.
Regards,
Daniel
"Gloria" <Gloria@.discussions.microsoft.com> wrote in message
news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> I am using SQLServer 2000 and for reasons unknown the name of the server
got
> changed so that it did not match the name of the machine. I discovered
this
> when our application could not connect to the database.
> I changed the servername using:
> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> exec sp_addserver 'SSM_6000_C', 'local'
> I stopped and started the server and when I checked the name of the server
> using
> SELECT @.@.SERVERNAME
> I got the correct name, SSM_6000_C
> I still could not connect to the database but I thought I had to recreate
> the logins.
> I deleted one of the users and logins and tried to recreate it and I get
the
> error:
> "ERROR15401: WindowsNT user or group 'user-name' not found. Check
> the name again."
> The server is on our network. I can go to folders, etc. on the network
once
> I log in using my network account.
> What is wrong?
> Is there someplace within SQLServer that did not get the server name
change?
> Where can I check?
> I went to a DTS package and was configuring a query in an Execute SQL Task
> and the server name was the old name.
> Thanks for your help!!
> Gloria
>|||Hi Daniel,
I only want to create user names from Windows logins. The problem is EM
won't let me create Windows logins.
When I try to create a new login by picking a name from the domain list, I
get the error message:
"Error15401:WindowsNT user or group 'domain\user_name' not found.
Check the name again."
I checked the servername to make sure after I changed it that if matches the
machine name and it does. Is it possible that somewhere in the bowels of
SQLServer the servername did not get changed and this mismatch is causing the
problem?
If so, how can I check this?
Does it check in the registry somewhere the name of the server?
Thanks again,
Gloria
"Daniel Joskovski" wrote:
> To create new logins you can use EM, but login are only existing windows
> user names, so if you use windows only authentication, you can add only
> existing windows user names for new logins.
> Regards,
> Daniel
> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> > I am using SQLServer 2000 and for reasons unknown the name of the server
> got
> > changed so that it did not match the name of the machine. I discovered
> this
> > when our application could not connect to the database.
> > I changed the servername using:
> > exec sp_dropserver 'SSM_6000_A', 'droplogins'
> > exec sp_addserver 'SSM_6000_C', 'local'
> > I stopped and started the server and when I checked the name of the server
> > using
> > SELECT @.@.SERVERNAME
> > I got the correct name, SSM_6000_C
> > I still could not connect to the database but I thought I had to recreate
> > the logins.
> >
> > I deleted one of the users and logins and tried to recreate it and I get
> the
> > error:
> > "ERROR15401: WindowsNT user or group 'user-name' not found. Check
> > the name again."
> >
> > The server is on our network. I can go to folders, etc. on the network
> once
> > I log in using my network account.
> >
> > What is wrong?
> > Is there someplace within SQLServer that did not get the server name
> change?
> > Where can I check?
> >
> > I went to a DTS package and was configuring a query in an Execute SQL Task
> > and the server name was the old name.
> >
> > Thanks for your help!!
> > Gloria
> >
>
>|||Hi
You could also try to take the server out of your domain, and then join it
to the domain again. Sometimes you have to take a server out of the domain
before it's properly "connected" to the AD again - especially when you mess
around with servernames.
Regards
Steen
Gloria wrote:
> Hi Daniel,
> I only want to create user names from Windows logins. The problem is
> EM won't let me create Windows logins.
> When I try to create a new login by picking a name from the domain
> list, I get the error message:
> "Error15401:WindowsNT user or group 'domain\user_name' not found.
> Check the name again."
> I checked the servername to make sure after I changed it that if
> matches the machine name and it does. Is it possible that somewhere
> in the bowels of SQLServer the servername did not get changed and
> this mismatch is causing the problem?
> If so, how can I check this?
> Does it check in the registry somewhere the name of the server?
> Thanks again,
> Gloria
> "Daniel Joskovski" wrote:
>> To create new logins you can use EM, but login are only existing
>> windows user names, so if you use windows only authentication, you
>> can add only existing windows user names for new logins.
>> Regards,
>> Daniel
>> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
>> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
>> I am using SQLServer 2000 and for reasons unknown the name of the
>> server got changed so that it did not match the name of the
>> machine. I discovered this when our application could not connect
>> to the database.
>> I changed the servername using:
>> exec sp_dropserver 'SSM_6000_A', 'droplogins'
>> exec sp_addserver 'SSM_6000_C', 'local'
>> I stopped and started the server and when I checked the name of the
>> server using
>> SELECT @.@.SERVERNAME
>> I got the correct name, SSM_6000_C
>> I still could not connect to the database but I thought I had to
>> recreate the logins.
>> I deleted one of the users and logins and tried to recreate it and
>> I get the error:
>> "ERROR15401: WindowsNT user or group 'user-name' not found.
>> Check the name again."
>> The server is on our network. I can go to folders, etc. on the
>> network once I log in using my network account.
>> What is wrong?
>> Is there someplace within SQLServer that did not get the server
>> name change? Where can I check?
>> I went to a DTS package and was configuring a query in an Execute
>> SQL Task and the server name was the old name.
>> Thanks for your help!!
>> Gloria|||Hi
What do you mean by "taking the server out of the domain"? Does our Network
Adminstrator have to take it off of the network and then add it again?
I can connect to our company network using the computer the SQL Server is on
but the SQL Server does not recognize it. Is there a way I can disconnect
then reconnect just the SQL Server?
Is this what typically happens when you change the servername?
What is the correct procedure?
Thanks,
Gloria
"Steen Persson" wrote:
> Hi
> You could also try to take the server out of your domain, and then join it
> to the domain again. Sometimes you have to take a server out of the domain
> before it's properly "connected" to the AD again - especially when you mess
> around with servernames.
> Regards
> Steen
> Gloria wrote:
> > Hi Daniel,
> > I only want to create user names from Windows logins. The problem is
> > EM won't let me create Windows logins.
> > When I try to create a new login by picking a name from the domain
> > list, I get the error message:
> > "Error15401:WindowsNT user or group 'domain\user_name' not found.
> > Check the name again."
> >
> > I checked the servername to make sure after I changed it that if
> > matches the machine name and it does. Is it possible that somewhere
> > in the bowels of SQLServer the servername did not get changed and
> > this mismatch is causing the problem?
> > If so, how can I check this?
> > Does it check in the registry somewhere the name of the server?
> >
> > Thanks again,
> > Gloria
> >
> > "Daniel Joskovski" wrote:
> >
> >> To create new logins you can use EM, but login are only existing
> >> windows user names, so if you use windows only authentication, you
> >> can add only existing windows user names for new logins.
> >>
> >> Regards,
> >> Daniel
> >>
> >> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> >> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> >> I am using SQLServer 2000 and for reasons unknown the name of the
> >> server got changed so that it did not match the name of the
> >> machine. I discovered this when our application could not connect
> >> to the database.
> >> I changed the servername using:
> >> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> >> exec sp_addserver 'SSM_6000_C', 'local'
> >> I stopped and started the server and when I checked the name of the
> >> server using
> >> SELECT @.@.SERVERNAME
> >> I got the correct name, SSM_6000_C
> >> I still could not connect to the database but I thought I had to
> >> recreate the logins.
> >>
> >> I deleted one of the users and logins and tried to recreate it and
> >> I get the error:
> >> "ERROR15401: WindowsNT user or group 'user-name' not found.
> >> Check the name again."
> >>
> >> The server is on our network. I can go to folders, etc. on the
> >> network once I log in using my network account.
> >>
> >> What is wrong?
> >> Is there someplace within SQLServer that did not get the server
> >> name change? Where can I check?
> >>
> >> I went to a DTS package and was configuring a query in an Execute
> >> SQL Task and the server name was the old name.
> >>
> >> Thanks for your help!!
> >> Gloria
>
>|||Hi Gloria
You might have to have your network administrator to do this. It will
require an account that has admin priveledges on your domain.
I don't know if there is a "correct procedure" for changing a servername,
but generally I'd take the server out of the domain - change the name and
then join the server to the domain again. This is not only relevant for
SQLServer, but for every kind of servers. In some cases you can get away
with just renaming the server while it's still a member of the domain, but
in some cases you see weird things and problems afterwards. Therefore I
prefer to do the steps above.
IMHO you shouldn't change a servername without knowing the consequences it
can have on the network. If you don't know about how to remove and join a
server to/from a Domain, I think you should leave the name change to
somebody else...:-).
Regards
Steen
Gloria wrote:
> Hi
> What do you mean by "taking the server out of the domain"? Does our
> Network Adminstrator have to take it off of the network and then add
> it again?
> I can connect to our company network using the computer the SQL
> Server is on but the SQL Server does not recognize it. Is there a
> way I can disconnect then reconnect just the SQL Server?
> Is this what typically happens when you change the servername?
> What is the correct procedure?
> Thanks,
> Gloria
> "Steen Persson" wrote:
>> Hi
>> You could also try to take the server out of your domain, and then
>> join it to the domain again. Sometimes you have to take a server out
>> of the domain before it's properly "connected" to the AD again -
>> especially when you mess around with servernames.
>> Regards
>> Steen
>> Gloria wrote:
>> Hi Daniel,
>> I only want to create user names from Windows logins. The problem
>> is EM won't let me create Windows logins.
>> When I try to create a new login by picking a name from the domain
>> list, I get the error message:
>> "Error15401:WindowsNT user or group 'domain\user_name' not
>> found. Check the name again."
>> I checked the servername to make sure after I changed it that if
>> matches the machine name and it does. Is it possible that somewhere
>> in the bowels of SQLServer the servername did not get changed and
>> this mismatch is causing the problem?
>> If so, how can I check this?
>> Does it check in the registry somewhere the name of the server?
>> Thanks again,
>> Gloria
>> "Daniel Joskovski" wrote:
>> To create new logins you can use EM, but login are only existing
>> windows user names, so if you use windows only authentication, you
>> can add only existing windows user names for new logins.
>> Regards,
>> Daniel
>> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
>> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
>> I am using SQLServer 2000 and for reasons unknown the name of the
>> server got changed so that it did not match the name of the
>> machine. I discovered this when our application could not connect
>> to the database.
>> I changed the servername using:
>> exec sp_dropserver 'SSM_6000_A', 'droplogins'
>> exec sp_addserver 'SSM_6000_C', 'local'
>> I stopped and started the server and when I checked the name of
>> the server using
>> SELECT @.@.SERVERNAME
>> I got the correct name, SSM_6000_C
>> I still could not connect to the database but I thought I had to
>> recreate the logins.
>> I deleted one of the users and logins and tried to recreate it and
>> I get the error:
>> "ERROR15401: WindowsNT user or group 'user-name' not found.
>> Check the name again."
>> The server is on our network. I can go to folders, etc. on the
>> network once I log in using my network account.
>> What is wrong?
>> Is there someplace within SQLServer that did not get the server
>> name change? Where can I check?
>> I went to a DTS package and was configuring a query in an Execute
>> SQL Task and the server name was the old name.
>> Thanks for your help!!
>> Gloria|||Hi,
I agree that you should not change things without knowing the consequences
but when you are trying to fix a problem and the documentation is inadequate,
you do the best you can.
The original problem was that our application could not connect to the
database. I discovered that the machine name and the SQLServer name did not
match. Now the computer that has SQLServer is connected to the network and
works fine. The domain is recognized by the computer. Changing the server
name to match the machine name should allow the network domain to be
recognized by SQLServer, shouldn't it?
When you select Windows authentication and the network domain and user names
are shown, where is this coming from?
Doesn't SQLServer use the same information when connecting to the network as
the computer does?
Thanks,
Gloria
"Steen Persson" wrote:
> Hi Gloria
> You might have to have your network administrator to do this. It will
> require an account that has admin priveledges on your domain.
> I don't know if there is a "correct procedure" for changing a servername,
> but generally I'd take the server out of the domain - change the name and
> then join the server to the domain again. This is not only relevant for
> SQLServer, but for every kind of servers. In some cases you can get away
> with just renaming the server while it's still a member of the domain, but
> in some cases you see weird things and problems afterwards. Therefore I
> prefer to do the steps above.
> IMHO you shouldn't change a servername without knowing the consequences it
> can have on the network. If you don't know about how to remove and join a
> server to/from a Domain, I think you should leave the name change to
> somebody else...:-).
> Regards
> Steen
>
> Gloria wrote:
> > Hi
> > What do you mean by "taking the server out of the domain"? Does our
> > Network Adminstrator have to take it off of the network and then add
> > it again?
> > I can connect to our company network using the computer the SQL
> > Server is on but the SQL Server does not recognize it. Is there a
> > way I can disconnect then reconnect just the SQL Server?
> >
> > Is this what typically happens when you change the servername?
> > What is the correct procedure?
> >
> > Thanks,
> > Gloria
> > "Steen Persson" wrote:
> >
> >> Hi
> >>
> >> You could also try to take the server out of your domain, and then
> >> join it to the domain again. Sometimes you have to take a server out
> >> of the domain before it's properly "connected" to the AD again -
> >> especially when you mess around with servernames.
> >>
> >> Regards
> >> Steen
> >>
> >> Gloria wrote:
> >> Hi Daniel,
> >> I only want to create user names from Windows logins. The problem
> >> is EM won't let me create Windows logins.
> >> When I try to create a new login by picking a name from the domain
> >> list, I get the error message:
> >> "Error15401:WindowsNT user or group 'domain\user_name' not
> >> found. Check the name again."
> >>
> >> I checked the servername to make sure after I changed it that if
> >> matches the machine name and it does. Is it possible that somewhere
> >> in the bowels of SQLServer the servername did not get changed and
> >> this mismatch is causing the problem?
> >> If so, how can I check this?
> >> Does it check in the registry somewhere the name of the server?
> >>
> >> Thanks again,
> >> Gloria
> >>
> >> "Daniel Joskovski" wrote:
> >>
> >> To create new logins you can use EM, but login are only existing
> >> windows user names, so if you use windows only authentication, you
> >> can add only existing windows user names for new logins.
> >>
> >> Regards,
> >> Daniel
> >>
> >> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> >> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> >> I am using SQLServer 2000 and for reasons unknown the name of the
> >> server got changed so that it did not match the name of the
> >> machine. I discovered this when our application could not connect
> >> to the database.
> >> I changed the servername using:
> >> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> >> exec sp_addserver 'SSM_6000_C', 'local'
> >> I stopped and started the server and when I checked the name of
> >> the server using
> >> SELECT @.@.SERVERNAME
> >> I got the correct name, SSM_6000_C
> >> I still could not connect to the database but I thought I had to
> >> recreate the logins.
> >>
> >> I deleted one of the users and logins and tried to recreate it and
> >> I get the error:
> >> "ERROR15401: WindowsNT user or group 'user-name' not found.
> >> Check the name again."
> >>
> >> The server is on our network. I can go to folders, etc. on the
> >> network once I log in using my network account.
> >>
> >> What is wrong?
> >> Is there someplace within SQLServer that did not get the server
> >> name change? Where can I check?
> >>
> >> I went to a DTS package and was configuring a query in an Execute
> >> SQL Task and the server name was the old name.
> >>
> >> Thanks for your help!!
> >> Gloria
>
>|||Hi
Since your problem is with the NTAuthentication and Domain name, it could
very well be that the server and/or Domain Controller isn't in "sync". Since
there has been messed with the servernames, the first thing I'd try would be
to re-join the server to the domain. In the AD you have a lot of pointers
and settings (DNS, SPN, WINS etc.) that holds a servername. If you just
change a servername when the server are in the Domain, some of these might
not be correctly updated where others will. This can very well cause a
number of weird issues that isn't explainable. When you take the server out
of the domain, the AD will remove all the references to the "old"
servername. When you then join the server back into the domain with the new
name, it will be correctly updated throughout the entire domain and all
pointers and references will be refreshed to reflect the new name.
It might not be the reason or solution in your case, but it's quite easy to
do so it would definately do one the first thing I'd try.
Regards
Steen
Gloria wrote:
> Hi,
> I agree that you should not change things without knowing the
> consequences but when you are trying to fix a problem and the
> documentation is inadequate, you do the best you can.
> The original problem was that our application could not connect to the
> database. I discovered that the machine name and the SQLServer name
> did not match. Now the computer that has SQLServer is connected to
> the network and works fine. The domain is recognized by the
> computer. Changing the server name to match the machine name should
> allow the network domain to be recognized by SQLServer, shouldn't it?
> When you select Windows authentication and the network domain and
> user names are shown, where is this coming from?
> Doesn't SQLServer use the same information when connecting to the
> network as the computer does?
> Thanks,
> Gloria
> "Steen Persson" wrote:
>> Hi Gloria
>> You might have to have your network administrator to do this. It will
>> require an account that has admin priveledges on your domain.
>> I don't know if there is a "correct procedure" for changing a
>> servername, but generally I'd take the server out of the domain -
>> change the name and then join the server to the domain again. This
>> is not only relevant for SQLServer, but for every kind of servers.
>> In some cases you can get away with just renaming the server while
>> it's still a member of the domain, but in some cases you see weird
>> things and problems afterwards. Therefore I prefer to do the steps
>> above.
>> IMHO you shouldn't change a servername without knowing the
>> consequences it can have on the network. If you don't know about how
>> to remove and join a server to/from a Domain, I think you should
>> leave the name change to somebody else...:-).
>> Regards
>> Steen
>>
>> Gloria wrote:
>> Hi
>> What do you mean by "taking the server out of the domain"? Does our
>> Network Adminstrator have to take it off of the network and then add
>> it again?
>> I can connect to our company network using the computer the SQL
>> Server is on but the SQL Server does not recognize it. Is there a
>> way I can disconnect then reconnect just the SQL Server?
>> Is this what typically happens when you change the servername?
>> What is the correct procedure?
>> Thanks,
>> Gloria
>> "Steen Persson" wrote:
>> Hi
>> You could also try to take the server out of your domain, and then
>> join it to the domain again. Sometimes you have to take a server
>> out of the domain before it's properly "connected" to the AD again
>> - especially when you mess around with servernames.
>> Regards
>> Steen
>> Gloria wrote:
>> Hi Daniel,
>> I only want to create user names from Windows logins. The problem
>> is EM won't let me create Windows logins.
>> When I try to create a new login by picking a name from the domain
>> list, I get the error message:
>> "Error15401:WindowsNT user or group 'domain\user_name' not
>> found. Check the name again."
>> I checked the servername to make sure after I changed it that if
>> matches the machine name and it does. Is it possible that
>> somewhere in the bowels of SQLServer the servername did not get
>> changed and this mismatch is causing the problem?
>> If so, how can I check this?
>> Does it check in the registry somewhere the name of the server?
>> Thanks again,
>> Gloria
>> "Daniel Joskovski" wrote:
>> To create new logins you can use EM, but login are only existing
>> windows user names, so if you use windows only authentication,
>> you can add only existing windows user names for new logins.
>> Regards,
>> Daniel
>> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
>> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
>>> I am using SQLServer 2000 and for reasons unknown the name of
>>> the server got changed so that it did not match the name of the
>>> machine. I discovered this when our application could not
>>> connect to the database.
>>> I changed the servername using:
>>> exec sp_dropserver 'SSM_6000_A', 'droplogins'
>>> exec sp_addserver 'SSM_6000_C', 'local'
>>> I stopped and started the server and when I checked the name of
>>> the server using
>>> SELECT @.@.SERVERNAME
>>> I got the correct name, SSM_6000_C
>>> I still could not connect to the database but I thought I had to
>>> recreate the logins.
>>>
>>> I deleted one of the users and logins and tried to recreate it
>>> and I get the error:
>>> "ERROR15401: WindowsNT user or group 'user-name' not
>>> found. Check the name again."
>>>
>>> The server is on our network. I can go to folders, etc. on the
>>> network once I log in using my network account.
>>>
>>> What is wrong?
>>> Is there someplace within SQLServer that did not get the server
>>> name change? Where can I check?
>>>
>>> I went to a DTS package and was configuring a query in an
>>> Execute SQL Task and the server name was the old name.
>>>
>>> Thanks for your help!!
>>> Gloria|||Hi Steen,
Many, many thanks. Worked like a charm!!
Gloria
"Steen Persson" wrote:
> Hi
> Since your problem is with the NTAuthentication and Domain name, it could
> very well be that the server and/or Domain Controller isn't in "sync". Since
> there has been messed with the servernames, the first thing I'd try would be
> to re-join the server to the domain. In the AD you have a lot of pointers
> and settings (DNS, SPN, WINS etc.) that holds a servername. If you just
> change a servername when the server are in the Domain, some of these might
> not be correctly updated where others will. This can very well cause a
> number of weird issues that isn't explainable. When you take the server out
> of the domain, the AD will remove all the references to the "old"
> servername. When you then join the server back into the domain with the new
> name, it will be correctly updated throughout the entire domain and all
> pointers and references will be refreshed to reflect the new name.
> It might not be the reason or solution in your case, but it's quite easy to
> do so it would definately do one the first thing I'd try.
> Regards
> Steen
> Gloria wrote:
> > Hi,
> >
> > I agree that you should not change things without knowing the
> > consequences but when you are trying to fix a problem and the
> > documentation is inadequate, you do the best you can.
> >
> > The original problem was that our application could not connect to the
> > database. I discovered that the machine name and the SQLServer name
> > did not match. Now the computer that has SQLServer is connected to
> > the network and works fine. The domain is recognized by the
> > computer. Changing the server name to match the machine name should
> > allow the network domain to be recognized by SQLServer, shouldn't it?
> >
> > When you select Windows authentication and the network domain and
> > user names are shown, where is this coming from?
> > Doesn't SQLServer use the same information when connecting to the
> > network as the computer does?
> >
> > Thanks,
> > Gloria
> > "Steen Persson" wrote:
> >
> >> Hi Gloria
> >>
> >> You might have to have your network administrator to do this. It will
> >> require an account that has admin priveledges on your domain.
> >> I don't know if there is a "correct procedure" for changing a
> >> servername, but generally I'd take the server out of the domain -
> >> change the name and then join the server to the domain again. This
> >> is not only relevant for SQLServer, but for every kind of servers.
> >> In some cases you can get away with just renaming the server while
> >> it's still a member of the domain, but in some cases you see weird
> >> things and problems afterwards. Therefore I prefer to do the steps
> >> above.
> >>
> >> IMHO you shouldn't change a servername without knowing the
> >> consequences it can have on the network. If you don't know about how
> >> to remove and join a server to/from a Domain, I think you should
> >> leave the name change to somebody else...:-).
> >>
> >> Regards
> >> Steen
> >>
> >>
> >> Gloria wrote:
> >> Hi
> >> What do you mean by "taking the server out of the domain"? Does our
> >> Network Adminstrator have to take it off of the network and then add
> >> it again?
> >> I can connect to our company network using the computer the SQL
> >> Server is on but the SQL Server does not recognize it. Is there a
> >> way I can disconnect then reconnect just the SQL Server?
> >>
> >> Is this what typically happens when you change the servername?
> >> What is the correct procedure?
> >>
> >> Thanks,
> >> Gloria
> >> "Steen Persson" wrote:
> >>
> >> Hi
> >>
> >> You could also try to take the server out of your domain, and then
> >> join it to the domain again. Sometimes you have to take a server
> >> out of the domain before it's properly "connected" to the AD again
> >> - especially when you mess around with servernames.
> >>
> >> Regards
> >> Steen
> >>
> >> Gloria wrote:
> >> Hi Daniel,
> >> I only want to create user names from Windows logins. The problem
> >> is EM won't let me create Windows logins.
> >> When I try to create a new login by picking a name from the domain
> >> list, I get the error message:
> >> "Error15401:WindowsNT user or group 'domain\user_name' not
> >> found. Check the name again."
> >>
> >> I checked the servername to make sure after I changed it that if
> >> matches the machine name and it does. Is it possible that
> >> somewhere in the bowels of SQLServer the servername did not get
> >> changed and this mismatch is causing the problem?
> >> If so, how can I check this?
> >> Does it check in the registry somewhere the name of the server?
> >>
> >> Thanks again,
> >> Gloria
> >>
> >> "Daniel Joskovski" wrote:
> >>
> >> To create new logins you can use EM, but login are only existing
> >> windows user names, so if you use windows only authentication,
> >> you can add only existing windows user names for new logins.
> >>
> >> Regards,
> >> Daniel
> >>
> >> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> >> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> >>> I am using SQLServer 2000 and for reasons unknown the name of
> >>> the server got changed so that it did not match the name of the
> >>> machine. I discovered this when our application could not
> >>> connect to the database.
> >>> I changed the servername using:
> >>> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> >>> exec sp_addserver 'SSM_6000_C', 'local'
> >>> I stopped and started the server and when I checked the name of
> >>> the server using
> >>> SELECT @.@.SERVERNAME
> >>> I got the correct name, SSM_6000_C
> >>> I still could not connect to the database but I thought I had to
> >>> recreate the logins.
> >>>
> >>> I deleted one of the users and logins and tried to recreate it
> >>> and I get the error:
> >>> "ERROR15401: WindowsNT user or group 'user-name' not
> >>> found. Check the name again."
> >>>
> >>> The server is on our network. I can go to folders, etc. on the
> >>> network once I log in using my network account.
> >>>
> >>> What is wrong?
> >>> Is there someplace within SQLServer that did not get the server
> >>> name change? Where can I check?
> >>>
> >>> I went to a DTS package and was configuring a query in an
> >>> Execute SQL Task and the server name was the old name.
> >>>
> >>> Thanks for your help!!
> >>> Gloria
>
>

Sunday, March 25, 2012

Can't Generate SSPI

Wednesday, March 7, 2012

Can't Create and Connect to a new Database (.mdf file)

Friday, February 24, 2012

Can't connect using sa login and don't have any other administrator logins

Can't connect to the sql server

Can't connect to the sql server

Can't connect to SQL server in Windows XP SP2

Can't connect to SQL server in Windows XP SP2

Tuesday, February 14, 2012

cant connect to my databse in lan

Sunday, February 12, 2012

Can't connect to database due to Windows authentication

Can't connect to database due to Windows authentication

Can't connect to database due to Windows authentication

connect from ASP app

Blog Archive

About Me