Showing posts with label password. Show all posts
Showing posts with label password. Show all posts

Wednesday, March 28, 2012

Login failed for user COLDFIRE/ASPNET

i have my SQL server in windows integrated security so my connection string doesnt have to have password and uid stuff.
this is my connection string

data source=COLDFIRE;initial catalog=Northwind;integrated security=SSPI;persist security info=True;workstation id=COLDFIRE;packet size=4096

i tried this in windows form project of .net and work fine, i connected easily but when i tried it in asp project i got this error :

Login failed for user COLDFIRE/ASPNET

whats wrong with it?That's because the ASPNet user account, which was created when you installed ASP.Net, is not set up as a user on the SQL Server.

Login failed for user 'abc'

When we get the error message stated in the subject , does it mean that the
password was incorrect ?
Trying to find out other possible reasons when you may get that message.
I do not believe one would get that message if the server is unavailable
right ? I believe the error in that case is more of a General Network Error
Please let me know
Thanks> When we get the error message stated in the subject , does it mean that
the
> password was incorrect
Or Login's name. Or Authentication issue.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:O0j%23Y33hFHA.2372@.TK2MSFTNGP14.phx.gbl...
> When we get the error message stated in the subject , does it mean that
the
> password was incorrect ?
> Trying to find out other possible reasons when you may get that message.
> I do not believe one would get that message if the server is unavailable
> right ? I believe the error in that case is more of a General Network
Error
> Please let me know
> Thanks
>|||what do u mean authentication issue ? Login name is right..
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23iS4563hFHA.572@.TK2MSFTNGP15.phx.gbl...
> > When we get the error message stated in the subject , does it mean that
> the
> > password was incorrect
> Or Login's name. Or Authentication issue.
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:O0j%23Y33hFHA.2372@.TK2MSFTNGP14.phx.gbl...
> > When we get the error message stated in the subject , does it mean that
> the
> > password was incorrect ?
> >
> > Trying to find out other possible reasons when you may get that message.
> >
> > I do not believe one would get that message if the server is unavailable
> > right ? I believe the error in that case is more of a General Network
> Error
> >
> > Please let me know
> >
> > Thanks
> >
> >
>|||Hassan
You can set up an authenication to Windows ONLY or Mixed (Windows/SQL
Server). If you have Windows Only and try to connect by using a login who
does not exist or exists only in SQL Server you will get an error.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23LN%231L8hFHA.3912@.tk2msftngp13.phx.gbl...
> what do u mean authentication issue ? Login name is right..
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:%23iS4563hFHA.572@.TK2MSFTNGP15.phx.gbl...
> > > When we get the error message stated in the subject , does it mean
that
> > the
> > > password was incorrect
> >
> > Or Login's name. Or Authentication issue.
> >
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:O0j%23Y33hFHA.2372@.TK2MSFTNGP14.phx.gbl...
> > > When we get the error message stated in the subject , does it mean
that
> > the
> > > password was incorrect ?
> > >
> > > Trying to find out other possible reasons when you may get that
message.
> > >
> > > I do not believe one would get that message if the server is
unavailable
> > > right ? I believe the error in that case is more of a General Network
> > Error
> > >
> > > Please let me know
> > >
> > > Thanks
> > >
> > >
> >
> >
>

Monday, March 26, 2012

Login failed for user '(null)'...Reasons?

A SQL Server (in another domain) I'm trying to connect to with SQL Server
authentication (UID and password) fails from an Access application. I've
tried a ODBC DSN and a DSN-less connection. The SQL Server is running in
mixed authentication mode.
I can get to the SQL Server with Enterprise Manager, can successfully test
the connection with the DSN in the ODBC Administrator, and can successfully
test the connection via a UDL test (OLEDB)...just not through an Access 2000
application.
Can anyone provide the various possible reasons for...
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
...?
Why is the SQL Server receiving a null UID?
Thanks,
JoeIn order for the server to accept the connection attempt it needs to
"authenticate" that the user is some that has rights (user needs the ability
to connect to the \\servername\ipc$ share). This step happens before SQL
Server gets a change to interrogate the credentials. See Books Online
"Authentication Modes" for more detail.
Steve
"JRE" <nomail@.all> wrote in message
news:#FMgYTUAEHA.3316@.TK2MSFTNGP11.phx.gbl...
> A SQL Server (in another domain) I'm trying to connect to with SQL Server
> authentication (UID and password) fails from an Access application. I've
> tried a ODBC DSN and a DSN-less connection. The SQL Server is running in
> mixed authentication mode.
> I can get to the SQL Server with Enterprise Manager, can successfully test
> the connection with the DSN in the ODBC Administrator, and can
successfully
> test the connection via a UDL test (OLEDB)...just not through an Access
2000
> application.
> Can anyone provide the various possible reasons for...
> Connection failed:
> SQLState: '28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> ...?
> Why is the SQL Server receiving a null UID?
> Thanks,
> Joe
>
>|||Thanks... Proper user accounts exist on both domains in question.
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:%233d64rVAEHA.2484@.TK2MSFTNGP12.phx.gbl...
> In order for the server to accept the connection attempt it needs to
> "authenticate" that the user is some that has rights (user needs the
ability
> to connect to the \\servername\ipc$ share). This step happens before SQL
> Server gets a change to interrogate the credentials. See Books Online
> "Authentication Modes" for more detail.
> Steve
> "JRE" <nomail@.all> wrote in message
> news:#FMgYTUAEHA.3316@.TK2MSFTNGP11.phx.gbl...
Server
test
> successfully
> 2000
>|||On SQL Server, enabled auditing for "failed logins" and see if the accounts
are being rejected by SQL Server.
Security auditing at the server level should indicate if the user account is
failing to get a server connection.
Steve
"JRE" <nomail@.all> wrote in message
news:OmopmQtAEHA.1548@.TK2MSFTNGP12.phx.gbl...
> Thanks... Proper user accounts exist on both domains in question.
> "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> news:%233d64rVAEHA.2484@.TK2MSFTNGP12.phx.gbl...
> ability
> Server
I've
in
> test
Access
>|||Joe,
See if this thread helps:
http://groups.google.com/groups?q=E...SQLServerTables Do you know
what piece of the Access application is raising the error?
SK
JRE wrote:

>A SQL Server (in another domain) I'm trying to connect to with SQL Server
>authentication (UID and password) fails from an Access application. I've
>tried a ODBC DSN and a DSN-less connection. The SQL Server is running in
>mixed authentication mode.
>I can get to the SQL Server with Enterprise Manager, can successfully test
>the connection with the DSN in the ODBC Administrator, and can successfully
>test the connection via a UDL test (OLEDB)...just not through an Access 200
0
>application.
>Can anyone provide the various possible reasons for...
>Connection failed:
>SQLState: '28000'
>SQL Server Error: 18452
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
>'(null)'. Reason: Not associated with a trusted SQL Server connection.
>...?
>Why is the SQL Server receiving a null UID?
>Thanks,
>Joe
>
>
>|||Thanks...I checked out the article. That's pretty much what I do to connect
to a SQL Server back end. The error I get is not an Access error. It's
generated by SQL Server.
"Steve Kass" <skass@.drew.edu> wrote in message
news:u$eUJJZBEHA.1544@.TK2MSFTNGP09.phx.gbl...
> Joe,
> See if this thread helps:
> http://groups.google.com/groups?q=E...SQLServerTables Do you know
> what piece of the Access application is raising the error?
> SK
> JRE wrote:
>
test
successfully
2000
>|||Thanks. I'll pass this on to the SQL Server admin.
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:e1yyddtAEHA.1456@.TK2MSFTNGP09.phx.gbl...
> On SQL Server, enabled auditing for "failed logins" and see if the
accounts
> are being rejected by SQL Server.
> Security auditing at the server level should indicate if the user account
is
> failing to get a server connection.
> Steve
> "JRE" <nomail@.all> wrote in message
> news:OmopmQtAEHA.1548@.TK2MSFTNGP12.phx.gbl...
SQL
> I've
running
> in
successfully
> Access
connection.
>|||Joe,
I know the error is a SQL Server error, but I wanted to know at what
point in your Access application that error is raised - is it a specific
line of VB code, is it when a specific form is opened, etc.? Since you
get the error when you run the Access application, there must be a way
to debug the Access application to see exactly at what point the error
occurs, and what Access is doing at that moment.
SK
JRE wrote:

>Thanks...I checked out the article. That's pretty much what I do to connect
>to a SQL Server back end. The error I get is not an Access error. It's
>generated by SQL Server.
>"Steve Kass" <skass@.drew.edu> wrote in message
>news:u$eUJJZBEHA.1544@.TK2MSFTNGP09.phx.gbl...
>
>test
>
>successfully
>
>2000
>
>
>

Login failed for user '(null)'...Reasons?

