Showing posts with label running. Show all posts
Showing posts with label running. Show all posts

Friday, March 30, 2012

Login failed for user NT AUTHORITY\NETWORK SERVICE

Hi,

We have just purchased a new server running Windows Server 2003 Standard and I am trying to run an ASP.NET 1.1 application but I keep getting the following error message when the application tries to connect to the SQL Server:

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

After reading numerous posts and responses in the forums I have still been unable to overcome this problem.

I have added the IIS_WPG group as a user in the SQL Server Enterprise Manager which NT AUTHORITY\NETWORK SERVICE is a member of but it still doesn't work.

Some of the other suggestions in the forum included not using a trusted connection and changing the Application Pool Identity in IIS from Network Service to Local System. However both of these options have security implications.

I am using
Windows Server 2003 Standard
- The only roles installed File Server, Application Server (IIS & ASP.NET) and DNS Server
SQL Server 2000
ASP.NET 1.1

Any help would be appreciated,

Thanks,

Peter.Hi,

Your are not alone....

I have similar problem, at least same login fail, problem,
(Login failed for user 'NT AUTHORITY\NETWORK SERVICE').

I´ll guess my second problem below will disappear if I solve this above?
Any help would be appreciated.

I have created an SQL instance DotNetNuke with MSDE(desktop engine)
1) How shall I do to create the tables ?
2) How shall I do to create a userid + password ? ( OSQL )
(work around, for problem one??, maybe)

I do not have Enterprise manager.

Thanks
Johan from Svedala..|||I have solved the problem,

When I installed SQL Server I selected to start and run the SQL Server using a Domain Administrator Account.

Changing this to the System Account solved the problem.

This is achieved by doing the following:

1. Expand a server group.
2. Right-click the server, and then clickProperties.
3. On theSecurity tab, underStartup service account, clickSystem account.

Peter.

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

Hello all -

I'm trying to connect to a Sql Server 2005 database from my local development machine, which is running IIS 5.1 (Windows XP Pro). The web application is not using impersonation and has anonymous access enabled. In my system's machine.config file, I've set the processModel section to look like:

<processModel userName="System" password="AutoGenerate" />

This has been working fine for us connecting to SQL Server 2000 databases (running on Windows 2003). When we connect, I access Sql 2000 databases under the context of "OurDomain\MyMachineName$". However, we've recently installed Sql Server 2005 on a new Windows 2003 server & when I connect to that server, I receive the error:

System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

when trying to call the SqlConnection.Open() method. Our connection string is very basic:

Data Source=sql-dev2; Initial Catalog=TestDatabase; Integrated Security=True; Application Name=PrototypeWebservice;

In the Sql Server logins, we've granted the computer account "OurDomain\MyMachineName$" db_owner access to every database (in both Sql Server 2000 & 2005).

I am able to connect to the Sql Server 2005 databases if I change my section in machine.config to <processModel userName="OurDomina\myPersonalAccount" password="myPersonalPwd"/>, or if I move the application to an IIS6 server & set the application pool identity to NETWORK SERVICE, but we'd like to continue accessing our Sql Server 2005 databases (from our development machines running IIS5.1) as we currently access our Sql Server 2000 databases; under the context of "OurDomain\MyMachineName$".

Would anyone have any ideas why this would be happening or how to resolve? Thanks in advance.

Please check this blog: http://blogs.msdn.com/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx

.....

[1] "Login Failed for user 'NT Authority\ANONYMOUS' LOGON"

In this scenario, client make tcp connection, and it is most likely running under LocalSystem account, and there is no SPN registered for SQL instance, hence, NTLM is used, however, LocalSystem account inherits from System Context instead of a true user-based context, thus, failed as 'ANONYMOUS LOGON'. See http://support.microsoft.com/kb/132679.

The workaround here is

a. ask your domain administrator to manually register SPN if your SQL Server running under a domain user account.

b. use NP connection.

c. change your sql server to run under either localsystem account or networkservice account.

|||

That was the ticket!!! Thank you very much.

