Nora
Blake

Configuring SMB network file shares in ChromeOS managed guest sessions

Nora Blake

Nov 19, 2026

10 min read

Configuring SMB network file shares in ChromeOS managed guest sessions

Key Takeaways

  • ChromeOS managed guest sessions provide access to network file shares through configurable network file share settings.
  • Verify server requirements before choosing Standard authentication or Kerberos SSO; enable NTLM when required.
  • NetBIOS discovery helps locate network shares, while preconfigured file share mode controls automatic mounting or user selection.
  • Before deployment, configure the appropriate managed guest session policy, target organizational units, and validate network share access.

What Does SMB Access Mean in a ChromeOS Managed Guest Session?

ChromeOS guest session SMB access lets temporary users retrieve files from shared network locations without individual Google Account sign-ins. SMB (Server Message Block) is a network file-sharing protocol that lets devices access files hosted on network servers.

For example, libraries, schools, and businesses can provide shared computers for temporary users. Administrators configure session settings and apply organizational policies to control the browsing environment.

Managed guest sessions provide session-specific settings through organizational units. However, device-level policies can also apply to ordinary guest users on managed ChromeOS devices.

Administrators must consider four areas when enabling network file sharing:

  • Share availability
  • Authentication
  • Network discovery
  • Mounting behavior

Enabling network file sharing does not grant unrestricted access to every network resource. Therefore, administrators must configure the relevant settings and verify access before deployment.

What Must Be in Place Before Enabling Managed Guest Sessions?

Managed guest sessions require enrolled ChromeOS devices and an eligible ChromeOS upgrade. Administrators should also verify organizational unit placement before configuring network file sharing.

Check these prerequisites before deployment:

  • Device enrollment: Enroll the ChromeOS devices intended for managed guest sessions.
  • Organizational unit: Place each device in an appropriate organizational unit. Google applies managed guest session settings through these units.
  • ChromeOS upgrade: Google requires ChromeOS Enterprise Upgrade or ChromeOS Education Upgrade for managed guest sessions. Organizations can purchase these separately or receive them bundled with devices.
  • Upgrade compatibility: Kiosk & Signage Upgrade does not support managed guest sessions.

These upgrade requirements apply to managed guest sessions, not ordinary Guest mode. However, Google does not apply user-level organizational policies during Guest mode sessions. Device-level policies can still apply to managed ChromeOS devices.

Which Network Share Controls Should You Configure First?

ChromeOS network file sharing relies on one primary setting and several supporting options. Administrators can control share availability, NTLM authentication, file URLs, NetBIOS discovery, and preconfigured mounting behavior.

How Do You Enable Network File Sharing?

The Network file share setting allows users to access network file shares on ChromeOS devices. Enable it before configuring the dependent options.

The following table summarizes the available controls and their documented ChromeOS version requirements.

Setting  What it controls  Supported ChromeOS version 
Network file share  Allows access to network file shares.  ChromeOS 70+ 
NTLM authentication  Enables NTLM authentication for SMB mounts.  ChromeOS 71+ 
Preconfigured file share mode  Controls automatic mounting or discovery dropdown placement.  ChromeOS 71+ 
File URL  Specifies the network file share URL.  ChromeOS 110+ 
NetBIOS discovery  Enables NetBIOS name queries for share discovery.  ChromeOS 70+

Understand the Configuration Dependencies 

NTLM authentication, Preconfigured file share mode, File URL, and NetBIOS discovery depend on Network file share being enabled first.

However, administrators do not need every option for every deployment. Choose settings according to the file server’s authentication requirements and the intended user experience.

For example, an organization might automatically mount a share using NTLM, while another might let users select a preconfigured share through discovery.

These version requirements reflect Hexnode’s managed guest session content settings documentation, reviewed as of November 2026. For additional policy details, consult Google’s ChromeOS network file share policies.

Which Authentication Options Are Available for ChromeOS Guest Sessions?

ChromeOS SMB shares support Standard authentication using username and password credentials or Kerberos-based SSO for Active Directory users. Separately, administrators can configure the NTLM policy to control NTLM authentication for SMB mounts.