A SQL Server (in another domain) I'm trying to connect to with SQL Server
authentication (UID and password) fails from an Access application. I've
tried a ODBC DSN and a DSN-less connection. The SQL Server is running in
mixed authentication mode.
I can get to the SQL Server with Enterprise Manager, can successfully test
the connection with the DSN in the ODBC Administrator, and can successfully
test the connection via a UDL test (OLEDB)...just not through an Access 2000
application.
Can anyone provide the various possible reasons for...
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
...?
Why is the SQL Server receiving a null UID?
Thanks,
JoeIn order for the server to accept the connection attempt it needs to
"authenticate" that the user is some that has rights (user needs the ability
to connect to the \\servername\ipc$ share). This step happens before SQL
Server gets a change to interrogate the credentials. See Books Online
"Authentication Modes" for more detail.
Steve
"JRE" <nomail@.all> wrote in message
news:#FMgYTUAEHA.3316@.TK2MSFTNGP11.phx.gbl...
> A SQL Server (in another domain) I'm trying to connect to with SQL Server
> authentication (UID and password) fails from an Access application. I've
> tried a ODBC DSN and a DSN-less connection. The SQL Server is running in
> mixed authentication mode.
> I can get to the SQL Server with Enterprise Manager, can successfully test
> the connection with the DSN in the ODBC Administrator, and can
successfully
> test the connection via a UDL test (OLEDB)...just not through an Access
2000
> application.
> Can anyone provide the various possible reasons for...
> Connection failed:
> SQLState: '28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> ...?
> Why is the SQL Server receiving a null UID?
> Thanks,
> Joe
>
>|||Thanks... Proper user accounts exist on both domains in question.
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:%233d64rVAEHA.2484@.TK2MSFTNGP12.phx.gbl...
> In order for the server to accept the connection attempt it needs to
> "authenticate" that the user is some that has rights (user needs the
ability
> to connect to the \\servername\ipc$ share). This step happens before SQL
> Server gets a change to interrogate the credentials. See Books Online
> "Authentication Modes" for more detail.
> Steve
> "JRE" <nomail@.all> wrote in message
> news:#FMgYTUAEHA.3316@.TK2MSFTNGP11.phx.gbl...
Server
test
> successfully
> 2000
>|||On SQL Server, enabled auditing for "failed logins" and see if the accounts
are being rejected by SQL Server.
Security auditing at the server level should indicate if the user account is
failing to get a server connection.
Steve
"JRE" <nomail@.all> wrote in message
news:OmopmQtAEHA.1548@.TK2MSFTNGP12.phx.gbl...
> Thanks... Proper user accounts exist on both domains in question.
> "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> news:%233d64rVAEHA.2484@.TK2MSFTNGP12.phx.gbl...
> ability
> Server
I've
in
> test
Access
>|||Joe,
See if this thread helps:
http://groups.google.com/groups?q=E...SQLServerTables Do you know
what piece of the Access application is raising the error?
SK
JRE wrote:

>A SQL Server (in another domain) I'm trying to connect to with SQL Server
>authentication (UID and password) fails from an Access application. I've
>tried a ODBC DSN and a DSN-less connection. The SQL Server is running in
>mixed authentication mode.
>I can get to the SQL Server with Enterprise Manager, can successfully test
>the connection with the DSN in the ODBC Administrator, and can successfully
>test the connection via a UDL test (OLEDB)...just not through an Access 200
0
>application.
>Can anyone provide the various possible reasons for...
>Connection failed:
>SQLState: '28000'
>SQL Server Error: 18452
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
>'(null)'. Reason: Not associated with a trusted SQL Server connection.
>...?
>Why is the SQL Server receiving a null UID?
>Thanks,
>Joe
>
>
>|||Thanks...I checked out the article. That's pretty much what I do to connect
to a SQL Server back end. The error I get is not an Access error. It's
generated by SQL Server.
"Steve Kass" <skass@.drew.edu> wrote in message
news:u$eUJJZBEHA.1544@.TK2MSFTNGP09.phx.gbl...
> Joe,
> See if this thread helps:
> http://groups.google.com/groups?q=E...SQLServerTables Do you know
> what piece of the Access application is raising the error?
> SK
> JRE wrote:
>
test
successfully
2000
>|||Thanks. I'll pass this on to the SQL Server admin.
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:e1yyddtAEHA.1456@.TK2MSFTNGP09.phx.gbl...
> On SQL Server, enabled auditing for "failed logins" and see if the
accounts
> are being rejected by SQL Server.
> Security auditing at the server level should indicate if the user account
is
> failing to get a server connection.
> Steve
> "JRE" <nomail@.all> wrote in message
> news:OmopmQtAEHA.1548@.TK2MSFTNGP12.phx.gbl...
SQL
> I've
running
> in
successfully
> Access
connection.
>|||Joe,
I know the error is a SQL Server error, but I wanted to know at what
point in your Access application that error is raised - is it a specific
line of VB code, is it when a specific form is opened, etc.? Since you
get the error when you run the Access application, there must be a way
to debug the Access application to see exactly at what point the error
occurs, and what Access is doing at that moment.
SK
JRE wrote:

>Thanks...I checked out the article. That's pretty much what I do to connect
>to a SQL Server back end. The error I get is not an Access error. It's
>generated by SQL Server.
>"Steve Kass" <skass@.drew.edu> wrote in message
>news:u$eUJJZBEHA.1544@.TK2MSFTNGP09.phx.gbl...
>
>test
>
>successfully
>
>2000
>
>
>|||Hi,
Was this resolved by anybody... I have the same problem and I get the
error when I start the index page. My OS is Win2k with SP4, the ASP is
version 5.0 and not. net, SQL is 2000 sp3. My connection string in the
_appStart.asa file is
Connection string in_appStart.asp =
application("sADOConn") ="Provider=SQLOLEDB;" &_
"Initial Catalog=TheMatrix;" &_
"Data Source=sqlServerName;" &_
"Integrated Security=SSPI;"
I believe the problem is something to do with impersonation and I've
read SP4 handles this differently to SP3. The IIS security as you can
see is Windows Authentication enabled so the app knows what domain
account is accessing it and shows details for that account.
Please help!!
Many thanks!
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Hi,
Was this ever resolved.. Have the same problem for my own web app. I get
the error as soon as I launch the app. The connection string is in the
_appstart.asa file and goes like this..
Connection string in_appStart.asp =
application("sADOConn") ="Provider=SQLOLEDB;" &_
"Initial Catalog=TheMatrix;" &_
"Data Source=sqlServerName;" &_
"Integrated Security=SSPI;"
OS is Win2k SP4, ASP is version 5.0 not .net.
When I query the SQL server from my desktop, same place I try to open
the web app, I'm told the system_user is my own domain account.
I'm thinking the problem is to do with how SP4 has changed impersonation
and IIS is set to enable windows authentication. But this is how I
gather what domain user account is accessing the website so they can see
their details. This is the theory but I'm stuck at index page with this
error.
Please help!!
Thanks!!!
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

Friday, March 23, 2012

Login failed for user '(null)'

I have several reports using the same database with the same credentials
(using a specific Username and Password). All display fine, except for one
that gives me the following Reporting Services Error:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'BCSpotBonus'.
(rsErrorOpeningConnection) Get Online Help
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
I've configured the data in the same way as the other reports and I've tried
using the "Shared database option" and not using the "Shared database
option." Nothing works. How can this be happening?That shouldnt be happening , but even i had the same
problem.
In the Report Designer try to delete the datasource and
then add it again and re deploy the report. Then try to
view the report.
Hope this helps!
>--Original Message--
>I have several reports using the same database with the
same credentials
>(using a specific Username and Password). All display
fine, except for one
>that gives me the following Reporting Services Error:
>An error has occurred during report processing.
(rsProcessingAborted) Get
>Online Help
>Cannot create a connection to data source 'BCSpotBonus'.
>(rsErrorOpeningConnection) Get Online Help
>Login failed for user '(null)'. Reason: Not associated
with a trusted SQL
>Server connection.
>I've configured the data in the same way as the other
reports and I've tried
>using the "Shared database option" and not using
the "Shared database
>option." Nothing works. How can this be happening?
>.
>

Wednesday, March 21, 2012

Login failed for Server\Guest

Hi - I have two computers, one running Xp Pro and one Xp Home. I created
a windows user account on both machines with the same password. I added
those accounts to SQL Server on both machines and I want to be able to
connect to each other using a trusted connection.
If I try to remotely connect to the Xp Pro machine from the Home machine
using windows authentication, everything works fine. But, if I try to
remotely connect to the Home machine it says that login failed for
Server\Guest. My understanding is that it tries to log in as guest if the
windows account is not found.
Why does it work on one computer but not the other? Is it because it is
Home edition? Is there something else I need to do?
BTW, standard authentication works fine on both machines and the Guest
account is turned off.
Thanks,
Maer
With XP home, authentication is done using the guest account
as simple file sharing is always enabled on XP Home. Refer
to the following for more info:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/?id=831133
-Sue
On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
<maer@.auditleverage.com> wrote:

> Hi - I have two computers, one running Xp Pro and one Xp Home. I created
>a windows user account on both machines with the same password. I added
>those accounts to SQL Server on both machines and I want to be able to
>connect to each other using a trusted connection.
> If I try to remotely connect to the Xp Pro machine from the Home machine
>using windows authentication, everything works fine. But, if I try to
>remotely connect to the Home machine it says that login failed for
>Server\Guest. My understanding is that it tries to log in as guest if the
>windows account is not found.
> Why does it work on one computer but not the other? Is it because it is
>Home edition? Is there something else I need to do?
> BTW, standard authentication works fine on both machines and the Guest
>account is turned off.
> Thanks,
> Maer
>
|||Thank you, Sue!
That clarifies so much! Would I be right in assuming that using windows
authentication is not an option when logging in remotely to Xp Home since it
always uses Guest? Is there a work-around?
Maer
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com...
> With XP home, authentication is done using the guest account
> as simple file sharing is always enabled on XP Home. Refer
> to the following for more info:
> SQL Server clients are authenticated as guests if Simple
> File Sharing is enabled
> http://support.microsoft.com/?id=831133
> -Sue
> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
> <maer@.auditleverage.com> wrote:
>
|||Hi Maer,
You can enable the guest account but that's a security risk
- especially if exposed to the outside world. For SQL
Server, although Windows Authentication is more secure than
SQL Authentication, I'd probably use that option instead of
enabling the guest account. Make sure to turn on security
audits, limit the number of SQL logins and make sure all SQL
logins have strong passwords - mixed case, alpha numeric
with special characters, no known words, etc.
-Sue
On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
<maer@.auditleverage.com> wrote:

> Thank you, Sue!
> That clarifies so much! Would I be right in assuming that using windows
>authentication is not an option when logging in remotely to Xp Home since it
>always uses Guest? Is there a work-around?
> Maer
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com.. .
>
|||Thank you, Sue. Your suggestion seems to be the way to go.
I have noticed that when I try to log in using Windows Authentication to
a Windows 2000 machine from my XP machine, it tries to log me in as
"Server\Administrator" and, of course, fails. My account is part of the
Administrator's group. However, the other way around (from Win 2000 to XP)
works fine.
Is there a limitation in Windows 2000 too?
Thanks again,
Maer
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com...
> Hi Maer,
> You can enable the guest account but that's a security risk
> - especially if exposed to the outside world. For SQL
> Server, although Windows Authentication is more secure than
> SQL Authentication, I'd probably use that option instead of
> enabling the guest account. Make sure to turn on security
> audits, limit the number of SQL logins and make sure all SQL
> logins have strong passwords - mixed case, alpha numeric
> with special characters, no known words, etc.
> -Sue
> On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
> <maer@.auditleverage.com> wrote:
>
|||Hello Maer,
I think it is not a limitation in Windows 2000. Based on my test, I could
access SQL server on Win2000 server by using Windows authenctication if I
use same password for Administrator account on both Win2000 and WinXP
computers. I suggest that you check security policy settings on both
computers to see if they match:
1. Run gpedit.msc
2. Check Computer configuration->Windows settings->Security Settings->Local
Policies->Security Options and make sure the following settings:
Digitally sign client communication (always)Not defined
Digitally sign client communication (when possible)Not defined
Digitally sign server communication (always)Not defined
Digitally sign server communication (when possible)Not defined
LAN Manager Authentication LevelNot defined
Secure channel: Digitally encrypt or sign secure channel data (always)Not
defined
Secure channel: Digitally encrypt secure channel data (when possible)Not
defined
Secure channel: Digitally sign secure channel data (when possible)Not
defined
Secure channel: Require strong (Windows 2000 or later) session keyNot
defined
3. Check Computer configuration->Windows settings->Security Settings->Local
Policies->User Rights assigment, and make sure Deny access this computer
from network is not configured.
Thanks & Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| From: "Maer" <maer@.auditleverage.com>
| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
<k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
<#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
<gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
| Subject: Re: Login failed for Server\Guest
| Date: Thu, 10 Feb 2005 19:33:17 -0500
| Lines: 87
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.connect
| NNTP-Posting-Host: pcp08367474pcs.lndsd201.pa.comcast.net 68.42.29.253
| Path:
TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3409
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Thank you, Sue. Your suggestion seems to be the way to go.
|
| I have noticed that when I try to log in using Windows Authentication
to
| a Windows 2000 machine from my XP machine, it tries to log me in as
| "Server\Administrator" and, of course, fails. My account is part of the
| Administrator's group. However, the other way around (from Win 2000 to
XP)
| works fine.
|
| Is there a limitation in Windows 2000 too?
|
| Thanks again,
| Maer
|
|
|
| "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
| news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com...
| > Hi Maer,
| > You can enable the guest account but that's a security risk
| > - especially if exposed to the outside world. For SQL
| > Server, although Windows Authentication is more secure than
| > SQL Authentication, I'd probably use that option instead of
| > enabling the guest account. Make sure to turn on security
| > audits, limit the number of SQL logins and make sure all SQL
| > logins have strong passwords - mixed case, alpha numeric
| > with special characters, no known words, etc.
| >
| > -Sue
| >
| > On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
| > <maer@.auditleverage.com> wrote:
| >
| >> Thank you, Sue!
| >>
| >> That clarifies so much! Would I be right in assuming that using
| >> windows
| >>authentication is not an option when logging in remotely to Xp Home
since
| >>it
| >>always uses Guest? Is there a work-around?
| >>
| >> Maer
| >>
| >>
| >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
| >>news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com. ..
| >>> With XP home, authentication is done using the guest account
| >>> as simple file sharing is always enabled on XP Home. Refer
| >>> to the following for more info:
| >>> SQL Server clients are authenticated as guests if Simple
| >>> File Sharing is enabled
| >>> http://support.microsoft.com/?id=831133
| >>>
| >>> -Sue
| >>>
| >>> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
| >>> <maer@.auditleverage.com> wrote:
| >>>
| >>>> Hi - I have two computers, one running Xp Pro and one Xp Home. I
| >>>> created
| >>>>a windows user account on both machines with the same password. I
added
| >>>>those accounts to SQL Server on both machines and I want to be able to
| >>>>connect to each other using a trusted connection.
| >>>>
| >>>> If I try to remotely connect to the Xp Pro machine from the Home
| >>>> machine
| >>>>using windows authentication, everything works fine. But, if I try to
| >>>>remotely connect to the Home machine it says that login failed for
| >>>>Server\Guest. My understanding is that it tries to log in as guest if
| >>>>the
| >>>>windows account is not found.
| >>>>
| >>>> Why does it work on one computer but not the other? Is it because
it
| >>>> is
| >>>>Home edition? Is there something else I need to do?
| >>>>
| >>>> BTW, standard authentication works fine on both machines and the
| >>>> Guest
| >>>>account is turned off.
| >>>>
| >>>> Thanks,
| >>>> Maer
| >>>>
| >>>
| >>
| >
|
|
|
|||Peter,
Not necessarily. In your testing, I would guess you are
using XP Pro and do not have simple file sharing enabled.
There are scenarios with XP where you are authenticated as
guest and the use of the same account/password does not
work. Refer to the following knowledge base article:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/?id=831133
-Sue
On Mon, 14 Feb 2005 07:08:38 GMT,
petery@.online.microsoft.com (Peter Yang [MSFT]) wrote:

>Hello Maer,
>I think it is not a limitation in Windows 2000. Based on my test, I could
>access SQL server on Win2000 server by using Windows authenctication if I
>use same password for Administrator account on both Win2000 and WinXP
>computers. I suggest that you check security policy settings on both
>computers to see if they match:
>1. Run gpedit.msc
>2. Check Computer configuration->Windows settings->Security Settings->Local
>Policies->Security Options and make sure the following settings:
>Digitally sign client communication (always)Not defined
>Digitally sign client communication (when possible)Not defined
>Digitally sign server communication (always)Not defined
>Digitally sign server communication (when possible)Not defined
>LAN Manager Authentication LevelNot defined
>Secure channel: Digitally encrypt or sign secure channel data (always)Not
>defined
>Secure channel: Digitally encrypt secure channel data (when possible)Not
>defined
>Secure channel: Digitally sign secure channel data (when possible)Not
>defined
>Secure channel: Require strong (Windows 2000 or later) session keyNot
>defined
>3. Check Computer configuration->Windows settings->Security Settings->Local
>Policies->User Rights assigment, and make sure Deny access this computer
>from network is not configured.
>Thanks & Regards,
>Peter Yang
>MCSE2000/2003, MCSA, MCDBA
>Microsoft Online Partner Support
>When responding to posts, please "Reply to Group" via your newsreader so
>that others may learn and benefit from your issue.
>================================================= ====
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>--
>| From: "Maer" <maer@.auditleverage.com>
>| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
><k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
><#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
><gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
>| Subject: Re: Login failed for Server\Guest
>| Date: Thu, 10 Feb 2005 19:33:17 -0500
>| Lines: 87
>| X-Priority: 3
>| X-MSMail-Priority: Normal
>| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>| X-RFC2646: Format=Flowed; Original
>| Message-ID: <eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
>| Newsgroups: microsoft.public.sqlserver.connect
>| NNTP-Posting-Host: pcp08367474pcs.lndsd201.pa.comcast.net 68.42.29.253
>| Path:
>TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSF TNGP08.phx.gbl!TK2MSFTNGP12
>phx.gbl
>| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3409
>| X-Tomcat-NG: microsoft.public.sqlserver.connect
>|
>| Thank you, Sue. Your suggestion seems to be the way to go.
>|
>| I have noticed that when I try to log in using Windows Authentication
>to
>| a Windows 2000 machine from my XP machine, it tries to log me in as
>| "Server\Administrator" and, of course, fails. My account is part of the
>| Administrator's group. However, the other way around (from Win 2000 to
>XP)
>| works fine.
>|
>| Is there a limitation in Windows 2000 too?
>|
>| Thanks again,
>| Maer
>|
>|
>|
>| "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>| news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com...
>| > Hi Maer,
>| > You can enable the guest account but that's a security risk
>| > - especially if exposed to the outside world. For SQL
>| > Server, although Windows Authentication is more secure than
>| > SQL Authentication, I'd probably use that option instead of
>| > enabling the guest account. Make sure to turn on security
>| > audits, limit the number of SQL logins and make sure all SQL
>| > logins have strong passwords - mixed case, alpha numeric
>| > with special characters, no known words, etc.
>| >
>| > -Sue
>| >
>| > On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
>| > <maer@.auditleverage.com> wrote:
>| >
>| >> Thank you, Sue!
>| >>
>| >> That clarifies so much! Would I be right in assuming that using
>| >> windows
>| >>authentication is not an option when logging in remotely to Xp Home
>since
>| >>it
>| >>always uses Guest? Is there a work-around?
>| >>
>| >> Maer
>| >>
>| >>
>| >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>| >>news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com. ..
>| >>> With XP home, authentication is done using the guest account
>| >>> as simple file sharing is always enabled on XP Home. Refer
>| >>> to the following for more info:
>| >>> SQL Server clients are authenticated as guests if Simple
>| >>> File Sharing is enabled
>| >>> http://support.microsoft.com/?id=831133
>| >>>
>| >>> -Sue
>| >>>
>| >>> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
>| >>> <maer@.auditleverage.com> wrote:
>| >>>
>| >>>> Hi - I have two computers, one running Xp Pro and one Xp Home. I
>| >>>> created
>| >>>>a windows user account on both machines with the same password. I
>added
>| >>>>those accounts to SQL Server on both machines and I want to be able to
>| >>>>connect to each other using a trusted connection.
>| >>>>
>| >>>> If I try to remotely connect to the Xp Pro machine from the Home
>| >>>> machine
>| >>>>using windows authentication, everything works fine. But, if I try to
>| >>>>remotely connect to the Home machine it says that login failed for
>| >>>>Server\Guest. My understanding is that it tries to log in as guest if
>| >>>>the
>| >>>>windows account is not found.
>| >>>>
>| >>>> Why does it work on one computer but not the other? Is it because
>it
>| >>>> is
>| >>>>Home edition? Is there something else I need to do?
>| >>>>
>| >>>> BTW, standard authentication works fine on both machines and the
>| >>>> Guest
>| >>>>account is turned off.
>| >>>>
>| >>>> Thanks,
>| >>>> Maer
>| >>>>
>| >>>
>| >>
>| >
>|
>|
>|
|||Not in terms of the same type of thing with the guest
account.When it's a specific account failing, that's a
different matter than attempted authentication via the guest
account.
-Sue
On Thu, 10 Feb 2005 19:33:17 -0500, "Maer"
<maer@.auditleverage.com> wrote:

> Thank you, Sue. Your suggestion seems to be the way to go.
> I have noticed that when I try to log in using Windows Authentication to
>a Windows 2000 machine from my XP machine, it tries to log me in as
>"Server\Administrator" and, of course, fails. My account is part of the
>Administrator's group. However, the other way around (from Win 2000 to XP)
>works fine.
> Is there a limitation in Windows 2000 too?
> Thanks again,
> Maer
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com.. .
>
|||Hello Sue,
I agree with you that WinXP home has this issue because of simple file
sharing. I mean that it is not a limitation in Win2000. It shall work the
same as WinXP pro based on my test. Sorry for the confustion brought. :-)
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| From: Sue Hoegemeier <Sue_H@.nomail.please>
| Subject: Re: Login failed for Server\Guest
| Date: Mon, 14 Feb 2005 07:44:48 -0700
| Message-ID: <c6e111poj51vkc5a37vs1kjbq92c46f2g6@.4ax.com>
| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
<k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
<#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
<gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
<eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
<pgtqGQmEFHA.3900@.TK2MSFTNGXA01.phx.gbl>
| X-Newsreader: Forte Agent 2.0/32.652
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.sqlserver.connect
| NNTP-Posting-Host: 0-2pool82-42.nas33.thornton1.co.us.da.qwest.net
67.4.82.42
| Lines: 1
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msft ngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3422
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Peter,
| Not necessarily. In your testing, I would guess you are
| using XP Pro and do not have simple file sharing enabled.
| There are scenarios with XP where you are authenticated as
| guest and the use of the same account/password does not
| work. Refer to the following knowledge base article:
| SQL Server clients are authenticated as guests if Simple
| File Sharing is enabled
| http://support.microsoft.com/?id=831133
|
| -Sue
|
| On Mon, 14 Feb 2005 07:08:38 GMT,
| petery@.online.microsoft.com (Peter Yang [MSFT]) wrote:
|
| >Hello Maer,
| >
| >I think it is not a limitation in Windows 2000. Based on my test, I
could
| >access SQL server on Win2000 server by using Windows authenctication if
I
| >use same password for Administrator account on both Win2000 and WinXP
| >computers. I suggest that you check security policy settings on both
| >computers to see if they match:
| >
| >1. Run gpedit.msc
| >
| >2. Check Computer configuration->Windows settings->Security
Settings->Local
| >Policies->Security Options and make sure the following settings:
| >
| >Digitally sign client communication (always)Not defined
| >
| >Digitally sign client communication (when possible)Not defined
| >
| >Digitally sign server communication (always)Not defined
| >
| >Digitally sign server communication (when possible)Not defined
| >
| >LAN Manager Authentication LevelNot defined
| >
| >Secure channel: Digitally encrypt or sign secure channel data (always)
Not
| >defined
| >
| >Secure channel: Digitally encrypt secure channel data (when possible)
Not
| >defined
| >
| >Secure channel: Digitally sign secure channel data (when possible)Not
| >defined
| >
| >Secure channel: Require strong (Windows 2000 or later) session keyNot
| >defined
| >
| >3. Check Computer configuration->Windows settings->Security
Settings->Local
| >Policies->User Rights assigment, and make sure Deny access this computer
| >from network is not configured.
| >
| >Thanks & Regards,
| >
| >Peter Yang
| >MCSE2000/2003, MCSA, MCDBA
| >Microsoft Online Partner Support
| >
| >When responding to posts, please "Reply to Group" via your newsreader so
| >that others may learn and benefit from your issue.
| >
| >================================================= ====
| >
| >This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| >
| >
| >
| >--
| >| From: "Maer" <maer@.auditleverage.com>
| >| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
| ><k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
| ><#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
| ><gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
| >| Subject: Re: Login failed for Server\Guest
| >| Date: Thu, 10 Feb 2005 19:33:17 -0500
| >| Lines: 87
| >| X-Priority: 3
| >| X-MSMail-Priority: Normal
| >| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| >| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| >| X-RFC2646: Format=Flowed; Original
| >| Message-ID: <eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
| >| Newsgroups: microsoft.public.sqlserver.connect
| >| NNTP-Posting-Host: pcp08367474pcs.lndsd201.pa.comcast.net 68.42.29.253
| >| Path:
|
>TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSF TNGP08.phx.gbl!TK2MSFTNGP1
2
| >phx.gbl
| >| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3409
| >| X-Tomcat-NG: microsoft.public.sqlserver.connect
| >|
| >| Thank you, Sue. Your suggestion seems to be the way to go.
| >|
| >| I have noticed that when I try to log in using Windows
Authentication
| >to
| >| a Windows 2000 machine from my XP machine, it tries to log me in as
| >| "Server\Administrator" and, of course, fails. My account is part of
the
| >| Administrator's group. However, the other way around (from Win 2000 to
| >XP)
| >| works fine.
| >|
| >| Is there a limitation in Windows 2000 too?
| >|
| >| Thanks again,
| >| Maer
| >|
| >|
| >|
| >| "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
| >| news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com...
| >| > Hi Maer,
| >| > You can enable the guest account but that's a security risk
| >| > - especially if exposed to the outside world. For SQL
| >| > Server, although Windows Authentication is more secure than
| >| > SQL Authentication, I'd probably use that option instead of
| >| > enabling the guest account. Make sure to turn on security
| >| > audits, limit the number of SQL logins and make sure all SQL
| >| > logins have strong passwords - mixed case, alpha numeric
| >| > with special characters, no known words, etc.
| >| >
| >| > -Sue
| >| >
| >| > On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
| >| > <maer@.auditleverage.com> wrote:
| >| >
| >| >> Thank you, Sue!
| >| >>
| >| >> That clarifies so much! Would I be right in assuming that using
| >| >> windows
| >| >>authentication is not an option when logging in remotely to Xp Home
| >since
| >| >>it
| >| >>always uses Guest? Is there a work-around?
| >| >>
| >| >> Maer
| >| >>
| >| >>
| >| >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
| >| >>news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com. ..
| >| >>> With XP home, authentication is done using the guest account
| >| >>> as simple file sharing is always enabled on XP Home. Refer
| >| >>> to the following for more info:
| >| >>> SQL Server clients are authenticated as guests if Simple
| >| >>> File Sharing is enabled
| >| >>> http://support.microsoft.com/?id=831133
| >| >>>
| >| >>> -Sue
| >| >>>
| >| >>> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
| >| >>> <maer@.auditleverage.com> wrote:
| >| >>>
| >| >>>> Hi - I have two computers, one running Xp Pro and one Xp Home.
I
| >| >>>> created
| >| >>>>a windows user account on both machines with the same password. I
| >added
| >| >>>>those accounts to SQL Server on both machines and I want to be
able to
| >| >>>>connect to each other using a trusted connection.
| >| >>>>
| >| >>>> If I try to remotely connect to the Xp Pro machine from the
Home
| >| >>>> machine
| >| >>>>using windows authentication, everything works fine. But, if I try
to
| >| >>>>remotely connect to the Home machine it says that login failed for
| >| >>>>Server\Guest. My understanding is that it tries to log in as guest
if
| >| >>>>the
| >| >>>>windows account is not found.
| >| >>>>
| >| >>>> Why does it work on one computer but not the other? Is it
because
| >it
| >| >>>> is
| >| >>>>Home edition? Is there something else I need to do?
| >| >>>>
| >| >>>> BTW, standard authentication works fine on both machines and
the
| >| >>>> Guest
| >| >>>>account is turned off.
| >| >>>>
| >| >>>> Thanks,
| >| >>>> Maer
| >| >>>>
| >| >>>
| >| >>
| >| >
| >|
| >|
| >|
|
|
|||No problem...I just didn't want the poster or anyone
following to get confused! As I posted back, the issue hit
the second time around would be different as the login
failed for Administrator not guest. Even though it wasn't
explained which version of XP was used on the second case,
it would likely have been XP Pro without simple file sharing
enabled and consequently more likely related to security
settings.
-Sue
On Tue, 15 Feb 2005 04:13:27 GMT,
petery@.online.microsoft.com (Peter Yang [MSFT]) wrote:

>Hello Sue,
>I agree with you that WinXP home has this issue because of simple file
>sharing. I mean that it is not a limitation in Win2000. It shall work the
>same as WinXP pro based on my test. Sorry for the confustion brought. :-)
>Best Regards,
>Peter Yang
>MCSE2000/2003, MCSA, MCDBA
>Microsoft Online Partner Support
>When responding to posts, please "Reply to Group" via your newsreader so
>that others may learn and benefit from your issue.
>================================================= ====
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>--
>| From: Sue Hoegemeier <Sue_H@.nomail.please>
>| Subject: Re: Login failed for Server\Guest
>| Date: Mon, 14 Feb 2005 07:44:48 -0700
>| Message-ID: <c6e111poj51vkc5a37vs1kjbq92c46f2g6@.4ax.com>
>| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
><k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
><#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
><gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
><eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
><pgtqGQmEFHA.3900@.TK2MSFTNGXA01.phx.gbl>
>| X-Newsreader: Forte Agent 2.0/32.652
>| MIME-Version: 1.0
>| Content-Type: text/plain; charset=us-ascii
>| Content-Transfer-Encoding: 7bit
>| Newsgroups: microsoft.public.sqlserver.connect
>| NNTP-Posting-Host: 0-2pool82-42.nas33.thornton1.co.us.da.qwest.net
>67.4.82.42
>| Lines: 1
>| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msft ngp13.phx.gbl
>| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3422
>| X-Tomcat-NG: microsoft.public.sqlserver.connect
>|
>| Peter,
>| Not necessarily. In your testing, I would guess you are
>| using XP Pro and do not have simple file sharing enabled.
>| There are scenarios with XP where you are authenticated as
>| guest and the use of the same account/password does not
>| work. Refer to the following knowledge base article:
>| SQL Server clients are authenticated as guests if Simple
>| File Sharing is enabled
>| http://support.microsoft.com/?id=831133
>|
>| -Sue
>|
>| On Mon, 14 Feb 2005 07:08:38 GMT,
>| petery@.online.microsoft.com (Peter Yang [MSFT]) wrote:
>|
>| >Hello Maer,
>| >
>| >I think it is not a limitation in Windows 2000. Based on my test, I
>could
>| >access SQL server on Win2000 server by using Windows authenctication if
>I
>| >use same password for Administrator account on both Win2000 and WinXP
>| >computers. I suggest that you check security policy settings on both
>| >computers to see if they match:
>| >
>| >1. Run gpedit.msc
>| >
>| >2. Check Computer configuration->Windows settings->Security
>Settings->Local
>| >Policies->Security Options and make sure the following settings:
>| >
>| >Digitally sign client communication (always)Not defined
>| >
>| >Digitally sign client communication (when possible)Not defined
>| >
>| >Digitally sign server communication (always)Not defined
>| >
>| >Digitally sign server communication (when possible)Not defined
>| >
>| >LAN Manager Authentication LevelNot defined
>| >
>| >Secure channel: Digitally encrypt or sign secure channel data (always)
>Not
>| >defined
>| >
>| >Secure channel: Digitally encrypt secure channel data (when possible)
>Not
>| >defined
>| >
>| >Secure channel: Digitally sign secure channel data (when possible)Not
>| >defined
>| >
>| >Secure channel: Require strong (Windows 2000 or later) session keyNot
>| >defined
>| >
>| >3. Check Computer configuration->Windows settings->Security
>Settings->Local
>| >Policies->User Rights assigment, and make sure Deny access this computer
>| >from network is not configured.
>| >
>| >Thanks & Regards,
>| >
>| >Peter Yang
>| >MCSE2000/2003, MCSA, MCDBA
>| >Microsoft Online Partner Support
>| >
>| >When responding to posts, please "Reply to Group" via your newsreader so
>| >that others may learn and benefit from your issue.
>| >
>| >================================================= ====
>| >
>| >This posting is provided "AS IS" with no warranties, and confers no
>rights.
>| >
>| >
>| >
>| >
>| >--
>| >| From: "Maer" <maer@.auditleverage.com>
>| >| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
>| ><k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
>| ><#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
>| ><gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
>| >| Subject: Re: Login failed for Server\Guest
>| >| Date: Thu, 10 Feb 2005 19:33:17 -0500
>| >| Lines: 87
>| >| X-Priority: 3
>| >| X-MSMail-Priority: Normal
>| >| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>| >| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>| >| X-RFC2646: Format=Flowed; Original
>| >| Message-ID: <eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
>| >| Newsgroups: microsoft.public.sqlserver.connect
>| >| NNTP-Posting-Host: pcp08367474pcs.lndsd201.pa.comcast.net 68.42.29.253
>| >| Path:
>|
>2
>| >phx.gbl
>| >| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3409
>| >| X-Tomcat-NG: microsoft.public.sqlserver.connect
>| >|
>| >| Thank you, Sue. Your suggestion seems to be the way to go.
>| >|
>| >| I have noticed that when I try to log in using Windows
>Authentication
>| >to
>| >| a Windows 2000 machine from my XP machine, it tries to log me in as
>| >| "Server\Administrator" and, of course, fails. My account is part of
>the
>| >| Administrator's group. However, the other way around (from Win 2000 to
>| >XP)
>| >| works fine.
>| >|
>| >| Is there a limitation in Windows 2000 too?
>| >|
>| >| Thanks again,
>| >| Maer
>| >|
>| >|
>| >|
>| >| "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>| >| news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com...
>| >| > Hi Maer,
>| >| > You can enable the guest account but that's a security risk
>| >| > - especially if exposed to the outside world. For SQL
>| >| > Server, although Windows Authentication is more secure than
>| >| > SQL Authentication, I'd probably use that option instead of
>| >| > enabling the guest account. Make sure to turn on security
>| >| > audits, limit the number of SQL logins and make sure all SQL
>| >| > logins have strong passwords - mixed case, alpha numeric
>| >| > with special characters, no known words, etc.
>| >| >
>| >| > -Sue
>| >| >
>| >| > On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
>| >| > <maer@.auditleverage.com> wrote:
>| >| >
>| >| >> Thank you, Sue!
>| >| >>
>| >| >> That clarifies so much! Would I be right in assuming that using
>| >| >> windows
>| >| >>authentication is not an option when logging in remotely to Xp Home
>| >since
>| >| >>it
>| >| >>always uses Guest? Is there a work-around?
>| >| >>
>| >| >> Maer
>| >| >>
>| >| >>
>| >| >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>| >| >>news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com. ..
>| >| >>> With XP home, authentication is done using the guest account
>| >| >>> as simple file sharing is always enabled on XP Home. Refer
>| >| >>> to the following for more info:
>| >| >>> SQL Server clients are authenticated as guests if Simple
>| >| >>> File Sharing is enabled
>| >| >>> http://support.microsoft.com/?id=831133
>| >| >>>
>| >| >>> -Sue
>| >| >>>
>| >| >>> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
>| >| >>> <maer@.auditleverage.com> wrote:
>| >| >>>
>| >| >>>> Hi - I have two computers, one running Xp Pro and one Xp Home.
>I
>| >| >>>> created
>| >| >>>>a windows user account on both machines with the same password. I
>| >added
>| >| >>>>those accounts to SQL Server on both machines and I want to be
>able to
>| >| >>>>connect to each other using a trusted connection.
>| >| >>>>
>| >| >>>> If I try to remotely connect to the Xp Pro machine from the
>Home
>| >| >>>> machine
>| >| >>>>using windows authentication, everything works fine. But, if I try
>to
>| >| >>>>remotely connect to the Home machine it says that login failed for
>| >| >>>>Server\Guest. My understanding is that it tries to log in as guest
>if
>| >| >>>>the
>| >| >>>>windows account is not found.
>| >| >>>>
>| >| >>>> Why does it work on one computer but not the other? Is it
>because
>| >it
>| >| >>>> is
>| >| >>>>Home edition? Is there something else I need to do?
>| >| >>>>
>| >| >>>> BTW, standard authentication works fine on both machines and
>the
>| >| >>>> Guest
>| >| >>>>account is turned off.
>| >| >>>>
>| >| >>>> Thanks,
>| >| >>>> Maer
>| >| >>>>
>| >| >>>
>| >| >>
>| >| >
>| >|
>| >|
>| >|
>|
>|

Login failed for Server\Guest

Hi - I have two computers, one running Xp Pro and one Xp Home. I created
a windows user account on both machines with the same password. I added
those accounts to SQL Server on both machines and I want to be able to
connect to each other using a trusted connection.
If I try to remotely connect to the Xp Pro machine from the Home machine
using windows authentication, everything works fine. But, if I try to
remotely connect to the Home machine it says that login failed for
Server\Guest. My understanding is that it tries to log in as guest if the
windows account is not found.
Why does it work on one computer but not the other? Is it because it is
Home edition? Is there something else I need to do?
BTW, standard authentication works fine on both machines and the Guest
account is turned off.
Thanks,
MaerWith XP home, authentication is done using the guest account
as simple file sharing is always enabled on XP Home. Refer
to the following for more info:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/?id=831133
-Sue
On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
<maer@.auditleverage.com> wrote:

> Hi - I have two computers, one running Xp Pro and one Xp Home. I create
d
>a windows user account on both machines with the same password. I added
>those accounts to SQL Server on both machines and I want to be able to
>connect to each other using a trusted connection.
> If I try to remotely connect to the Xp Pro machine from the Home machin
e
>using windows authentication, everything works fine. But, if I try to
>remotely connect to the Home machine it says that login failed for
>Server\Guest. My understanding is that it tries to log in as guest if the
>windows account is not found.
> Why does it work on one computer but not the other? Is it because it is
>Home edition? Is there something else I need to do?
> BTW, standard authentication works fine on both machines and the Guest
>account is turned off.
> Thanks,
> Maer
>|||Thank you, Sue!
That clarifies so much! Would I be right in assuming that using windows
authentication is not an option when logging in remotely to Xp Home since it
always uses Guest? Is there a work-around?
Maer
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.
4ax.com...
> With XP home, authentication is done using the guest account
> as simple file sharing is always enabled on XP Home. Refer
> to the following for more info:
> SQL Server clients are authenticated as guests if Simple
> File Sharing is enabled
> http://support.microsoft.com/?id=831133
> -Sue
> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
> <maer@.auditleverage.com> wrote:
>
>|||Hi Maer,
You can enable the guest account but that's a security risk
- especially if exposed to the outside world. For SQL
Server, although Windows Authentication is more secure than
SQL Authentication, I'd probably use that option instead of
enabling the guest account. Make sure to turn on security
audits, limit the number of SQL logins and make sure all SQL
logins have strong passwords - mixed case, alpha numeric
with special characters, no known words, etc.
-Sue
On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
<maer@.auditleverage.com> wrote:

> Thank you, Sue!
> That clarifies so much! Would I be right in assuming that using windows
>authentication is not an option when logging in remotely to Xp Home since i
t
>always uses Guest? Is there a work-around?
> Maer
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.
4ax.com...
>|||Thank you, Sue. Your suggestion seems to be the way to go.
I have noticed that when I try to log in using Windows Authentication to
a Windows 2000 machine from my XP machine, it tries to log me in as
"Server\Administrator" and, of course, fails. My account is part of the
Administrator's group. However, the other way around (from Win 2000 to XP)
works fine.
Is there a limitation in Windows 2000 too?
Thanks again,
Maer
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.
4ax.com...
> Hi Maer,
> You can enable the guest account but that's a security risk
> - especially if exposed to the outside world. For SQL
> Server, although Windows Authentication is more secure than
> SQL Authentication, I'd probably use that option instead of
> enabling the guest account. Make sure to turn on security
> audits, limit the number of SQL logins and make sure all SQL
> logins have strong passwords - mixed case, alpha numeric
> with special characters, no known words, etc.
> -Sue
> On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
> <maer@.auditleverage.com> wrote:
>
>|||Hello Maer,
I think it is not a limitation in Windows 2000. Based on my test, I could
access SQL server on Win2000 server by using Windows authenctication if I
use same password for Administrator account on both Win2000 and WinXP
computers. I suggest that you check security policy settings on both
computers to see if they match:
1. Run gpedit.msc
2. Check Computer configuration->Windows settings->Security Settings->Local
Policies->Security Options and make sure the following settings:
Digitally sign client communication (always) Not defined
Digitally sign client communication (when possible) Not defined
Digitally sign server communication (always) Not defined
Digitally sign server communication (when possible) Not defined
LAN Manager Authentication Level Not defined
Secure channel: Digitally encrypt or sign secure channel data (always) Not
defined
Secure channel: Digitally encrypt secure channel data (when possible) Not
defined
Secure channel: Digitally sign secure channel data (when possible) Not
defined
Secure channel: Require strong (Windows 2000 or later) session key Not
defined
3. Check Computer configuration->Windows settings->Security Settings->Local
Policies->User Rights assigment, and make sure Deny access this computer
from network is not configured.
Thanks & Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| From: "Maer" <maer@.auditleverage.com>
| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
<k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
<#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
<gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
| Subject: Re: Login failed for Server\Guest
| Date: Thu, 10 Feb 2005 19:33:17 -0500
| Lines: 87
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.connect
| NNTP-Posting-Host: pcp08367474pcs.lndsd201.pa.comcast.net 68.42.29.253
| Path:
TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3409
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Thank you, Sue. Your suggestion seems to be the way to go.
|
| I have noticed that when I try to log in using Windows Authentication
to
| a Windows 2000 machine from my XP machine, it tries to log me in as
| "Server\Administrator" and, of course, fails. My account is part of the
| Administrator's group. However, the other way around (from Win 2000 to
XP)
| works fine.
|
| Is there a limitation in Windows 2000 too?
|
| Thanks again,
| Maer
|
|
|
| "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
| news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.
4ax.com...
| > Hi Maer,
| > You can enable the guest account but that's a security risk
| > - especially if exposed to the outside world. For SQL
| > Server, although Windows Authentication is more secure than
| > SQL Authentication, I'd probably use that option instead of
| > enabling the guest account. Make sure to turn on security
| > audits, limit the number of SQL logins and make sure all SQL
| > logins have strong passwords - mixed case, alpha numeric
| > with special characters, no known words, etc.
| >
| > -Sue
| >
| > On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
| > <maer@.auditleverage.com> wrote:
| >
| >> Thank you, Sue!
| >>
| >> That clarifies so much! Would I be right in assuming that using
| >> windows
| >>authentication is not an option when logging in remotely to Xp Home
since
| >>it
| >>always uses Guest? Is there a work-around?
| >>
| >> Maer
| >>
| >>
| >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
| >> news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.
4ax.com...
| >>> With XP home, authentication is done using the guest account
| >>> as simple file sharing is always enabled on XP Home. Refer
| >>> to the following for more info:
| >>> SQL Server clients are authenticated as guests if Simple
| >>> File Sharing is enabled
| >>> http://support.microsoft.com/?id=831133
| >>>
| >>> -Sue
| >>>
| >>> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
| >>> <maer@.auditleverage.com> wrote:
| >>>
| >>>> Hi - I have two computers, one running Xp Pro and one Xp Home. I
| >>>> created
| >>>>a windows user account on both machines with the same password. I
added
| >>>>those accounts to SQL Server on both machines and I want to be able to
| >>>>connect to each other using a trusted connection.
| >>>>
| >>>> If I try to remotely connect to the Xp Pro machine from the Home
| >>>> machine
| >>>>using windows authentication, everything works fine. But, if I try to
| >>>>remotely connect to the Home machine it says that login failed for
| >>>>Server\Guest. My understanding is that it tries to log in as guest if
| >>>>the
| >>>>windows account is not found.
| >>>>
| >>>> Why does it work on one computer but not the other? Is it because
it
| >>>> is
| >>>>Home edition? Is there something else I need to do?
| >>>>
| >>>> BTW, standard authentication works fine on both machines and the
| >>>> Guest
| >>>>account is turned off.
| >>>>
| >>>> Thanks,
| >>>> Maer
| >>>>
| >>>
| >>
| >
|
|
||||Peter,
Not necessarily. In your testing, I would guess you are
using XP Pro and do not have simple file sharing enabled.
There are scenarios with XP where you are authenticated as
guest and the use of the same account/password does not
work. Refer to the following knowledge base article:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/?id=831133
-Sue
On Mon, 14 Feb 2005 07:08:38 GMT,
petery@.online.microsoft.com (Peter Yang [MSFT]) wrote:

>Hello Maer,
>I think it is not a limitation in Windows 2000. Based on my test, I could
>access SQL server on Win2000 server by using Windows authenctication if I
>use same password for Administrator account on both Win2000 and WinXP
>computers. I suggest that you check security policy settings on both
>computers to see if they match:
>1. Run gpedit.msc
>2. Check Computer configuration->Windows settings->Security Settings->Local
>Policies->Security Options and make sure the following settings:
>Digitally sign client communication (always) Not defined
>Digitally sign client communication (when possible) Not defined
>Digitally sign server communication (always) Not defined
>Digitally sign server communication (when possible) Not defined
>LAN Manager Authentication Level Not defined
>Secure channel: Digitally encrypt or sign secure channel data (always) Not
>defined
>Secure channel: Digitally encrypt secure channel data (when possible) Not
>defined
>Secure channel: Digitally sign secure channel data (when possible) Not
>defined
>Secure channel: Require strong (Windows 2000 or later) session key Not
>defined
>3. Check Computer configuration->Windows settings->Security Settings->Local
>Policies->User Rights assigment, and make sure Deny access this computer
>from network is not configured.
>Thanks & Regards,
>Peter Yang
>MCSE2000/2003, MCSA, MCDBA
>Microsoft Online Partner Support
>When responding to posts, please "Reply to Group" via your newsreader so
>that others may learn and benefit from your issue.
> ========================================
=============
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>--
>| From: "Maer" <maer@.auditleverage.com>
>| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
><k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
><#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
><gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
>| Subject: Re: Login failed for Server\Guest
>| Date: Thu, 10 Feb 2005 19:33:17 -0500
>| Lines: 87
>| X-Priority: 3
>| X-MSMail-Priority: Normal
>| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>| X-RFC2646: Format=Flowed; Original
>| Message-ID: <eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
>| Newsgroups: microsoft.public.sqlserver.connect
>| NNTP-Posting-Host: pcp08367474pcs.lndsd201.pa.comcast.net 68.42.29.253
>| Path:
>TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP1
2
>phx.gbl
>| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3409
>| X-Tomcat-NG: microsoft.public.sqlserver.connect
>|
>| Thank you, Sue. Your suggestion seems to be the way to go.
>|
>| I have noticed that when I try to log in using Windows Authentication
>to
>| a Windows 2000 machine from my XP machine, it tries to log me in as
>| "Server\Administrator" and, of course, fails. My account is part of the
>| Administrator's group. However, the other way around (from Win 2000 to
>XP)
>| works fine.
>|
>| Is there a limitation in Windows 2000 too?
>|
>| Thanks again,
>| Maer
>|
>|
>|
>| "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>| news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.
4ax.com...
>| > Hi Maer,
>| > You can enable the guest account but that's a security risk
>| > - especially if exposed to the outside world. For SQL
>| > Server, although Windows Authentication is more secure than
>| > SQL Authentication, I'd probably use that option instead of
>| > enabling the guest account. Make sure to turn on security
>| > audits, limit the number of SQL logins and make sure all SQL
>| > logins have strong passwords - mixed case, alpha numeric
>| > with special characters, no known words, etc.
>| >
>| > -Sue
>| >
>| > On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
>| > <maer@.auditleverage.com> wrote:
>| >
>| >> Thank you, Sue!
>| >>
>| >> That clarifies so much! Would I be right in assuming that using
>| >> windows
>| >>authentication is not an option when logging in remotely to Xp Home
>since
>| >>it
>| >>always uses Guest? Is there a work-around?
>| >>
>| >> Maer
>| >>
>| >>
>| >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>| >> news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.
4ax.com...
>| >>> With XP home, authentication is done using the guest account
>| >>> as simple file sharing is always enabled on XP Home. Refer
>| >>> to the following for more info:
>| >>> SQL Server clients are authenticated as guests if Simple
>| >>> File Sharing is enabled
>| >>> http://support.microsoft.com/?id=831133
>| >>>
>| >>> -Sue
>| >>>
>| >>> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
>| >>> <maer@.auditleverage.com> wrote:
>| >>>
>| >>>> Hi - I have two computers, one running Xp Pro and one Xp Home. I
>| >>>> created
>| >>>>a windows user account on both machines with the same password. I
>added
>| >>>>those accounts to SQL Server on both machines and I want to be able t
o
>| >>>>connect to each other using a trusted connection.
>| >>>>
>| >>>> If I try to remotely connect to the Xp Pro machine from the Home
>| >>>> machine
>| >>>>using windows authentication, everything works fine. But, if I try to
>| >>>>remotely connect to the Home machine it says that login failed for
>| >>>>Server\Guest. My understanding is that it tries to log in as guest if
>| >>>>the
>| >>>>windows account is not found.
>| >>>>
>| >>>> Why does it work on one computer but not the other? Is it because
>it
>| >>>> is
>| >>>>Home edition? Is there something else I need to do?
>| >>>>
>| >>>> BTW, standard authentication works fine on both machines and the
>| >>>> Guest
>| >>>>account is turned off.
>| >>>>
>| >>>> Thanks,
>| >>>> Maer
>| >>>>
>| >>>
>| >>
>| >
>|
>|
>||||Not in terms of the same type of thing with the guest
account.When it's a specific account failing, that's a
different matter than attempted authentication via the guest
account.
-Sue
On Thu, 10 Feb 2005 19:33:17 -0500, "Maer"
<maer@.auditleverage.com> wrote:

> Thank you, Sue. Your suggestion seems to be the way to go.
> I have noticed that when I try to log in using Windows Authentication t
o
>a Windows 2000 machine from my XP machine, it tries to log me in as
>"Server\Administrator" and, of course, fails. My account is part of the
>Administrator's group. However, the other way around (from Win 2000 to XP)
>works fine.
> Is there a limitation in Windows 2000 too?
> Thanks again,
> Maer
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.
4ax.com...
>|||Hello Sue,
I agree with you that WinXP home has this issue because of simple file
sharing. I mean that it is not a limitation in Win2000. It shall work the
same as WinXP pro based on my test. Sorry for the confustion brought. :-)
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| From: Sue Hoegemeier <Sue_H@.nomail.please>
| Subject: Re: Login failed for Server\Guest
| Date: Mon, 14 Feb 2005 07:44:48 -0700
| Message-ID: <c6e111poj51vkc5a37vs1kjbq92c46f2g6@.4ax.com>
| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
<k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
<#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
<gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
<eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
<pgtqGQmEFHA.3900@.TK2MSFTNGXA01.phx.gbl>
| X-Newsreader: Forte Agent 2.0/32.652
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.sqlserver.connect
| NNTP-Posting-Host: 0-2pool82-42.nas33.thornton1.co.us.da.qwest.net
67.4.82.42
| Lines: 1
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3422
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Peter,
| Not necessarily. In your testing, I would guess you are
| using XP Pro and do not have simple file sharing enabled.
| There are scenarios with XP where you are authenticated as
| guest and the use of the same account/password does not
| work. Refer to the following knowledge base article:
| SQL Server clients are authenticated as guests if Simple
| File Sharing is enabled
| http://support.microsoft.com/?id=831133
|
| -Sue
|
| On Mon, 14 Feb 2005 07:08:38 GMT,
| petery@.online.microsoft.com (Peter Yang [MSFT]) wrote:
|
| >Hello Maer,
| >
| >I think it is not a limitation in Windows 2000. Based on my test, I
could
| >access SQL server on Win2000 server by using Windows authenctication if
I
| >use same password for Administrator account on both Win2000 and WinXP
| >computers. I suggest that you check security policy settings on both
| >computers to see if they match:
| >
| >1. Run gpedit.msc
| >
| >2. Check Computer configuration->Windows settings->Security
Settings->Local
| >Policies->Security Options and make sure the following settings:
| >
| >Digitally sign client communication (always) Not defined
| >
| >Digitally sign client communication (when possible) Not defined
| >
| >Digitally sign server communication (always) Not defined
| >
| >Digitally sign server communication (when possible) Not defined
| >
| >LAN Manager Authentication Level Not defined
| >
| >Secure channel: Digitally encrypt or sign secure channel data (always)
Not
| >defined
| >
| >Secure channel: Digitally encrypt secure channel data (when possible)
Not
| >defined
| >
| >Secure channel: Digitally sign secure channel data (when possible) Not
| >defined
| >
| >Secure channel: Require strong (Windows 2000 or later) session key Not
| >defined
| >
| >3. Check Computer configuration->Windows settings->Security
Settings->Local
| >Policies->User Rights assigment, and make sure Deny access this computer
| >from network is not configured.
| >
| >Thanks & Regards,
| >
| >Peter Yang
| >MCSE2000/2003, MCSA, MCDBA
| >Microsoft Online Partner Support
| >
| >When responding to posts, please "Reply to Group" via your newsreader so
| >that others may learn and benefit from your issue.
| >
| > ========================================
=============
| >
| >This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| >
| >
| >
| >--
| >| From: "Maer" <maer@.auditleverage.com>
| >| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
| ><k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
| ><#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
| ><gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
| >| Subject: Re: Login failed for Server\Guest
| >| Date: Thu, 10 Feb 2005 19:33:17 -0500
| >| Lines: 87
| >| X-Priority: 3
| >| X-MSMail-Priority: Normal
| >| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| >| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| >| X-RFC2646: Format=Flowed; Original
| >| Message-ID: <eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
| >| Newsgroups: microsoft.public.sqlserver.connect
| >| NNTP-Posting-Host: pcp08367474pcs.lndsd201.pa.comcast.net 68.42.29.253
| >| Path:
|
>TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP1
2
| >phx.gbl
| >| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3409
| >| X-Tomcat-NG: microsoft.public.sqlserver.connect
| >|
| >| Thank you, Sue. Your suggestion seems to be the way to go.
| >|
| >| I have noticed that when I try to log in using Windows
Authentication
| >to
| >| a Windows 2000 machine from my XP machine, it tries to log me in as
| >| "Server\Administrator" and, of course, fails. My account is part of
the
| >| Administrator's group. However, the other way around (from Win 2000 to
| >XP)
| >| works fine.
| >|
| >| Is there a limitation in Windows 2000 too?
| >|
| >| Thanks again,
| >| Maer
| >|
| >|
| >|
| >| "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
| >| news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.
4ax.com...
| >| > Hi Maer,
| >| > You can enable the guest account but that's a security risk
| >| > - especially if exposed to the outside world. For SQL
| >| > Server, although Windows Authentication is more secure than
| >| > SQL Authentication, I'd probably use that option instead of
| >| > enabling the guest account. Make sure to turn on security
| >| > audits, limit the number of SQL logins and make sure all SQL
| >| > logins have strong passwords - mixed case, alpha numeric
| >| > with special characters, no known words, etc.
| >| >
| >| > -Sue
| >| >
| >| > On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
| >| > <maer@.auditleverage.com> wrote:
| >| >
| >| >> Thank you, Sue!
| >| >>
| >| >> That clarifies so much! Would I be right in assuming that using
| >| >> windows
| >| >>authentication is not an option when logging in remotely to Xp Home
| >since
| >| >>it
| >| >>always uses Guest? Is there a work-around?
| >| >>
| >| >> Maer
| >| >>
| >| >>
| >| >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
| >| >> news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.
4ax.com...
| >| >>> With XP home, authentication is done using the guest account
| >| >>> as simple file sharing is always enabled on XP Home. Refer
| >| >>> to the following for more info:
| >| >>> SQL Server clients are authenticated as guests if Simple
| >| >>> File Sharing is enabled
| >| >>> http://support.microsoft.com/?id=831133
| >| >>>
| >| >>> -Sue
| >| >>>
| >| >>> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
| >| >>> <maer@.auditleverage.com> wrote:
| >| >>>
| >| >>>> Hi - I have two computers, one running Xp Pro and one Xp Home.
I
| >| >>>> created
| >| >>>>a windows user account on both machines with the same password. I
| >added
| >| >>>>those accounts to SQL Server on both machines and I want to be
able to
| >| >>>>connect to each other using a trusted connection.
| >| >>>>
| >| >>>> If I try to remotely connect to the Xp Pro machine from the
Home
| >| >>>> machine
| >| >>>>using windows authentication, everything works fine. But, if I try
to
| >| >>>>remotely connect to the Home machine it says that login failed for
| >| >>>>Server\Guest. My understanding is that it tries to log in as guest
if
| >| >>>>the
| >| >>>>windows account is not found.
| >| >>>>
| >| >>>> Why does it work on one computer but not the other? Is it
because
| >it
| >| >>>> is
| >| >>>>Home edition? Is there something else I need to do?
| >| >>>>
| >| >>>> BTW, standard authentication works fine on both machines and
the
| >| >>>> Guest
| >| >>>>account is turned off.
| >| >>>>
| >| >>>> Thanks,
| >| >>>> Maer
| >| >>>>
| >| >>>
| >| >>
| >| >
| >|
| >|
| >|
|
||||No problem...I just didn't want the poster or anyone
following to get confused! As I posted back, the issue hit
the second time around would be different as the login
failed for Administrator not guest. Even though it wasn't
explained which version of XP was used on the second case,
it would likely have been XP Pro without simple file sharing
enabled and consequently more likely related to security
settings.
-Sue
On Tue, 15 Feb 2005 04:13:27 GMT,
petery@.online.microsoft.com (Peter Yang [MSFT]) wrote:

