AIMP Samba Share Not Connecting: How to Fix It

When an AIMP Samba share is not connecting, the failure usually comes from one of five places: an incompatible SMB protocol version, an incorrect server or share address, rejected credentials, blocked network access, or an outdated playlist entry. AIMP for Android supports Windows shared folders and NAS storage through Samba v2 and v3, but it cannot connect to a server that offers only SMB v1. The steps below isolate each possibility without deleting playlists, weakening security, or changing unrelated playback settings.

1. Confirm the Symptom With a Small Safe Test

Start by separating an AIMP problem from a server or network problem. Do not begin by reinstalling the player, resetting the NAS, or changing several settings at once. A controlled test will tell you which side of the connection needs attention.

1.1 Test the share from an Android file manager

Install or open a reputable file manager that supports SMB connections. Add the same server using the same address, share name, username, and password that you intend to use in AIMP. For example, if the Windows path is \\192.168.1.20\Music, the important values are the server address 192.168.1.20 and the share name Music.

Try opening one ordinary MP3 or FLAC file located near the top of the shared folder. Choose a file with a short, simple name so that unusual characters and deeply nested folders do not complicate the test.

• If the file manager cannot connect, troubleshoot the server, credentials, or network before changing AIMP.
• If it opens folders but cannot read the file, review the account's file permissions.
• If it can play or download the file, the server and basic network route are working.

Success means the Android device can browse the share and read the test track. Once that happens, stop changing Windows sharing and move to the AIMP-specific steps.

1.2 Verify the share from another computer

For a Windows-hosted folder, test it from another computer using a UNC path such as \\PC-NAME\Music or \\192.168.1.20\Music. For a NAS, use its normal file-sharing interface or map the share from a computer.

If no device can open the share, the issue is not an AIMP audio player issue. Confirm that the host is awake, the folder is still shared, and the storage volume is mounted. A sleeping PC, disconnected USB drive, or unmounted NAS volume can leave an old server entry visible even though its files are unavailable.

2. Add the Samba Share in the Correct Part of AIMP

In AIMP for Android, network files are added through the playlist file-selection workflow. The local music library is designed primarily to find and organize files stored on the device. Therefore, a Samba folder that works as a playlist source may not behave like an ordinary local library folder.

2.1 Create the connection through the playlist

Open the playlist screen, use the add-files control, enter AIMP's file manager, and add a shared Windows folder from its main screen. Enter the server details in the fields presented by AIMP rather than pasting a complete path into an unrelated search or local-folder field.

The interface can vary by release and device layout, but the connection should contain these essential values:

• Server: The computer name, NAS hostname, or local IP address.
• Share: The published share name, not necessarily the physical folder name.
• Username: An account recognized by the Windows PC or NAS.
• Password: The network account password, not a phone unlock code or Windows PIN.

Success means AIMP displays the folders inside the share and allows you to add a small test track to a playlist. If the folder opens, do not keep modifying the server address or credentials.

2.2 Distinguish the share name from the folder path

A common AIMP Samba share not connecting fix is correcting the share name. Suppose the music is physically stored at D:\Media\Music, but Windows publishes that folder as Audio. The network share is Audio, not D, Media, or Music.

Start with the share root before adding subfolders. Use the equivalent of server/Audio, confirm that it opens, and then browse to an album inside AIMP. Avoid guessing whether the form requires an smb:// prefix. Use AIMP's dedicated server and share fields when available. If AIMP accepts a single server field, try the plain hostname or IP address first.

2.3 Test the IP address when the hostname fails

Local hostname discovery can fail even when direct network access works. Replace a name such as MUSIC-PC with its local address, such as 192.168.1.20. If the IP works, the connection problem is name resolution rather than audio decoding, output mode, tags, or the selected skin.

A local IP may change after the router restarts. If the address solves the problem, create a DHCP reservation in the router so the server receives the same address consistently. Do not expose the SMB service directly to the public internet.

3. Confirm Samba v2 or v3 and Valid Credentials

3.1 Make sure the server supports SMB v2 or v3

AIMP for Android supports Samba v2 and v3. A router, old NAS, or legacy media appliance configured for SMB v1 only will not connect. Open the device's administration page and look for a setting named SMB protocol, minimum SMB version, maximum SMB version, CIFS version, or Windows file service.

Select SMB v2, SMB v3, or automatic negotiation that includes both. If the device offers only SMB v1, update its firmware or replace the obsolete sharing method. Do not enable SMB v1 on Windows merely to accommodate old hardware. SMB v1 has known security weaknesses and is not required for modern AIMP Samba access.

Success means the same share becomes accessible after the server begins offering SMB v2 or v3. Once AIMP can browse it, leave the negotiated protocol enabled and move on to playback testing.

3.2 Use a real server account