For future reference, the problem we ran into was that we had multiple active directory accounts registered with the same SPN. One entry was registered under the computer account sql server was running on & the other was the user account the sql server service was running under. We detected this by looking into the System event log on the domains PDC (the entry was EventID 11, Source KDC. Exact steps we followed were those suggested by other users on the thread: http://www.eventid.net/display.asp?eventid=11&eventno=569&source=KDC&phase=1). After removing the entry for the computer account, kerberos authentication succeeded.

Thanks again!

|||Thanks for the feedback.

Wednesday, March 28, 2012

login failed for user error

This summary is not available. Please click here to view the post.

login failed for user error

This summary is not available. Please click here to view the post.

Login failed for user domain\domcontroller$ - 18456

I am running several instances of SQL Server 2005 sp2 on a W2k3 sp2 box (member server).

This morning, I installed reporting services to one of my instances and shortly after noticed I was getting the following two messages in my SQL Server log file:-

08/08/2007 11:05:03,Logon,Unknown,Login failed for user 'DOMAIN\DOMCONTROLLER$'. [CLIENT: xxx.xxx.xxx.xxx]
08/08/2007 11:05:03,Logon,Unknown,Error: 18456, Severity: 14, State: 16.

The above entries were each repeated 6 times every 15 minutes but with State 11. I created a logon for the above, and now get the above messages (state 16) repeated 3 times every 15 minutes!

Any ideas why?

Regards

Ian

It seems like a service in DOMCONTROLLER machine is trying to connect to SQL Server, it must be running under network service or local system account.

I recommend reading the following post, hopefully it will help you find the solution:

http://forums.microsoft.com/msdn/showpost.aspx?postid=66265&siteid=1

-Raul Garcia

SDE/T

SQL Server Engine

Monday, March 26, 2012

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server

We have a problem on a SQL Server 2000 with SP3a and
latest security patch running on Windows 2003.
We have several other SQL-servers aswell but this one
seems to have problems with Windows Authentication. It
worked properly first but then when we changed to Windows
authentication and then back to SQL Server and Windows
authentication it stopped working properly. I have
successfully got this problem in my lab aswell (see
below).
The problem: We're running the SQL Service using a
domainaccount (sql1) which is in the local Administrators
group on the server. If I login using this account I can
open Ent Manager using Windows Authentication. I login to
Windows using another domainaccount (user1) that is also
a member of Administrators on the server, when I open up
Ent Manager I get "Login failed for user '(null)'.
Reason: Not associated with a trusted SQL Server
connection.". This is also logged in the Event Log. If I
use SQL Authentication it works. Same goes when I try to
connect remotly to a database with an ODBC-connection.
If I check the permissions I can see that
BUILTIN\Administrators have the System Administrators
role. I also try to att DOMAIN\user1 manually and give
permission. Still doesn't work. The SQL Server is
configured for both SQL Server and Windows Authentication.
I have restarted the server to make sure settings are
changed. I've also looked through MS KB's and found a
registrykey:
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\Lo ginMode
and it's set to 2.
In my lab I installed SQL2000. I could use Ent Manager
with both sql1 and user1. Then I switched to Windows mode
and then back to SQL Server and Windows and restarted the
server. Now I have the problem mentioned above and I can
only use sql1 to open Ent Manager.
I've looked through many posts in this forum but none
have supplied with me with any solution.
This is usually a problem with Kerberos and authentication. You can look at
this article for help:
http://support.microsoft.com/default.aspx?scid=kb;[LN];811889
The error you are getting is different but they are usually caused by the
same thing or similar things.
The article mentions a setspn utility. You can downlod it from here:
http://www.microsoft.com/windows2000...sting/setspn-o
.asp
Rand
This posting is provided "as is" with no warranties and confers no rights.

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server

We have a problem on a SQL Server 2000 with SP3a and
latest security patch running on Windows 2003.
We have several other SQL-servers aswell but this one
seems to have problems with Windows Authentication. It
worked properly first but then when we changed to Windows
authentication and then back to SQL Server and Windows
authentication it stopped working properly. I have
successfully got this problem in my lab aswell (see
below).
The problem: We're running the SQL Service using a
domainaccount (sql1) which is in the local Administrators
group on the server. If I login using this account I can
open Ent Manager using Windows Authentication. I login to
Windows using another domainaccount (user1) that is also
a member of Administrators on the server, when I open up
Ent Manager I get "Login failed for user '(null)'.
Reason: Not associated with a trusted SQL Server
connection.". This is also logged in the Event Log. If I
use SQL Authentication it works. Same goes when I try to
connect remotly to a database with an ODBC-connection.
If I check the permissions I can see that
BUILTIN\Administrators have the System Administrators
role. I also try to att DOMAIN\user1 manually and give
permission. Still doesn't work. The SQL Server is
configured for both SQL Server and Windows Authentication.
I have restarted the server to make sure settings are
changed. I've also looked through MS KB's and found a
registrykey:
HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer\LoginMode
and it's set to 2.
In my lab I installed SQL2000. I could use Ent Manager
with both sql1 and user1. Then I switched to Windows mode
and then back to SQL Server and Windows and restarted the
server. Now I have the problem mentioned above and I can
only use sql1 to open Ent Manager.
I've looked through many posts in this forum but none
have supplied with me with any solution.This is usually a problem with Kerberos and authentication. You can look at
this article for help:
http://support.microsoft.com/defaul...scid=kb;[LN];811889
The error you are getting is different but they are usually caused by the
same thing or similar things.
The article mentions a setspn utility. You can downlod it from here:
http://www.microsoft.com/windows200...isting/setspn-o
.asp
Rand
This posting is provided "as is" with no warranties and confers no rights.

Login failed for user '(null)'.

I'm running SQL 2000, SP3 on a W2K server and am having an issue where
users who are trying to connect to SQL Server via Windows Authenication
are getting a 'Login failed for user '(null)'. error. They have plenty
of permissions on SQL Server so that's not the issue. I've done some
testing and the only way I can get them to connect to SQL Server is if I
add them to the local admin group on the server. Has anyone else ever
seen this?
*** Sent via Developersdex http://www.codecomments.com ***
Hi
Give the domain user permission to log into SQL Server.
Look at "user accounts, described" in BOL Index.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this?
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||They do have permissions through SQL Server. The problem is that their
domain logins still fail unless I add their login to the local admin
group on the server.
*** Sent via Developersdex http://www.codecomments.com ***
|||No problems with these users logging into the Domain and accessing Domain
resources? Make sure they're not logging into their local machines as
opposed to the Domain (sometimes users forget to change the little drop-down
box on the login screen). Are you using an app that you created or is it an
off-the-shelf prog? If it is a custom app, what's the connection string
look like?
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:eNXw5jVOFHA.3704@.TK2MSFTNGP12.phx.gbl...
> They do have permissions through SQL Server. The problem is that their
> domain logins still fail unless I add their login to the local admin
> group on the server.
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||They're definitely logged into the domain - and just to be sure it
wasn't just an end-user error I had 2 other DBAs on my team try to
connect to the database through query analyzer and they got the same
error message.
The application team has tried connecting through their application and
through query analyzer but cannot connect unless I add them to the local
admin group. We can use that as a temporary work around but I'd like to
figure out what's going on.
Any suggestions?
*** Sent via Developersdex http://www.codecomments.com ***
|||Hi,
What account is SQL Server running under?
I've had issues with authentication if it's running under the local system account.
I don't know how you've set things up, but here is what worked for me.
I create a local group and add the domain users to this group.
I create a logon for the local group and give it the appropriate permissions.
HTH
Dan Artuso, MVP
"Rachael Faber" <rfaber@.alldata.net> wrote in message news:uV%23r8ieOFHA.2356@.TK2MSFTNGP14.phx.gbl...
> They're definitely logged into the domain - and just to be sure it
> wasn't just an end-user error I had 2 other DBAs on my team try to
> connect to the database through query analyzer and they got the same
> error message.
> The application team has tried connecting through their application and
> through query analyzer but cannot connect unless I add them to the local
> admin group. We can use that as a temporary work around but I'd like to
> figure out what's going on.
> Any suggestions?
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||It's running under a domain account.
*** Sent via Developersdex http://www.codecomments.com ***
|||Hi Rachael,
Try to rejoin to domain some of the clients.
Regards,
Daniel
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this?
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||Hi,
Okay, the only other thing I've seen is I've had to grant access explicitly to the domain group
in the Local Security Policy
In User Rights Assignment:
Allow access to this computer from the network
add the domain group that your users area member of. By default the local Admins group
is a part of this so perhaps that is why it works when you make your users part of that group.
HTH
Dan Artuso, MVP
"Rachael Faber" <rfaber@.alldata.net> wrote in message news:%23ZoVHurOFHA.1732@.TK2MSFTNGP14.phx.gbl...
> It's running under a domain account.
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||That's exactly what the problem was - thank you!!
*** Sent via Developersdex http://www.codecomments.com ***

Login failed for user '(null)'.

I'm running SQL 2000, SP3 on a W2K server and am having an issue where
users who are trying to connect to SQL Server via Windows Authenication
are getting a 'Login failed for user '(null)'. error. They have plenty
of permissions on SQL Server so that's not the issue. I've done some
testing and the only way I can get them to connect to SQL Server is if I
add them to the local admin group on the server. Has anyone else ever
seen this'
*** Sent via Developersdex http://www.developersdex.com ***Hi
Give the domain user permission to log into SQL Server.
Look at "user accounts, described" in BOL Index.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this'
>
> *** Sent via Developersdex http://www.developersdex.com ***|||Hi Rachael,
Try to rejoin to domain some of the clients.
Regards,
Daniel
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this'
>
> *** Sent via Developersdex http://www.developersdex.com ***

Login failed for user '(null)'.

I'm running SQL 2000, SP3 on a W2K server and am having an issue where
users who are trying to connect to SQL Server via Windows Authenication
are getting a 'Login failed for user '(null)'. error. They have plenty
of permissions on SQL Server so that's not the issue. I've done some
testing and the only way I can get them to connect to SQL Server is if I
add them to the local admin group on the server. Has anyone else ever
seen this'
*** Sent via Developersdex http://www.codecomments.com ***Hi
Give the domain user permission to log into SQL Server.
Look at "user accounts, described" in BOL Index.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this'
>
> *** Sent via Developersdex http://www.codecomments.com ***|||They do have permissions through SQL Server. The problem is that their
domain logins still fail unless I add their login to the local admin
group on the server.
*** Sent via Developersdex http://www.codecomments.com ***|||No problems with these users logging into the Domain and accessing Domain
resources? Make sure they're not logging into their local machines as
opposed to the Domain (sometimes users forget to change the little drop-down
box on the login screen). Are you using an app that you created or is it an
off-the-shelf prog? If it is a custom app, what's the connection string
look like?
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:eNXw5jVOFHA.3704@.TK2MSFTNGP12.phx.gbl...
> They do have permissions through SQL Server. The problem is that their
> domain logins still fail unless I add their login to the local admin
> group on the server.
>
> *** Sent via Developersdex http://www.codecomments.com ***|||They're definitely logged into the domain - and just to be sure it
wasn't just an end-user error I had 2 other DBAs on my team try to
connect to the database through query analyzer and they got the same
error message.
The application team has tried connecting through their application and
through query analyzer but cannot connect unless I add them to the local
admin group. We can use that as a temporary work around but I'd like to
figure out what's going on.
Any suggestions'
*** Sent via Developersdex http://www.codecomments.com ***|||Hi,
What account is SQL Server running under?
I've had issues with authentication if it's running under the local system a
ccount.
I don't know how you've set things up, but here is what worked for me.
I create a local group and add the domain users to this group.
I create a logon for the local group and give it the appropriate permissions
.
HTH
--
Dan Artuso, MVP
"Rachael Faber" <rfaber@.alldata.net> wrote in message news:uV%23r8ieOFHA.2356@.TK2MSFTNGP14.p
hx.gbl...
> They're definitely logged into the domain - and just to be sure it
> wasn't just an end-user error I had 2 other DBAs on my team try to
> connect to the database through query analyzer and they got the same
> error message.
> The application team has tried connecting through their application and
> through query analyzer but cannot connect unless I add them to the local
> admin group. We can use that as a temporary work around but I'd like to
> figure out what's going on.
> Any suggestions'
>
> *** Sent via Developersdex http://www.codecomments.com ***|||It's running under a domain account.
*** Sent via Developersdex http://www.codecomments.com ***|||Hi Rachael,
Try to rejoin to domain some of the clients.
Regards,
Daniel
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this'
>
> *** Sent via Developersdex http://www.codecomments.com ***|||Hi,
Okay, the only other thing I've seen is I've had to grant access explicitly
to the domain group
in the Local Security Policy
In User Rights Assignment:
Allow access to this computer from the network
add the domain group that your users area member of. By default the local Ad
mins group
is a part of this so perhaps that is why it works when you make your users p
art of that group.
HTH
--
Dan Artuso, MVP
"Rachael Faber" <rfaber@.alldata.net> wrote in message news:%23ZoVHurOFHA.1732@.TK2MSFTNGP14.p
hx.gbl...
> It's running under a domain account.
>
> *** Sent via Developersdex http://www.codecomments.com ***|||That's exactly what the problem was - thank you!!
*** Sent via Developersdex http://www.codecomments.com ***

Wednesday, March 21, 2012

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

Hello all -

I'm trying to connect to a Sql Server 2005 database from my local development machine, which is running IIS 5.1 (Windows XP Pro). The web application is not using impersonation and has anonymous access enabled. In my system's machine.config file, I've set the processModel section to look like:

<processModel userName="System" password="AutoGenerate" />

This has been working fine for us connecting to SQL Server 2000 databases (running on Windows 2003). When we connect, I access Sql 2000 databases under the context of "OurDomain\MyMachineName$". However, we've recently installed Sql Server 2005 on a new Windows 2003 server & when I connect to that server, I receive the error:

System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

when trying to call the SqlConnection.Open() method. Our connection string is very basic:

Data Source=sql-dev2; Initial Catalog=TestDatabase; Integrated Security=True; Application Name=PrototypeWebservice;

In the Sql Server logins, we've granted the computer account "OurDomain\MyMachineName$" db_owner access to every database (in both Sql Server 2000 & 2005).

I am able to connect to the Sql Server 2005 databases if I change my section in machine.config to <processModel userName="OurDomina\myPersonalAccount" password="myPersonalPwd"/>, or if I move the application to an IIS6 server & set the application pool identity to NETWORK SERVICE, but we'd like to continue accessing our Sql Server 2005 databases (from our development machines running IIS5.1) as we currently access our Sql Server 2000 databases; under the context of "OurDomain\MyMachineName$".

Would anyone have any ideas why this would be happening or how to resolve? Thanks in advance.

Please check this blog: http://blogs.msdn.com/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx

.....

[1] "Login Failed for user 'NT Authority\ANONYMOUS' LOGON"

In this scenario, client make tcp connection, and it is most likely running under LocalSystem account, and there is no SPN registered for SQL instance, hence, NTLM is used, however, LocalSystem account inherits from System Context instead of a true user-based context, thus, failed as 'ANONYMOUS LOGON'. See http://support.microsoft.com/kb/132679.

The workaround here is

a. ask your domain administrator to manually register SPN if your SQL Server running under a domain user account.

b. use NP connection.

c. change your sql server to run under either localsystem account or networkservice account.

|||

That was the ticket!!! Thank you very much.

For future reference, the problem we ran into was that we had multiple active directory accounts registered with the same SPN. One entry was registered under the computer account sql server was running on & the other was the user account the sql server service was running under. We detected this by looking into the System event log on the domains PDC (the entry was EventID 11, Source KDC. Exact steps we followed were those suggested by other users on the thread: http://www.eventid.net/display.asp?eventid=11&eventno=569&source=KDC&phase=1). After removing the entry for the computer account, kerberos authentication succeeded.

Thanks again!

|||Thanks for the feedback.

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