How Does NTLM Authentication Work for SMB Mounts?

NTLM (NT LAN Manager) is an authentication protocol that ChromeOS can use for SMB mounts. Enable Network file share first, then configure NTLM if the file server requires it.

Can Kerberos Provide Single Sign-On to Network File Shares?

Kerberos uses authentication tickets to provide single sign-on (SSO) to compatible internal resources, including network file shares. Hexnode provides separate Kerberos settings under Managed Guest Session > Basic.

These settings include:

  • Kerberos: Enables Kerberos ticket-based SSO for supported internal resources.
  • Autocomplete Kerberos domain: Prefills the domain in the Kerberos authentication dialog.
  • Use custom pre-filled configs for Kerberos: Enables administrators to apply a custom Kerberos configuration.
  • Custom configuration: Accepts the Kerberos configuration for managed guest sessions.

Google specifies an Active Directory environment for its documented ChromeOS Kerberos SSO configuration. Its documentation also states that kiosks are currently unsupported.

For setup requirements, consult Google’s Kerberos authentication guide for ChromeOS.

Importantly, the documentation does not establish authentication precedence or fallback behavior between NTLM and Kerberos. Treat them as separate configuration considerations.

What Should Administrators Verify Before Choosing Authentication?

Before configuring authentication, check:

  • Does the file server support the selected authentication method?
  • Is Active Directory available when users require Kerberos SSO?
  • Can a test user authenticate and access the intended network share?

For configuration details, consult Hexnode’s managed guest session settings guide.

How Do NetBIOS Discovery and Preconfigured Mounting Work?

Preconfigured file share mode controls automatic mounting or user selection. NetBIOS discovery helps locate network shares.

What Is NetBIOS Discovery?

NetBIOS discovery enables ChromeOS to use the NetBIOS name query protocol when discovering network file shares.

However, discovery and mounting serve different purposes. Discovery locates network shares, while mounting makes a selected share available for access.

When Should You Automatically Mount a Share?

The Mount the shared URL option automatically mounts the specified URL as a file share. This approach suits shared computers where users regularly access the same resource.

For example, a library computer might provide consistent access to a common document repository. However, automatic mounting does not eliminate authentication requirements.

When Should You Add a Share to the Discovery Dropdown?

The Add to the shared discovery dropdown option displays the configured URL in the file share discovery list. Users can then select and mount the share manually.

This approach suits shared workstations where visitors should choose whether to access a particular network resource.

Configuration  Device behavior  Suitable consideration 
Mount the shared URL  Automatically mounts the specified URL.  Resources requiring automatic availability. 
Add to the shared discovery dropdown  Lets users select and mount the configured URL.  Resources requiring user selection. 
NetBIOS discovery  Enables NetBIOS-based share discovery.  Environments requiring this discovery mechanism. 

Choose discovery and mounting behavior according to the network environment and intended user access.

How Should You Set Up and Validate SMB Access?

Setting up ChromeOS guest session SMB access involves identifying the network share, verifying authentication requirements, and choosing suitable mounting behavior. Administrators must also apply the configuration and test access before deployment.

What Should You Confirm Before Configuration?

Check these prerequisites before configuring SMB access:

  • Network share URL: Identify the exact address, such as smb://server/share or \\shared\resource.
  • Session environment: Confirm that the target devices use managed guest sessions.
  • Authentication: Verify which authentication protocols the file server supports.
  • Mounting preference: Decide between automatic mounting and manual selection.
  • Discovery requirements: Determine whether the network requires NetBIOS discovery.

Google documents these SMB URL formats in its ChromeOS network file share policies.

How Should You Configure the Network Share?

Follow these steps:

  • Enable Network file share.
  • Configure NTLM authentication if the SMB environment requires it.
  • Enter the intended File URL.
  • Select automatic mounting or discovery dropdown placement.
  • Enable NetBIOS discovery when the network requires it.
  • Configure Kerberos separately when the environment requires supported Kerberos-based SSO.

