Morris_Z
Level 2: Rookie

I can no longer open network USB files from Mac OS Big Sur

I used to be able to read files from USB plugged into Telstra Smart Modem Gen 2 router/modem. I can see the device in the browser at http://192.168.0.1/gateway.lp but no longer can I open it from my Mac Finder.

Any Suggestions?

The USB storage device shows up in the Content Sharing panel. But From my MacBook Air Finder under Network > telstra-modem > Connect As all I get is an error message "There was a problem connecting to "telstra-modem" Check the server name and IP address and try again ....".Mac OS Big Sur 11.6

An older 2012 MacBook Pro on OS10.14 Mojave will connect and read the networked driver as before! It will allow read and write as “Guest” but will throw up error message if I hit “Connect As”. Then the connection disappears BUT will return after waiting many minutes and connect/edit as Guest is automatically restored.

From the older Mac in Terminal this command will list all files on the USB:

ls /Volumes/SanDisk_Extreme_1_82ff/Jaques_Diffaction_Photos/003/

But on the MacBook Air I get a "No such file or directory".

I have talked to Telstra help chat people without success.

Any suggestions appreciated.

Regards

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
27 REPLIES 27
cf4
Level 25: The Singularity
Level 25: The Singularity

Re: I can no longer open network USB files from Mac OS Big Sur

The  latest firmware (20.3.c.0329-MR19-RB) for the Technicolor version of the Smart modem (DJA0231) upgraded  SMB from 1.0 to 2. Is SMB version 2 enabled on the MAC?

Morris_Z
Level 2: Rookie

Re: I can no longer open network USB files from Mac OS Big Sur

Thanks cf4

My firmware 20.3.c.0329-MR19-RB 

SMB enabled?

Well maybe not. In iTerm this is what I get:

% which smb
smb not found

What do I have to do now?

Regards

Morris_Z
Level 2: Rookie

Re: I can no longer open network USB files from Mac OS Big Sur

I still haven't found a solution to this.

Maybe if someone has the energy to look at this thread on the Apple help where I have more details of the various attempts to solve it you may get some ideas.

https://discussions.apple.com/thread/253152384?answerId=255921894022&cid=em-com-apple_watches_email_...

 

Hope someone can help.

Regards

George

Jupiter
Level 25: The Singularity
Level 25: The Singularity

Re: I can no longer open network USB files from Mac OS Big Sur

A suggested solution on Reddit is:

  1. Open the Terminal app, which is in the Utilities folder of your Applications folder.

  2. Type sudo /usr/libexec/configureLocalKDC and press Return.

  3. Enter your administrator password and press Return.

  4. Quit the Terminal app.

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big Sur

Hi - I tested this out on a DJA0230 with current firmware and connected wirelessly to it from my Mini Mac on 11.6 Build (20G165) which was released on the 13th September 2021( also the 13th version of 11.6) and got the same failed authentication behaviour as you did. The work around code suggested by @Jupiter seemed to be apply back in earlier versions going back to 2018, so it may still help but I haven't loaded it as I don't use a USB external drive. MacRumour posts confirmed the SMB issue was addressed in 11.3.2 however I am not aware if those posts related to NAS applications only.

 

The new Technicolor firmware replaced Samba with YNQ Visualityynq.com for the embedded modem File Server conversion utility but it appears that may have also influenced the previous anonymous log-in access (Guest) that was used successfully from a Mac.  On 11-04-2021 ( assume it was 11.2.3 then per Wikipedia History), I was able to access a USB stick connected to the DJA0230 by selecting Guest when challenged by the MacOS, without a password and now that does not work. Looking back now, maybe that was bug with Authentication in 11.2.3. 

 

Unlike the Arcadyan LH:1000 where you can enter an authorised User and Password to individuals into the modem to allow access from authorised parties on your modems's network, the Technicolor modem has no such input screens for File Server on its Shared Content Screen, so I am not sure if this influences matters. I have tried all combinations including using the log-in admin and password code for the modem itself rather than the presented Mac PC owner's name and password but won't connect. The Beta 11.6.1 (20G214) was released on 6th October 2021 - is this the version you have - if you select 11.6, it reveals the Build Number.

Morris_Z
Level 2: Rookie

