Hunterconsultant635

Windows troubleshooting detected ' network adapter or access point issues.' The wireless driver properties shows that device status ' works properly ' and ' up to date'. Resetting the router - the problem still exist. Disable/enable DELL wireless driver - the problem still exist. Update the wireless driver - the problem still exist. The service provider (Alice DSL, www.alice-dsl.de (German)) had sent her a 'broadband modem' called 'Turbolink IAD' from Sphairon Access Systems. An installation CD was provided but it will only install on a German version of Windows - this version is English. Sphairon Access Systems GmbH: 0110: Turbolink UB801R WLAN Adapter: Vendor Device USB: 114b: Sphairon Access Systems GmbH: 0150: Turbolink UB801RE Wireless 802.11g 54Mbps Network Adapter RTL8187 Vendor Device.

• Sphairon Access Network & Wireless Cards Drivers

444 drivers total Last updated: May 2nd 2020, 05:09 GMT RSS Feed. Latest downloads from Qualcomm in Network Card. Sort by: last update. ASUS VivoBook 17 X705UFR Qualcomm WLAN Driver 12.0.0.725 for Windows 10 64-bit 141 downloads. Network Card Qualcomm. Compaq CQ10-400 Mini PC Series (Win 7) Network card driver. Download the Network card driver for your Compaq CQ10-400 Mini PC Series. License: Free OS: Windows 7.

This article provides solutions for the issue that DNS CNAME alias can't access SMB file servers.

Original product version: Windows 10 - all editions, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows 7 Service Pack 1
Original KB number: 3181029

Symptoms

Configuration

• You're running an SMB file server, such as Windows Server. The server has files and resources that are configured by using their NetBIOS name, the DNS fully qualified domain name (FQDN), and their alias (CNAME).
• You have a client that's running Windows 7, Windows Server 2008 R2, or a later version of Windows.

Scenarios

• When an application or user uses the actual storage name (the NetBIOS name or the FQDN) for files or other resources on the server that's using SMB, access is successful.

• When an application or user uses the CNAME alias for files or other resources on the server that's using SMB, and you try to connect to a share on the file server with its DNS CNAME alias. For example, you try to connect to a share on the file server by using its DNS CNAME alias:

  In this case, you experience the following behaviors:

  • Access from a Windows Server 2008 R2 or Windows 7 client is successful.

  • Access from a Windows Server 2012 R2, Windows 8.1, or a later version of Windows client is unsuccessful. In this case, you receive an error message that resembles the following one:

    Open Folder

    uncpath is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

    Logon Failure: The target account name is incorrect.

Cause