>Hello Sue,
>I agree with you that WinXP home has this issue because of simple file
>sharing. I mean that it is not a limitation in Win2000. It shall work the
>same as WinXP pro based on my test. Sorry for the confustion brought. :-)
>Best Regards,
>Peter Yang
>MCSE2000/2003, MCSA, MCDBA
>Microsoft Online Partner Support
>When responding to posts, please "Reply to Group" via your newsreader so
>that others may learn and benefit from your issue.
> ========================================
=============
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>--
>| From: Sue Hoegemeier <Sue_H@.nomail.please>
>| Subject: Re: Login failed for Server\Guest
>| Date: Mon, 14 Feb 2005 07:44:48 -0700
>| Message-ID: <c6e111poj51vkc5a37vs1kjbq92c46f2g6@.4ax.com>
>| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
><k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
><#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
><gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
><eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
><pgtqGQmEFHA.3900@.TK2MSFTNGXA01.phx.gbl>
>| X-Newsreader: Forte Agent 2.0/32.652
>| MIME-Version: 1.0
>| Content-Type: text/plain; charset=us-ascii
>| Content-Transfer-Encoding: 7bit
>| Newsgroups: microsoft.public.sqlserver.connect
>| NNTP-Posting-Host: 0-2pool82-42.nas33.thornton1.co.us.da.qwest.net
>67.4.82.42
>| Lines: 1
>| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3422
>| X-Tomcat-NG: microsoft.public.sqlserver.connect
>|
>| Peter,
>| Not necessarily. In your testing, I would guess you are
>| using XP Pro and do not have simple file sharing enabled.
>| There are scenarios with XP where you are authenticated as
>| guest and the use of the same account/password does not
>| work. Refer to the following knowledge base article:
>| SQL Server clients are authenticated as guests if Simple
>| File Sharing is enabled
>| http://support.microsoft.com/?id=831133
>|
>| -Sue
>|
>| On Mon, 14 Feb 2005 07:08:38 GMT,
>| petery@.online.microsoft.com (Peter Yang [MSFT]) wrote:
>|
>| >Hello Maer,
>| >
>| >I think it is not a limitation in Windows 2000. Based on my test, I
>could
>| >access SQL server on Win2000 server by using Windows authenctication if
>I
>| >use same password for Administrator account on both Win2000 and WinXP
>| >computers. I suggest that you check security policy settings on both
>| >computers to see if they match:
>| >
>| >1. Run gpedit.msc
>| >
>| >2. Check Computer configuration->Windows settings->Security
>Settings->Local
>| >Policies->Security Options and make sure the following settings:
>| >
>| >Digitally sign client communication (always) Not defined
>| >
>| >Digitally sign client communication (when possible) Not defined
>| >
>| >Digitally sign server communication (always) Not defined
>| >
>| >Digitally sign server communication (when possible) Not defined
>| >
>| >LAN Manager Authentication Level Not defined
>| >
>| >Secure channel: Digitally encrypt or sign secure channel data (always)
>Not
>| >defined
>| >
>| >Secure channel: Digitally encrypt secure channel data (when possible)
>Not
>| >defined
>| >
>| >Secure channel: Digitally sign secure channel data (when possible) Not
>| >defined
>| >
>| >Secure channel: Require strong (Windows 2000 or later) session key Not
>| >defined
>| >
>| >3. Check Computer configuration->Windows settings->Security
>Settings->Local
>| >Policies->User Rights assigment, and make sure Deny access this computer
>| >from network is not configured.
>| >
>| >Thanks & Regards,
>| >
>| >Peter Yang
>| >MCSE2000/2003, MCSA, MCDBA
>| >Microsoft Online Partner Support
>| >
>| >When responding to posts, please "Reply to Group" via your newsreader so
>| >that others may learn and benefit from your issue.
>| >
>| > ========================================
=============
>| >
>| >This posting is provided "AS IS" with no warranties, and confers no
>rights.
>| >
>| >
>| >
>| >
>| >--
>| >| From: "Maer" <maer@.auditleverage.com>
>| >| References: <esy#R5JCFHA.3592@.TK2MSFTNGP11.phx.gbl>
>| ><k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.4ax.com>
>| ><#5wLGfLCFHA.1296@.TK2MSFTNGP10.phx.gbl>
>| ><gg8001d3s2nhf3kjd1i61srhmh5264arvc@.4ax.com>
>| >| Subject: Re: Login failed for Server\Guest
>| >| Date: Thu, 10 Feb 2005 19:33:17 -0500
>| >| Lines: 87
>| >| X-Priority: 3
>| >| X-MSMail-Priority: Normal
>| >| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>| >| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>| >| X-RFC2646: Format=Flowed; Original
>| >| Message-ID: <eUzy8D9DFHA.936@.TK2MSFTNGP12.phx.gbl>
>| >| Newsgroups: microsoft.public.sqlserver.connect
>| >| NNTP-Posting-Host: pcp08367474pcs.lndsd201.pa.comcast.net 68.42.29.253
>| >| Path:
>|
>2
>| >phx.gbl
>| >| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:3409
>| >| X-Tomcat-NG: microsoft.public.sqlserver.connect
>| >|
>| >| Thank you, Sue. Your suggestion seems to be the way to go.
>| >|
>| >| I have noticed that when I try to log in using Windows
>Authentication
>| >to
>| >| a Windows 2000 machine from my XP machine, it tries to log me in as
>| >| "Server\Administrator" and, of course, fails. My account is part of
>the
>| >| Administrator's group. However, the other way around (from Win 2000 to
>| >XP)
>| >| works fine.
>| >|
>| >| Is there a limitation in Windows 2000 too?
>| >|
>| >| Thanks again,
>| >| Maer
>| >|
>| >|
>| >|
>| >| "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>| >| news:gg8001d3s2nhf3kjd1i61srhmh5264arvc@.
4ax.com...
>| >| > Hi Maer,
>| >| > You can enable the guest account but that's a security risk
>| >| > - especially if exposed to the outside world. For SQL
>| >| > Server, although Windows Authentication is more secure than
>| >| > SQL Authentication, I'd probably use that option instead of
>| >| > enabling the guest account. Make sure to turn on security
>| >| > audits, limit the number of SQL logins and make sure all SQL
>| >| > logins have strong passwords - mixed case, alpha numeric
>| >| > with special characters, no known words, etc.
>| >| >
>| >| > -Sue
>| >| >
>| >| > On Tue, 1 Feb 2005 18:44:54 -0500, "Maer"
>| >| > <maer@.auditleverage.com> wrote:
>| >| >
>| >| >> Thank you, Sue!
>| >| >>
>| >| >> That clarifies so much! Would I be right in assuming that using
>| >| >> windows
>| >| >>authentication is not an option when logging in remotely to Xp Home
>| >since
>| >| >>it
>| >| >>always uses Guest? Is there a work-around?
>| >| >>
>| >| >> Maer
>| >| >>
>| >| >>
>| >| >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>| >| >> news:k2tvv01h3cqitqs4jefqnnoa9s3obd5rv1@.
4ax.com...
>| >| >>> With XP home, authentication is done using the guest account
>| >| >>> as simple file sharing is always enabled on XP Home. Refer
>| >| >>> to the following for more info:
>| >| >>> SQL Server clients are authenticated as guests if Simple
>| >| >>> File Sharing is enabled
>| >| >>> http://support.microsoft.com/?id=831133
>| >| >>>
>| >| >>> -Sue
>| >| >>>
>| >| >>> On Tue, 1 Feb 2005 15:42:45 -0500, "Maer"
>| >| >>> <maer@.auditleverage.com> wrote:
>| >| >>>
>| >| >>>> Hi - I have two computers, one running Xp Pro and one Xp Home.
>I
>| >| >>>> created
>| >| >>>>a windows user account on both machines with the same password. I
>| >added
>| >| >>>>those accounts to SQL Server on both machines and I want to be
>able to
>| >| >>>>connect to each other using a trusted connection.
>| >| >>>>
>| >| >>>> If I try to remotely connect to the Xp Pro machine from the
>Home
>| >| >>>> machine
>| >| >>>>using windows authentication, everything works fine. But, if I try
>to
>| >| >>>>remotely connect to the Home machine it says that login failed for
>| >| >>>>Server\Guest. My understanding is that it tries to log in as guest
>if
>| >| >>>>the
>| >| >>>>windows account is not found.
>| >| >>>>
>| >| >>>> Why does it work on one computer but not the other? Is it
>because
>| >it
>| >| >>>> is
>| >| >>>>Home edition? Is there something else I need to do?
>| >| >>>>
>| >| >>>> BTW, standard authentication works fine on both machines and
>the
>| >| >>>> Guest
>| >| >>>>account is turned off.
>| >| >>>>
>| >| >>>> Thanks,
>| >| >>>> Maer
>| >| >>>>
>| >| >>>
>| >| >>
>| >| >
>| >|
>| >|
>| >|
>|
>|sql