Re: I can no longer open network USB files from Mac OS Big Sur

Jupiter

Thanks for that suggestion. I'm nervous about trying it that so I haven't done it yet.

Could you please tell me a bit more about what this particular command is doing and why it might be the solution to my problem. I am familiar with Terminal commands but not familiar with libexec/configureLocalKDC and what it does. 

Also I wonder if you could comment on the response below from Mkrtich and whether it is relevant to your suggestion.

Regards

George

Jupiter
Level 25: The Singularity
Level 25: The Singularity

Re: I can no longer open network USB files from Mac OS Big Sur

It seems that this has been a persistent bug for quite a few years, the most recent post that I have seen about the suggestion solution that I posted working was in June 2021 on MacRumors.

 

The local Key Distribution Center (LKDC) facilitates single sign-on for Apple Filing Protocol (AFP) file sharing and screen sharing. The command kickstarts it. According to people who have said that they have tried it, it's not a 100% fix, but does make file sharing more reliable.

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Morris_Z
Level 2: Rookie

Re: I can no longer open network USB files from Mac OS Big Sur

Mkrtich

Seems like you have very similar problem to mine.

My modem as displayed on modem page. Maybe you can make sense of it.
Technicolor DJA0231
Software Version
20.3.c
Firmware Version
20.3.c.0329-MR19-RB
Hardware Version
VCNT-A
DSL Version
A2pvfbH046y.d27j
Serial Number
CP1845RAAWK
 
Regards
George 
 
Morris_Z
Level 2: Rookie

Re: I can no longer open network USB files from Mac OS Big Sur

Jupiter

OK on "persistent bug".

After reading man configureLocalKDC,  I first ran this command: sudo /usr/libexec/checkLocalKDC

And - although still mysterious - is does seem to indicate there is some kind of certificate problem:

georgewright@Georges-MacBook-Air ~ % man configureLocalKDC

georgewright@Georges-MacBook-Air ~ % man checkLocalKDC
georgewright@Georges-MacBook-Air ~ % sudo /usr/libexec/checkLocalKDC
Password:
The KDC certificate hash (B0AB0DEDB981F79E77F582C654AB652C54C84FDD425A01A86CA0ED6DB63B4DEE) does not match the realm (48B5BE46004F3CC4AB4FCF8621AE26C5D2DB7F85).

So I then went ahead and tried your suggestion:

Georges-MacBook-Air ~ % sudo /usr/libexec/configureLocalKDC

I ran the checkLocalKDC again and found the same “does not match” message. That was after a computer restart too.

georgewright@Georges-MacBook-Air ~ % sudo /usr/libexec/checkLocalKDC

The KDC certificate hash (B0AB0DEDB981F79E77F582C654AB652C54C84FDD425A01A86CA0ED6DB63B4DEE) does not match the realm (48B5BE46004F3CC4AB4FCF8621AE26C5D2DB7F85).

The attempts to read the USB failed as before. Meanwhile the older Mac continues to work OK.

So it doesn’t look like we have a solution yet.

Regards

George

Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big Sur

Hi - your modem has current firmware for the DJA0231 - the VCNT-A internal hardware structure uses two PCBs connected together in a metal cage - this is called the Gen2 model. The modem I used for the testing is a DJA0230, the predecessor VBNT-V hardware structure which has a different form factor, a rather large rectangular footprint, likely to be one PCB - it is called Gen 1.1. The DSL hardware is the same. 

 

Prior to firmware 20.3.c 0329-MR19-RB, the firmware levels were different, but with the current release, they are now the same. I used 192.168.50.1 as IP addressing scheme - with Windows, it makes a difference if you change the default 192.168.0.1 range and try to view the contents of the File Server connected USB in Network  icon - you have to use the explorer bar to map the drive successfully. All works without a user ID and password challenge using Windows - my Win 10 PC is defaulted to SMB2. I assume you are not using the NetDuma OS. I also tried afp://192.168.50.1 but no luck.

 

Mojave OS 10.14.6 had an update on July 2021, Build 18G9323, so strange that both versions of OS display different behaviour with SMB compliance on the DJA0231. Given that Windows 10 and Mojave work, it suggests the bug is with MacOS 11.6.1.  (Build 20G214).

 

 