Guest access is often inconsistent across Windows, NAS devices, and SMB clients. Create or use a password-protected account on the server and grant that account read access to the music share. For Windows, the username may need to be entered as PC-NAME\username or as the local username alone. A NAS normally expects an account created in its own administration interface.

A Windows Hello PIN is not automatically the password used for network authentication. If the user signs in to Windows with a PIN, enter the underlying account password when AIMP requests Samba credentials.

Check both layers of Windows access control:

1. Confirm that the account has permission in the folder's sharing settings.
2. Confirm that the account has read permission in the folder's Security properties.

The effective access is limited by the more restrictive layer. Success means the account can list folders and read a track without an authentication loop or access-denied message.

3.3 Recreate saved credentials carefully

If the password changed, remove the failed Samba connection from AIMP and create it again with the current credentials. Repeatedly editing an old entry can make it difficult to tell whether AIMP is using a stored value or the value you just typed.

Pay attention to capitalization, spaces, keyboard language, and automatic text corrections. Test a straightforward server account rather than temporarily removing password protection from the whole network.

4. Check Android Network Access and Router Boundaries

4.1 Allow permissions related to network and media access

Open Android Settings, find AIMP under Apps, and review its permissions. Allow any requested permission related to local network access, nearby devices, music and audio, or files and media when that permission is presented by your Android version and device manufacturer. Permission labels differ among Android releases, so focus on access that directly affects local-network discovery or audio files.

If you previously denied a permission permanently, Android may stop displaying AIMP's prompt. Grant it from system settings, return to AIMP, and retry the test share. Success means the connection proceeds beyond server discovery or the previous permission error.

4.2 Put the phone and server on a reachable network

The phone and Samba server normally need to be on the same home or office network unless a properly configured VPN provides access to the server's private network. Mobile data alone cannot reach an address such as 192.168.1.20. Those private addresses are not routed across the public internet.

Check these common boundaries:

• The phone is on the main Wi-Fi network, not an isolated guest network.
• The server is not separated into an IoT or VLAN network that blocks client access.
• Wireless client isolation or access-point isolation is not preventing local connections.
• The VPN is not sending local traffic through a remote gateway that cannot reach the server.
• A privacy or firewall app is not selectively blocking AIMP's local network traffic.

For a safe test, disconnect a third-party VPN briefly, keep the phone on trusted home Wi-Fi, and retry AIMP. If that works, configure the VPN for local-network access or split tunneling rather than leaving it disabled permanently.

4.3 Avoid forwarding SMB ports to the internet

Do not solve remote-access problems by forwarding SMB ports from the router to a Windows PC or NAS. If you need your music while away from home, use a trusted VPN that gives the phone an authorized route to the home network, or use a secure remote-access feature supported by the NAS.

After connecting through a VPN, test the server address in an SMB-capable file manager before testing AIMP. If the file manager cannot reach the server, correct the VPN route, firewall rule, or subnet access first.

4.4 Review battery and background restrictions only when playback drops

Battery restrictions are unlikely to explain a share that never opens, but they can matter if browsing works and playback stops after the screen turns off. Open AIMP's battery settings and permit appropriate background activity. Also check whether Wi-Fi is configured to disconnect aggressively during sleep.

Success means a network track continues playing with the display off. Stop there. There is no reason to alter audio output methods or Bluetooth profiles when the actual failure is the network session being suspended.

5. Diagnose AIMP Playlist and Playback Behavior

5.1 Add a fresh track instead of trusting an old playlist entry

An existing playlist may refer to an old hostname, IP address, share name, folder structure, or server connection. After confirming that the share opens, browse to one track through the newly created connection and add it to a temporary playlist.

If the fresh item plays but older items do not, the network connection is fixed. Re-add the affected folders rather than changing codecs, skins, tag settings, or the audio output system. Old playlist paths do not automatically become valid when a share is renamed.

5.2 Use a short, ordinary test file

Choose a locally playable MP3, AAC, OGG, or FLAC track with a short filename and place a copy directly in the share's top-level folder. This helps separate Samba access from a damaged file, unsupported format variation, unusual filename, or deeply nested path.

• If the simple file plays, test the original folder and track next.
• If AIMP lists the file but cannot start it, copy that exact file to Android storage and play it locally.
• If the local copy also fails, investigate the file itself rather than Samba.

Tag data and embedded artwork may make a network track slower to inspect, especially when artwork is very large. However, tags, skins, and visualizer plugins do not normally prevent AIMP from authenticating with a Samba server. Change those components only if the share opens and a repeatable playback or interface failure points to them.

5.3 Do not troubleshoot unrelated output settings too early

AudioTrack, OpenSL, AAudio, Bluetooth profiles, equalizer settings, and output-device selection can affect audible playback. They do not ordinarily determine whether AIMP can list a Windows shared folder. If the error appears before the folder opens, stay focused on SMB version, addressing, credentials, and network reachability.

Consider changing the output method only when the network track visibly plays, its timer advances, and no sound is heard. In that case, first test the same track through the phone speaker and check Android's media volume and current output device.