Not every deployment needs every setting. Select options according to the file server’s capabilities and the intended user experience.

What Should You Test Before Deployment?

Use this validation checklist:

  • Does the intended share appear in the expected location?
  • Does automatic mounting or manual selection work as configured?
  • Can users authenticate successfully?
  • Can users access the intended files and directories?
  • Does the configuration work after starting a new managed guest session?
  • Do unrelated network shares remain inaccessible where required?

Test the chosen configuration against actual access requirements before deployment.

What Should You Check When an SMB Share Fails to Mount?

SMB mounting failures can result from incorrect URLs, authentication problems, unavailable servers, or incompatible file servers.

Check these common issues:

  • Invalid share URL: Verify the server address and share name. ChromeOS supports smb://server/share and \\server\share formats.
  • Unsupported SMB version: Confirm that the file server supports SMBv2 or later. ChromeOS displays an error when the server does not meet this requirement.
  • Authentication failure: Recheck the supplied credentials and confirm that the account has access to the intended share.
  • SSO hostname requirement: When using Kerberos SSO, specify the server using its hostname. ChromeOS rejects an SSO share URL without a hostname.
  • Unavailable server: Check whether the device can reach the file server. If the resource requires an organizational VPN, verify the connection before retrying.

How Can Hexnode UEM Help Configure SMB Access in Managed Guest Sessions?

Hexnode UEM provides ChromeOS managed guest session content policies for configuring network file-sharing behavior. Administrators can access these controls through the policy editor.

Where Can Administrators Configure SMB Settings in Hexnode UEM?

To configure SMB access:

  • Log in to the Hexnode UEM console.
  • Navigate to Policies and select New Policy or edit an existing policy.
  • Select ChromeOS > Managed Guest Session > Content.
  • Click Configure.

Configure the required options:

  • Network file share
  • NTLM authentication
  • Preconfigured file share mode
  • File URL
  • NetBIOS discovery

For details, consult Content settings in managed guest sessions.

How Can Administrators Apply the Configuration?

After configuring the policy, navigate to Policy Targets > Domains/OUs and click +Add Domain/OUs. Select the Google Workspace account integrated with Hexnode, choose the required parent or child organizational units, and click OK.

Then, associate the policy with the selected OUs and click Save. Hexnode applies ChromeOS policies through organizational units. Parent OU assignments also extend to their child OUs.

How Does Hexnode Handle Kerberos Configuration?

Separately, administrators can navigate to Managed Guest Session > Basic to configure Kerberos settings. These include Kerberos, Autocomplete Kerberos domain, and Use custom pre-filled configs for Kerberos. The Custom configuration field accepts the Kerberos configuration for managed guest sessions.

Hexnode Unified Endpoint Management
Featured Resource

Hexnode Unified Endpoint Management

Discover how Hexnode UEM helps IT teams manage endpoints from a centralized console.

Download the Datasheet

Frequently Asked Questions

Yes. Administrators can configure ChromeOS network file sharing for managed guest sessions through supported policies.

No. NTLM is an optional authentication setting for SMB file share mounts. Enable it when the file server’s authentication requirements call for NTLM.

NetBIOS discovery enables ChromeOS to discover network file shares using NetBIOS name queries. However, preconfigured file share settings control how administrator-specified URLs appear to users or mount automatically.

Yes. ChromeOS supports Kerberos-based SSO for Active Directory users. Google’s documented configuration does not support kiosks. Administrators should verify environment compatibility before deployment.

Prepare Your ChromeOS Guest Session SMB Configuration with Hexnode UEM

Reliable ChromeOS guest session SMB access requires the right authentication, discovery, and mounting configurations. Before deployment, test access permissions and mounting behavior across intended managed guest sessions.

Hexnode UEM helps administrators configure these settings through policies and apply them to selected organizational units. Request a ChromeOS Policy Demo.

Share

Nora Blake

I write at the intersection of technology, process, and people, focusing on explaining complex products with clarity. I break down tools, systems, and workflows without any noise, jargon, or the hype.