Janlor
Level 1: Cadet

Re: I can no longer open network USB files from Mac OS Big Sur

Hi Morris_Z

I am wondering if you have found a solution to your problem which appears to be identical to mine, although I have a Seagate portable SSD connected via USB to my modem, Telstra Smart Modem Gen 2.

I have had no problems connecting to it and accessing my files previously.  I don't access it very often, so it is also quite likely that the problem has occurred since upgrading to Big Sur.

I would appreciate any further info you may have.

Cheers.

Morris_Z
Level 2: Rookie

Re: I can no longer open network USB files from Mac OS Big Sur

Well No Janlor,  I haven't solved it .

None of the suggestions on this thread have lead anywhere.

Thanks for your contact. Good to know the problem is out there and not just something in my setup.

I think it must be partly a Big Sur problem but I have no response from the Apple people either.

You might be able to read this thread on the Apple Community site where I was able to post pics showing more detail than I could show here. Maybe you have to log in.

https://discussions.apple.com/thread/253152384?answerId=255921894022&cid=em-com-apple_watches_email_...

 

At least there is a record of the issue so someone in the future might solve it.

Meanwhile my old 2012 MacBook Pro continues to read the networked files as before!

Regards

George

I've clicked the No, I still need help thing below but that didn't lead anywhere either.

Morris_Z
Level 2: Rookie

I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files fro

I've had this thread running quite a while with no solution.

The thread is here:

https://crowdsupport.telstra.com.au/t5/community-feedback/i-can-no-longer-open-network-usb-files-fro...

 

I have also had help from Telstra chat with no result.

 

I have also had a parallel thread going on the Apple community support but again with no solution.

If you can read this thread I have fully explained the problem and what I have tried.

https://discussions.apple.com/thread/253152384?answerId=255921894022&cid=em-com-apple_watches_email_...

 

I think there is an incompatibility between the "Big Sur" operating system on the computer and the server functions in the particular model of Telstra modem. Someone who is familiar with Mac and Telstra modem might be able to help.

Regards

George

Jupiter
Level 25: The Singularity
Level 25: The Singularity

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

There's no need to start a new thread, adding to the existing one bumps it to the top of the list.

 

The Apple forum is the most likely place to get an answer as you have already stated that your older machine still accesses the network files properly. So you would need to understand from Apple about what has changed with MacOS that causes it to no longer work.

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Hi - I haven't got any success story to share and now I am not sure if the issue is with modem or the Mac. I upgraded our Mini Mac from 11.6.0 to 11.6.0.1 tonight hoping for some good news but no progress. I was invited to upgrade to 12.0.1 Monterey OS which has just been released but thought I would wait a month to see how it goes. 

 

It seems to me the Big Sur Mac OS is strictly looking for an SMB Server User ID and Password for authentication input from the client but the modem is not structured for this as it uses unchallenged Anonymous access to USB mounted drives. Using the Modem's Log-In credentials for the SMB Server doesn't work.  

 

With a USB drive mounted in the modem, when I use Terminal command  smbutil statshare -a   <return> , testing two USB sticks, I get  empty fields for Attribute Type and Value indicating the OS thinks the USB drive is not mounted. Both USB sticks were VFAT formatted.

It should look like this example from a web page.

 

This is an example how smbutil statshares -a looks like on MacOS 10.15.4:

~ $ smbutil statshares -a

==================================================================================================
SHARE                         ATTRIBUTE TYPE                VALUE
==================================================================================================
SomeShareName
                              SERVER_NAME                   MYSERVER._smb._tcp.local
                              USER_ID                       502
                              SMB_NEGOTIATE                 SMBV_NEG_SMB1_ENABLED
                              SMB_NEGOTIATE                 SMBV_NEG_SMB2_ENABLED
                              SMB_NEGOTIATE                 SMBV_NEG_SMB3_ENABLED
                              SMB_VERSION                   SMB_3.02
                              SMB_SHARE_TYPE                DISK
                              SIGNING_SUPPORTED             TRUE
                              EXTENDED_SECURITY_SUPPORTED   TRUE
                              LARGE_FILE_SUPPORTED          TRUE
                              OS_X_SERVER                   TRUE
                              DFS_SUPPORTED                 TRUE
                              FILE_LEASING_SUPPORTED        TRUE
                              MULTI_CREDIT_SUPPORTED        TRUE
                              ENCRYPTION_SUPPORTED          TRUE
                              ENCRYPTION_REQUIRED           TRUE

