Infuse can't connect to SMB shares anymore

Streaming & Network
1

Hi,

I’ve recently noticed that Infuse doesn’t connect to my SMB-shares running on my Synology NAS anymore.
This issue seems to appear on all devices where I’m running Infuse ( iphone, ipad, appletv ).

I’ve already looked through the forums here at similar posts but haven’t come up with any troubleshooting steps that seem to resolve my issue.

Configuration:

  • Infuse is up-to-date with latest version available in AppStore for all devices
  • Devices are wirelessly connected to same subnet as NAS
  • Nas has wired connection with LACP enabled

Troubleshooting steps undertaken thusfar:

  • Reinstalled Infuse on all devices → NOK, issue still present.
  • Created new share and tried to configure → NOK, issue still present.
  • Reinstalled NAS, and recreated shares → NOK, issue still present.
  • Tried configuring Infuse using all 4 SMB settings ( V1-3 and legacy ) → NOK issue still present.
  • Disabled LACP configuration and tried connecting to both interfaces on the NAS using different IP-addresses → NOK, issue still present.

I’m slowly running out of ideas as everything has been been either updated, reinstalled, or reconfigured.
Would anybody have any recommendations on what more I could try to solve this issue?

Thanks!

2

I have the same problem : not working for smb

3

I doubt this helps you, but Infuse still is able to connect to SMB shares on my Windows 7 box. At least you can know the problem is not with ALL SMB shares

4

I also have the same issue whathever smb option I choose

5

Welcome to the forum and sorry you’re having problems.

Have you updated to the latest 6.5.7? If not please try that and also you may want to try restarting your ATV also since there were some changes to the SMB library.

6

Hi, I’m facing the same issue.

Connection to Windows 10 and FreeNAS SMB shares from Infuse on my iPhone and AppleTV works only intermittently. Sometimes it takes 1-2 minutes to open a folder (with very few items) or play files from the library or it brings up an error. Then again rarely it works as quickly as it used to. Configuration on the servers has not changed.

Restarting devices, deleting and re-adding shares or changing the SMB version does not alleviate the situation. Connecting from other devices or even my iPhone using the Files app works without issues.

Report code after trying to access a share and getting a “Could not connect” error: 7DGZM.

I hope this can get some attention and be fixed rather quickly as it affects the core functionality.

7

Your logs contain quite a few network related errors, both for the SMB shares and internet sources Infuse uses for metadata.

This usually indicates some sort of network issue (router, cables, etc…). If possible, I’d recommend checking all cables, restarting the router, and see where that gets you.

8

Thank you for checking the logs so quickly!

I did some more experimenting and it seems adding a share using an IP address instead of a hostname at least always lets Infuse connect to the share (even though it still takes some time to load). Adding the same share using a hostname results in a connection error (it loaded once initially after adding from the discovered shares section). Logs: PED5J. Share “dsa” with a hostname and “dsaip” is the same with its IP address if you can see the share names in the diagnostics file.

I am very certain it is not a general network error as all other apps and speedtests function without issues and Infuse itself on my AppleTV plays even large 4k files without hiccups once it has connected. I can upload diagnostics from there some time later.

I’d be happy to provide any other information if it could be helpful to nail this down, either a misconfiguration on my side, although this would surprise me as Files and VLC can connect every time, or some issue with Infuse.

9

Hi,
I had the same issue, no clue what caused the problem, but it was not the first time. The Infuse app cannot make the available devices on the local server appear. My solution that worked for me was to add my Synology NAS again manually by selecting SMB (again) and write the IP (192.168.1.5) to the address instead of disk station.local. Everything went back to normal. And the app still doesn’t find the NAS automatically.

10

I came here as I was having this same issue. After some trial and error the fix was:

  • Create an Infuse user account with a strong password in Synology DSM with the following settings
    • Member of the “users” User group
    • Permissions - tick Read Only access to the share folder to be accessed in Infuse
  • In Infuse setup the share as SMB and choose the server address in yourservername.local format (which is Infuse default)
  • Specify a user name same as you created in DSM
  • Specify the password you created in DSM
11

Yeah, have had issues in general not only with SMB non of the connections I had in earlier versions works, and support was no help and I have just attempted it again today and nothing so glad that I have not wasted any more money on this product

12

Sorry for the trouble, but if you are able to drop a quick note from your device and post the code here we can look into what may be causing issues in this specific case.

13

I’m having a similar problem of not being able to connect to SMB-share as of yesterday on a Mac-to-ATV setup.

After troubleshooting I seem to have worked out that it’s likely related to updating NordVPN (or less likely to the latest Infuse update as both done around the same time yesterday). Now Infuse on my ATV won’t connect to the SMB-share when a VPN is active on my Mac but will connect when the VPN is turned off.

Any ideas on why this would be or what I can do to fix it? Before yesterday I could turn a VPN on or off at any time on my Mac and not effect the ATV/Infuse at all.

14

We’ve uncovered another macOS Sonoma quirk that may be preventing SMB connections from working as expected. Steps for checking and resolving this can be found in this guide.

Note: If you have already added a connection in Infuse using the old name, you will need to remove and re-add the share using the new name.

15

Is “quirk” a polite way of saying bug?

Is this something that Apple may de-quirk once they realize that it’s causing problems?

Are you reporting this to Apple as a bug?

16

In the past, changing the local hostname would also change the SMB sharing name, but this no longer appears to be the case.

I’m not sure if it’s intentional or a bug, but for now it just is. :man_shrugging:

Note: I am seeing this on a brand-new MacBook Pro which was set up from scratch (no data transferred from old Mac).

17

Hi!

I have been using Infuse Pro for a couple of months and up until now it was seamless. However, now Infuse on my Apple TV keeps saying “Sorry, Infuse encountered an error while trying to connect” when I try to add my MacBook Pro as a share.

I did all the things mentioned in this thread (macOS Sonoma & Apple TV 4K Setup?) and I am still having issues. Could someone please help me understand the issue?

I created a “Standard” user called Infuse on my Mac, File Sharing and Windows File Sharing are on for this user. I have also made sure that the folder I have my stuff on is accessible by the Infuse user.

Please let me know if you wanna know something else!

Configuration:
M1 MacBook Pro with macOS Sonoma 14.2.1
Apple TV 4K (3rd gen) running Infuse 7.6.6. The Apple TV is connected to the router by LAN (not sure if this matters).
Diagnostics from Apple TV: BZZDX

18

See the post above for a potential files for this.

19

Thanks! I checked the linked article about verifying device address on Mac, and I have an IP address shown in File Sharing. Is there something else I should do?