6. Use AIMP Logging and a Temporary Clean Test

6.1 Capture a log after reproducing the failure

If basic AIMP troubleshooting does not reveal the cause, open AIMP's About area and look for its logging option. Enable logging, reproduce the connection failure once, and save the resulting log. Turn logging off afterward unless AIMP support asks you to leave it enabled.

Record the exact test conditions with the log: whether you used a hostname or IP address, whether the server uses SMB v2 or v3, whether another Android SMB client works, and whether AIMP fails during connection, folder listing, file opening, or playback. Do not publish a log without checking it for server names, usernames, addresses, or other private details.

6.2 Build a temporary playlist

Create a new empty playlist and add only the short test track from the newly configured share. This clean test avoids stale paths, missing files, playlist sorting rules, and unrelated radio, podcast, cloud, WebDAV, or local-library entries.

If the clean playlist works, keep the functioning Samba connection and rebuild only the affected playlist entries. Do not delete every playlist or reset the entire app.

6.3 Test without optional customizations when AIMP itself is unstable

If AIMP freezes, closes, or displays a broken connection screen, temporarily return to the standard skin and disable optional components that directly alter the affected interface. This is different from assuming every plugin causes network failure. The goal is to determine whether the connection form or playlist screen is malfunctioning.

Success means the standard interface can create the connection and play the test file. Re-enable customizations one at a time, stopping when the symptom returns.

7. Run a Clean Test Before Reinstalling AIMP

Before reinstalling, write down the working server details and preserve important playlists. Then perform one final controlled sequence:

1. Connect the phone to the same main Wi-Fi network as the server.
2. Pause any VPN that may block local access.
3. Confirm the share works in an SMB-capable file manager.
4. Verify that the server offers SMB v2 or v3.
5. Create a new AIMP Samba connection using the server's IP address.
6. Enter a password-protected account with read permission.
7. Add one short test track to a new playlist.
8. Play it through the phone speaker.

If this sequence works, the core AIMP Samba function is healthy. Stop changing settings and add the rest of the music gradually. If the file manager works but the clean AIMP test still fails, preserve the log and contact AIMP support or post in the appropriate AIMP for Android forum section with reproducible details.

Reinstallation should be a late step because it does not upgrade an SMB v1 server, correct a misspelled share name, restore Windows permissions, or bridge an isolated guest network. It may also remove saved settings or make playlist recovery more difficult.

8. Quick Fix Checklist

• Confirm the server is powered on and its storage volume is mounted.
• Verify the share from an SMB-capable Android file manager.
• Use Samba v2 or v3, not SMB v1.
• Enter the server address and published share name separately when possible.
• Try the server's local IP address if its hostname fails.
• Use a valid server username and password rather than guest access.
• Grant the account both share and file-system read permission.
• Allow AIMP's relevant Android network and media permissions.
• Use the main Wi-Fi network instead of an isolated guest network.
• Test without a VPN that may block local routes.
• Add the share through AIMP's playlist file manager.
• Create a fresh playlist entry instead of relying on an old path.
• Test one short, known-good audio file.
• Enable AIMP logging only long enough to reproduce the failure.
• Do not expose SMB ports directly to the internet.

9. Frequently Asked Questions

9.1 Does AIMP for Android support Samba v2 and v3?

Yes. AIMP's official Android feature information states that Windows network and NAS access supports Samba v2 and v3. A server limited to SMB v1 will need a firmware or configuration update. Enabling the obsolete SMB v1 protocol is not the recommended fix.

9.2 Why does the Samba share work in a file manager but not AIMP?

The most likely causes are an incorrectly entered AIMP connection, a stale saved credential, or an old playlist path. Create a new connection from AIMP's playlist file manager, use the same tested values, and add one file to a new playlist. If it still fails, reproduce the issue with AIMP logging enabled.

9.3 Should I add a Samba folder to the AIMP music library?

Use AIMP's playlist and file-adding workflow for Samba content. The Android music library is intended for automatic organization of local files, so a network share should not be judged by whether it behaves like a local library folder.

9.4 Why does the share work by IP address but not computer name?

That indicates a local name-resolution or discovery problem. You can use the IP address and reserve it in the router, or troubleshoot hostname resolution separately. There is no need to change AIMP's decoder, equalizer, output method, or skin.

9.5 Can AIMP reach my home Samba share over mobile data?

Not directly through a private home address. Use a securely configured VPN that routes the phone to the home network, then confirm the share in an SMB-capable file manager. Do not forward ordinary SMB ports to the public internet.

9.6 Why can AIMP browse the share but not play one particular file?

Copy that file to Android storage and test it locally. If the local copy fails, the file may be damaged or use an unsupported variation. If it works locally, shorten its filename or folder path, compare its permissions with a working track, and add it through a fresh AIMP playlist entry.