---------------------------------------------------------------------------------

 

Jupiter
Level 25: The Singularity
Level 25: The Singularity

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Avoiding Monterey would be a very good move as it has been killing Macs that don't have the newest Apple chips in them. Don't know what's going on with Apple recently but they've really dropped the ball on their OS releases in the past couple of years. They used to be really good at making sure their OS releases were stable, but now ????.

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Yes, I agree. There seems to be a focus on more how things look like, developing features for the challenge of it, rather than for customer usage e.g. a touch bar on a MacBook which has now been removed and minor tweaks for a very restricted audience. By no means am I discounting the effort involved in keeping the OS relevant and reliable in a fast paced competitive environment where things change on a quarterly basis. Things appear to reflect too many changes done too fast without a lot of beta testing - that may also reflect the state of the whole of the PC industry. 

 

I have been an Apple fan and user starting with the Apple 2e and since those days having the original 1983 Macintosh, followed by the Centris 610 with a huge leapfrog in time back into a Mac Mini in 2014 and I can't help but admire what Apple has achieved and continues to develop. Apple's focus on their core business of mobile phones have historically placed their PC line of business behind and hopefully more attention will be directed back towards their PC's with the M1 chip. 

 

Visuality Systems is an Israeli company who specialise in providing SMB access in embedded OS systems with their YNQ suite and I understand that is what Technicolor firmware version 20.3 has adopted. I haven't found any significant data on their Mac Client compatibility in Linux based routers which act as the SMB Server for USB connected external drives. Web searches have revealed many posts of people not being able to connect to SMB servers with the Mac OS and most of their suggested workarounds didn't seem to work for the cases that followed. 

Morris_Z
Level 2: Rookie

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Mkrtich

Similar result for smbutil statshares -a. > An empty table on Big Sur and something similar to your pic on the older computer. I notice your SMB_VERSION is 3.02 , mine is 3.00. 

There are many things I don't understand so I have some questions about that.