• If you use Network Monitor, Wire Shark, or Microsoft Message Analyzer to examine the network trace when the SMB Session Setup is successful, the session goes to the TREE Connect.

  However, if you examine the network trace when the SMB Session Setup is unsuccessful, the session fails with a Kerberos KRB_AP_ERR_MODIFIED error. Here's an example of an unsuccessful SMB Session Setup request in a network trace:

  MessageNumber DiagnosisTypes Timestamp Source Destination Module Summary
  112 None DateTime Client Server SMB2 Negotiate, Status: Success, 2780879Guid: {12f74af4-be82-11e5-b5c2-005056890096}, DialectRevision: SMB 2.
  112 None DateTime Client Server SMB2 NegotiateRequest, Dialects: [SMB 2.0.2, SMB 2.1], Capabilities: , 2780879Guid: {12f74af4-be82-11e5-b5c2-
  115 None DateTime Server Client SMB2 NegotiateResponse, Status: Success, DialectRevision: SMB 2.1, Capabilities: SMB2GlobalCapDfs|SMB2GlobalC
  116 None DateTime Client Server SMB2 SessionSetup, Status: STATUS_MORE_PROCESSING_REQUIRED, Kerberos, Flags: 0
  116 None DateTime Client Server SMB2 SessionSetupRequest, Kerberos, Flags: Unknown(0), PreviousSessionId: 0x0000000000000000
  122 None DateTime Server Client SMB2 SessionSetupResponse, Status: STATUS_MORE_PROCESSING_REQUIRED, Kerberos, SessionId: 0x000004030800006D
  135 None DateTime Client Server SMB2 SessionSetup, Status: STATUS_MORE_PROCESSING_REQUIRED, Kerberos, Flags: 0
  135 None DateTime Client Server SMB2 SessionSetupRequest, Kerberos, Flags: Unknown(0), PreviousSessionId: 0x0000000000000000
  143 None DateTime Server Client SMB2 SessionSetupResponse, Status: STATUS_MORE_PROCESSING_REQUIRED, Kerberos, SessionId: 0x000004030800006D

  In an unsuccessful SMB Session Setup request, the client forwards an incorrect CNAME SPN. The SPN may be incorrect because it's registered for an old server. However in a successful SMB Session Setup request such as in the Windows Server 2008 R2 client case, the client forwards the SPN for the actual server name.

• If the file server name was resolved through DNS, the SMB client appends the DNS suffix to the user-supplied name. That is, the first component of the SPN will always be the user supplied name as in the following example:

  Note

  This try would fail on older SMB implementations (Like AIX Samba 3.5.8), that cannot be configured for Kerberos authentication and does not listen to SMB direct host port 445, but only on NetBIOS port 139.

• If the file server name was resolved through some other mechanism such as

  • NetBIOS
  • Link-Local Multicast Name Resolution (LLMNR)
  • Peer Name Resolution Protocol (PNRP) processes

  the SMB client uses the user supplied name such as the following one:

Resolution

To resolve this issue on a file server that is running the SMB version 1 protocol, add the DisableStrictNameChecking value to the registry:

Registry location: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters
DWORD name: DisableStrictNameChecking
DWORD value: 1

Important

Do not use DNS CNAMEs in the future for file servers. If you want to still give alternate names to servers, you can do so with the following command:
NETDOM COMPUTERNAME/ADD

This command automatically registers SPNs for the alternate names.

We don't recommend that you resolve this issue for a file server that isn't Windows-based by typing the following commands in an elevated Command Prompt window on a Windows-based computer. You would have to be logged on with Domain Administrator credentials. Then press Enter at the command prompt to register the SPN for the CNAME of the non-Windows-based File Server storage device:

Note

• If you use Windows 2012 Clustering, install the hotfix for down-level clients in which Windows XP or Windows Server 2003 computers cannot connect: Can't access a resource that is hosted on a Windows Server 2012-based failover cluster.
• If you create a CNAME for the clustered name the clients are connecting to, you have to make sure that you set the properties on that Clustered name so that it responds to the CNAMEs:How to configure an alias for a clustered SMB share with Windows Server 2012.

Network trace

To collect a network trace, follow these steps:

1. Open an elevated Command Prompt window, type the following command, and then press Enter:

2. Delete any existing File Server network connections by running the following command:

3. Initialize all name caching by deleting the existing cache:

   1. To delete the DNS cache, type the following command, and then press Enter:

   2. To delete the NetBIOS cache, type the following command, and then press Enter:

   3. To delete the Kerberos cache, type the following command, and then press Enter:

   4. To delete the ARP cache, type the following command, and then press Enter:

4. Try to connect to the network share by typing the following command and then pressing Enter:

5. To stop the network trace in an unsuccessful scenario, type the following command, and then press Enter:

Collect registry settings

To collect registry settings on the file server, select Start, select Run, type the command in the Open box, and then select OK. Repeat this step for the following commands:

Note

The registry setting files (.HIV) are saved to the TEMP folder on the file server.

Check registry settings

Check the settings of the following registry values on the file server:

Apply hotfixes (server and client)

For Windows 7 and Windows Server 2008 R2, apply the following Windows 7 Enterprise hotfix rollup:

Additionally, apply the following hotfixes:

References

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Sphairon Access Network & Wireless Cards Drivers