SQL Server uses Windows authentication to connect to another SQL server in the LAN

SQLSERVER uses Windows authentication on the LAN to connect to another SQL server in the LAN (not a domain environment) previously, even MSDN said that connecting to another SQL server in the LAN must be a domain environment if you want to use Windows authentication. But today I found that using Windows authentication, you can still connect to the LAN without using the domain environment. another SQL

SQLSERVER uses Windows authentication on the LAN to connect to another SQL server in the LAN (not a domain environment) previously, even MSDN said that connecting to another SQL server in the LAN must be a domain environment if you want to use Windows authentication. But today I found that using Windows authentication, you can still connect to the LAN without using the domain environment. another SQL

SQLSERVER uses Windows authentication on the LAN to connect to another SQL server in the LAN (not a domain environment)

Previously, even MSDN said that connecting to another SQL server in the LAN must be"Domain environment"

However, today I found that using Windows authentication can connect to another SQL server in the LAN without a domain environment.

Description on MSDN:

Address:Http://msdn.microsoft.com/zh-cn/library/ms144284.aspx

Http://msdn.microsoft.com/zh-cn/library/ms143705 (v = SQL .90). aspx

"

• SQL Server is allowed to support environments with hybrid operating systems. In such environments, not all users are verified by the Windows domain.

"

It was actually found after someone tried it in a post on the msdn forum.

Let me take the following steps:

My test environment:

Machine A: Windows 7 SQL2005 computer name: joe

Machine B: Windows8 SQL2008R2 computer name: joehomepc

Condition: the Windows Account Name of machine A is the same as the Windows Account Name of machine B, and the password is the same (no password can be used)

Step 1:

For example, my Windows account for machine A is Administrator.

My Windows account for machine B is also Administrator.

The passwords of both accounts are empty.

Machine A ip Address: 192.168.1.100
Machine B ip: 192.168.1.102

Step 2:

Open SSMS on machine A, enter the IP address of machine B, and use Windows authentication.

Connect directly to SQL2008R2

Step 3:

Query data on SQL2008R2. If you open the table in object Resource Manager->, an error is returned.

However, no error is reported when you use the query editor.

It is estimated that SQL2008 does not support the "Open Table" command of SQL2005.

Summary:

Is it Microsoft's vulnerability? Or do we not know this feature?