Is that SMB server running on the modem hardware Or is it part of the OSX software ?? (smb in Terminal gets "Command not found)"  Is it possible to update. Are firmware updates on the modem automatic? Or am I supposed to check for updates myself? If so how?

Maybe a newer Telstra modem is the answer?

And one other thing ... your screenshot above .. how did you do that? I can see no way for posting pics onto this thread. Yours doesn't seem to be a png or similar . It is searchable text on the screen. How can I post pics here?

Regards

George

Jupiter
Level 25: The Singularity
Level 25: The Singularity

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

You can post images by clicking on the camera icon and selecting the file (so screenshots need to be saved first). 

 

 

The searchable text was done using html code in the message rather than it being a screenshot.
It was a copy and paste, just with some formatting added.

 

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Morris_Z 

The SMB has two elements - Client Software (OSX) and Server Software (Modem). The Modem has an embedded application that translates the native modem Linux OS commands to SMB Server commands so that users can access USB drives. Telstra modems traditionally only supported SMB1 which Microsoft later discontinued due to security breaches and adopted SMB2 as default in Windows 10. People had to wind back the default setting to SMB1 in order to access their files on a USB drive connected to their modem. Up until firmware 20.3, Technicolor used an Open Source translator package called SAMBA and they chose to stay with SMB1 throughout the last five modems they distributed instead of upgrading to SMB2 and 3 thereby limiting the functionality to SMB1 capabilities.

 

With 20.3 Technicolor adopted a non Open Source translator from Visuality Systems called YNQ which supports SMB1, SMB2 and SMB 3. This morning I cranked up an old Technicolor TG800vac which supports SMB1 only and mounted a USB stick into it. I then did the [smbutil statshares -a] command in Terminal and got this screen.

~ % smbutil statshares -a

 

==================================================================================================

SHARE                         ATTRIBUTE TYPE                VALUE

==================================================================================================

SCSI_DISK_1_268d              

                              SERVER_NAME                   10.0.0.138

                              USER_ID                       501

                              SMB_NEGOTIATE                 SMBV_NEG_SMB1_ENABLED

                              SMB_NEGOTIATE                 SMBV_NEG_SMB2_ENABLED

                              SMB_NEGOTIATE                 SMBV_NEG_SMB3_ENABLED

                              SMB_VERSION                   SMB_1

                              SMB_SHARE_TYPE                UNKNOWN

                              LARGE_FILE_SUPPORTED          TRUE

 

I think this means that the Mac with Big Sur supports all three SMB versions shown but is using SMB 1 due to the TG800vac being limited to SMB 1 only. 

 

When using the Finder/Go/Connect to Server, I found that if I used smb://10.0.0.138 for the path name which is the default IP address of the TG800vac, it connected immediately and showed the drive as SCSI_DISK_1_268d. The same occurred if I used smb://10.0.0.138/SCSI_DISK_1_268d however it presented a challenge for User ID and Password - this is the Log-In credentials for the modem - as it is a factory reset one, I used 'admin' and empty field for password and it connected successfully.

 

If I used the Browse button, I can see 'telstra-modem' Icon for a modem instead of the GUI name 'Telstra Gateway' and if selected it presents a User ID and Password challenge which I didn't try after previous post failures. I later discovered that is my live Arcadyan modem which is on my Home Network along with my HP PC.

 

As a possible workaround, when you successfully connect your old Mac to the DJA0231, can you right click on the drive, in my case SCSI_DISK_1_268d and select Get Info - at the bottom section, Sharing & Permissions, your connected Mac will have full permissions, is 'everyone' underneath toggled to 'Read&Write'? Maybe that will allow the Big Sur Mac to connect.

 

The Telstra modem will update automatically when there is a new release. The smb Terminal command used has no space between smb and util and should not present an error.

@Jupiter thanks for helping with the picture insertions - I was away all day yesterday. Cheers

Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Just a small follow up. I still can't access the USB drive on the DJA0230 with 20.3 RB firmware from WiFi connected Mac Big Sur OSX. The DJA0231 has identical firmware excluding the external antennae setting used in the DJA0230.

 

To verify the USB stick did not have any issues and to check its capability, I mounted the stick into my Arcadyan LH:1000 0.15.16r and linked to it from my HP Win 10 PC with the pre-assigned User ID and Password I had previously entered into the modems's GUI - these credentials are used to enter when challenged by the Microsoft Security Window, all connected fine.

 

I then went to the Mini Mac and linked to it via WiFi with Finder/Go/Connect to Server - used same credentials and linked OK. The smbutil command shows the Arcadyan is operating SMB2.002 (via SAMBA) and as a result supports more functionality than the TG800vac as listed below. 

~ % smbutil statshares -a

 

==================================================================================================

SHARE                         ATTRIBUTE TYPE                VALUE

==================================================================================================

sda1                          

                              SERVER_NAME                   192.168.0.1

                              USER_ID                              501

                              SMB_NEGOTIATE                 SMBV_NEG_SMB1_ENABLED

                              SMB_NEGOTIATE                 SMBV_NEG_SMB2_ENABLED

                              SMB_NEGOTIATE                 SMBV_NEG_SMB3_ENABLED

                              SMB_VERSION                     SMB_2.002

                              SMB_SHARE_TYPE                DISK

                              SIGNING_SUPPORTED             TRUE

                              EXTENDED_SECURITY_SUPPORTED   TRUE

                              LARGE_FILE_SUPPORTED          TRUE

                              FILE_IDS_SUPPORTED            TRUE

                              DFS_SUPPORTED                 TRUE

 

There is definitely an issue between Mac Big Sur and DJA0231 20.3 RB firmware which is frustrating to experience. It's difficult to tell where the problem is. Have you reported this to Telstra Platinum Support for follow up and possible resolution?

Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Ran out of time to add the following.

The Big Sur Mac appears enabled for SMB1/2/3 and has no issue handshaking with the Technicolor TG800vac (SMB1-SAMBA) and the Arcadyan LH:1000 (SMB 2.002 - SAMBA)  but strikes a communication problem with Visuality Systems YNQ in the Technicolor DJA0230 (mine) and the DJA0231 (yours) with 20.3.c 0329-MR19-RB firmware.

 

I am fairly sure that a Windows 10 PC can access USB drives on a DJA0231 with 20.3.c 0329-MR19-RB firmware from another post I read a while ago - will test out. 

Jupiter
Level 25: The Singularity
Level 25: The Singularity

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

I was doing a bit of browsing and found rekordbox were having a similar problem with Big Sur not allowing access or not displaying devices.

 

They suggest going to [System Preferences] >[Security & Privacy] > [Privacy]tab > [Files and Folders] and ticking they checkboxes for the device.

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Thanks Jupiter. That looks like a permission setting for Apps to access Files and Folders rather than a device. On my Mac , I have two entries - Printer proxy.app , Documents Folder ticked and Pages App - Removable Volumes ticked.

 

I think there is an issue with the way Technicolor may have implemented the YNQ API and how Apple is interpreting it which is causing the the Apple Mac to reject its handshake. Usually when this occurs, the three parties need to get together to resolve.  It looks like Apple has supported SMB 3 for quite some time - 10.15.4 is Catalina which was released in late 2019. Apparently if it works on SMB2, it should work on SMB3 according to a web page I read this morning. Most workaround posts on the web relate to Mac User Permission settings, accessing other PCs on a network and a variety of workarounds for specific servers that use SMB - there is no clear fix for all. That is why I have suggested contact with Platinum support for escalation. 

 

It doesn't appear to be an issue with my Windows 10 PC - as an SMB Client, it uses SMB 2 in Default and according to the Get command below, verified with the Run as Administrator in the Powershell App. I assume the command is true to the input and showing the SMB Server parameters - the USB is mounted and the 'ServerHidden' is showing as True?

 

PS C:\WINDOWS\system32> Get-SmbServerConfiguration.  

AnnounceComment :
AnnounceServer : False
AsynchronousCredits : 64
AuditSmb1Access : False
AutoDisconnectTimeout : 15
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 0
DurableHandleV2TimeoutInSeconds : 180
EnableAuthenticateUserSharing : True
EnableDownlevelTimewarp : False
EnableForcedLogoff : True
EnableLeasing : True
EnableMultiChannel : True
EnableOplocks : True
EnableSecuritySignature : False
EnableSMB1Protocol : False
EnableSMB2Protocol : True
EnableStrictNameChecking : True
EncryptData : False
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes :
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeconds : 120
RejectUnencryptedAccess : True
RequireSecuritySignature : False
ServerHidden : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLevel : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAliased : True
ValidateTargetName : True

 

PS C:\WINDOWS\system32>

Jupiter
Level 25: The Singularity
Level 25: The Singularity

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

I get a similar result from my Win10 computer:

PS C:\WINDOWS\system32> get-smbserverconfiguration


AnnounceComment :
AnnounceServer : False
AsynchronousCredits : 64
AuditSmb1Access : False
AutoDisconnectTimeout : 15
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 10
DurableHandleV2TimeoutInSeconds : 180
EnableAuthenticateUserSharing : False
EnableDownlevelTimewarp : False
EnableForcedLogoff : True
EnableLeasing : True
EnableMultiChannel : True
EnableOplocks : True
EnableSecuritySignature : False
EnableSMB1Protocol : False
EnableSMB2Protocol : True
EnableStrictNameChecking : True
EncryptData : False
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes :
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeconds : 120
RejectUnencryptedAccess : True
RequireSecuritySignature : False
ServerHidden : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLevel : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAliased : True
ValidateTargetName : True

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Posting in case a Telstra Product Specialist is reading this post out of interest.

 

This evening, from the Mini Mac Safari view, I looked at the Log file in the Diagnostics card to see what was happening after the initial DJA0230 boot up and then observed events after the USB drive was mounted into the modem with no attempt to access data as I know it fails using the Mac. I find Technicolor log file events not as friendly to read compared to the Arcadyan but here goes. The modem was off line and not connected to my home network or the NBN Internet, so the time stamps are not current. It appears that the Technicolor loses the events on shutdown, so the log file only covers a very short period of time tonight. These entries relate to any lines that included a reference to the USB function.

 

Tue Oct 12 03:43:44 2021 kern.info kernel: [ 0.702082] usbcore: registered new interface driver usbfs
Tue Oct 12 03:43:44 2021 kern.info kernel: [ 0.707631] usbcore: registered new interface driver hub
Tue Oct 12 03:43:44 2021 kern.info kernel: [ 0.713128] usbcore: registered new device driver usb

 

I have excluded USB entries that cover various mobile modem interfaces.

 

First entries that show Visuality Systems FNQ - my highlight on Bold.

 

Tue Oct 12 03:44:40 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 03:44:40 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 03:44:40 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 03:44:40 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 03:44:40 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 03:44:40 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 03:44:40 2021 daemon.notice mobiled: Device 1 will wait 5.541 seconds before initializing
Tue Oct 12 03:44:40 2021 daemon.notice wansensing: (L2Sense) runs L2Main.check(timeout)
Tue Oct 12 03:44:40 2021 daemon.notice wansensing: L2Main.lua: check interface PHY type nil
Tue Oct 12 03:44:41 2021 user.notice firewall: Reloading firewall due to ifupdate of lan (br-lan)
Tue Oct 12 03:44:42 2021 user.err nqnd: E;smb_interfaces.c;config_getInterfaces();267--->Using default Interface(s) value as br-lan
Tue Oct 12 03:44:42 2021 user.err nqnd: E;smb_interfaces.c;config_getInterfaces();267--->Using default Interface(s) value as br-lan

 

Failure to open secret file -

 

Tue Oct 12 03:44:50 2021 user.err nqcs: E;smb_interfaces.c;config_getInterfaces();267--->Using default Interface(s) value as br-lan
Tue Oct 12 03:44:50 2021 user.err nqcs: E;smb_interfaces.c;config_getInterfaces();267--->Using default Interface(s) value as br-lan
Tue Oct 12 03:44:50 2021 user.err nqcs: E;nssessio.c;nsBindInet();501--->Unable to update DNS record
Tue Oct 12 03:44:50 2021 user.err nqcs: E;smb_interfaces.c;config_getInterfaces();267--->Using default Interface(s) value as br-lan
Tue Oct 12 03:44:50 2021 user.err nqcs: E;smb_interfaces.c;config_getInterfaces();267--->Using default Interface(s) value as br-lan
Tue Oct 12 03:44:50 2021 user.err nqcs: E;nssessio.c;nsBindInet();501--->Unable to update DNS record
Tue Oct 12 03:44:50 2021 user.err nqcs: E;udconfig.c;udDefGetComputerSecret();2772--->Failed to open secret file

 

More information on failure NQ failure - USB drive not mounted as yet

 

Tue Oct 12 03:44:52 2021 user.err nqcs: E;cmresolver.c;cmResolverGetDCName();1335--->Select timeout - no response, priority: 4
Tue Oct 12 03:44:52 2021 user.err nqcs: E;cmresolver.c;cmResolverGetDCName();1328--->Get DC Select timeout, methods priority: 5.
Tue Oct 12 03:44:52 2021 user.err nqcs: E;cmresolver.c;cmResolverGetDCName();1439--->All methods failed
Tue Oct 12 03:44:52 2021 user.err nqcs: E;ccdomain.c;domainJoin();491--->failed to get dc for domain WORKGROUP
Tue Oct 12 03:44:52 2021 daemon.warn [8639]: Use tch.logger in /usr/bin/redirecthelper.lua:24
Tue Oct 12 03:44:52 2021 user.err nqcs: E;smb_interfaces.c;addSharefromUCI();401--->Unable to read share description, Adding shareDescription as shareName value : printers
Tue Oct 12 03:44:52 2021 user.err nqcs: E;smb_interfaces.c;addSharefromUCI();416--->Unable to read share Offline, Adding shareOffline as 0 : 0
Tue Oct 12 03:44:52 2021 user.err nqcs: E;smb_interfaces.c;addSharefromUCI();428--->Not adding default share or share is not enabled or share is offline or shareName or/and sharePath or/and shareEnabled or/and shareOffline is/are not provided

 

USB Stick '268d' drive mounted. Left over entries from this morning's second USB drive '2227' appear in lines.

Assume last entry 'd-mount samba' means to remove it and use YNQ.

 

Tue Oct 12 04:16:38 2021 user.crit mountd[8417]: new mount : USB-A1 -> sda1 (fat)
Tue Oct 12 04:16:38 2021 user.crit mountd[8417]: mounting /tmp/run/mountd/sda1
Tue Oct 12 04:16:38 2021 user.crit mountd[13016]: mount -t vfat -o umask=0000,noatime,noexec,errors=continue,iocharset=utf8 /dev/sda1 /tmp/run/mountd/sda1
Tue Oct 12 04:16:38 2021 kern.warn kernel: [ 1995.386581] FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Tue Oct 12 04:16:38 2021 kern.warn kernel: [ 1995.393590] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Tue Oct 12 04:16:38 2021 user.crit mountd[8417]: ----------> mount ret = 0
Tue Oct 12 04:16:38 2021 user.notice hotplug.d-mount-mounts: ACTION=add DEVICE=sda1 NAME=USB-A1
Tue Oct 12 04:16:38 2021 user.notice hotplug.d-mount-mounts: VENDOR=SCSI MODEL=DISK START=48 SIZE=30957584 HASH=268d STATUS=mounted
Tue Oct 12 04:16:38 2021 user.notice hotplug.d-mount-mounts: Add mount sda1 (/tmp/run/mountd/sda1)
Tue Oct 12 04:16:38 2021 user.notice hotplug.d-mount-mounts: Added disk sda
Tue Oct 12 04:16:39 2021 user.notice mvfsd: start mvfsd.
Tue Oct 12 04:16:39 2021 user.notice mud: mud start.
Tue Oct 12 04:16:39 2021 user.err mvfs: metadb_init (Heap)
Tue Oct 12 04:16:39 2021 user.err mvfs: metadb_init (Scratch)
Tue Oct 12 04:16:39 2021 user.err [mud][13178]: mud_monitor_mounted_usb (1493): in mud_monitor_mounted_usb
Tue Oct 12 04:16:39 2021 user.notice dlnad: Reload: restarting
Tue Oct 12 04:16:39 2021 user.notice dlnad: Stopping dlnad
Tue Oct 12 04:16:39 2021 user.notice dlnad: Renaming unknown_SCSI_DISK_1_268d to unknown_<share_name>
Tue Oct 12 04:16:39 2021 user.notice dlnad: Renaming unknown_Generic_FlashDisk_1_2227 to unknown_<share_name>
Tue Oct 12 04:16:40 2021 daemon.warn mobiled: Failed to retrieve ICCID
Tue Oct 12 04:16:40 2021 user.notice dlnad: Starting dlnad
Tue Oct 12 04:16:41 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 04:16:41 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 04:16:41 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 04:16:41 2021 user.notice hotplug.d-mount-samba: ACTION=add DEVICE=sda1 NAME=USB-A1
Tue Oct 12 04:16:41 2021 user.notice hotplug.d-mount-samba: VENDOR=SCSI MODEL=DISK START=48 SIZE=30957584 HASH=268d
Tue Oct 12 04:16:41 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 04:16:41 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 04:16:41 2021 user.err dlnad: 295>No matching interface
Tue Oct 12 04:16:41 2021 user.notice hotplug.d-mount-samba: Add share SCSI_DISK_1_268d (/var/etc/smb.auto/USB-A1.conf)

 

 

 

 

 

 

 

 

 

 

 

Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: I can no longer open network USB files from Mac OS Big SurI can no longer open network USB files

Hi - I had hoped to be the bearer of good news but unfortunately no change of circumstances with the new Technicolor DJA0231 20.3.c.0389 -MR20-RA firmware which I received today when my test modem updated.  Apple OS Big Sur 11.6.1 [Build 20G224] is still being blocked from accessing the USB Drive or the Mac OS has an issue?  The USB drive doesn't show up in the Mac Network Browse window which oddly is blank which led me to think the issue is with the Mac? I was accessing the DJA0231 via WiFi and had a valid IP address assigned to the Mac from the modem. 

 

In contrast, from a Jetson Nano with Ubuntu Linux OS, using the same command smb://192.168.1.1 in my case, it opens up a challenge window and asks if you wish to use Anonymous Log In or User ID and Password. Choosing the former, connects you directly to the USB drive and files shown. 

Set it & forget it

With direct debit there’s no need to give paying your bill another thought.

Avoid queuing up and never worry about late fees again.

Setup direct debit