Closed IsaacKieffer closed 5 years ago
Any help??
Hi Isaac. Sorry for the delay.
Were you using back or forward slashes? It should look like this...
\servername\files or \123.123.123.123\files
Notice the \ not the /.
If you are still have trouble do the following to get the log.
1) Go to chrome://extensions in your browser 2) Scroll down until you see "Network File Share for Chrome OS" 3) Click on "plugin.html" 4) Select the "console" tab 5) Copy and paste the errors from the log.
Thanks!
Thank you so much for getting back to me! I will try that when i get to the office tomorrow!
On Monday, October 10, 2016, Zentaro Kavanagh notifications@github.com wrote:
Hi Isaac. Sorry for the delay.
Were you using back or forward slashes? It should look like this...
\servername\files or \123.123.123.123\files
Notice the \ not the /.
If you are still have trouble do the following to get the log.
1) Go to chrome://extensions in your browser 2) Scroll down until you see "Network File Share for Chrome OS" 3) Click on "plugin.html" 4) Select the "console" tab 5) Copy and paste the errors from the log.
Thanks!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GoogleChrome/chromeos_network_file_share/issues/48#issuecomment-252749298, or mute the thread https://github.com/notifications/unsubscribe-auth/AVo4E1qPWqxHf1yE-99nT037_xxytjqLks5qyqwIgaJpZM4KRcia .
I kept getting errors mounting the share until I tried the IP address of the window computer.
Using the plugin.html mentioned above by Isaac, and the mount.html links in the logs at chrome://extensions/ I saw that it could not resolve the windows computer name,
Then I checked under settings under my wifi connection, under Network and NamesServers and saw that the Chromebook was not using my router as a DNS server (apparently it defaults to Google DNS servers), so changed the first of the two values to match the gateway IP value, which I knew was my router IP, and then I was able to remove the mount and re-add it using the windows computer name instead of the IP address. It seems to be a bit slow, but it works.
I keep receiving the following errors in the log: NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 60 SHOULD_RETRY log.js:68 WARNING: mount[60] failed on attempt 1 of 3. Retrying... log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 60 SHOULD_RETRY log.js:68 WARNING: mount[60] failed on attempt 2 of 3. Retrying... log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 60 SHOULD_RETRY log.js:68 ERROR: mount[60] failed on attempt 3 of 3. Retrying... log.js:68 ERROR: Mount with samba failed with FAILED log.js:68 ERROR: Sending err response to popup Anyone could help?
Very similar misbehavior on Synology NAS connection that had mounted sucessfully and worked well 100s of times, fails repeatedly now (Jan 2019): Platform 11316.66.0 (Official Build) dev-channel guado Firmware Google_Guado.6301.108.4 Chrome OS version 72.0.3626.49 using Network File Share for Chrome OS version 0.81.18120 "" In common.js - DOMContentLoaded log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 1 SHOULD_RETRY log.js:68 WARNING: mount[1] failed on attempt 1 of 3. Retrying... log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 1 SHOULD_RETRY log.js:68 WARNING: mount[1] failed on attempt 2 of 3. Retrying... log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 1 SHOULD_RETRY log.js:68 ERROR: mount[1] failed on attempt 3 of 3. Retrying... log.js:68 ERROR: Mount with samba failed with FAILED log.js:68 ERROR: Sending err response to popup log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 2 SHOULD_RETRY log.js:68 WARNING: mount[2] failed on attempt 1 of 3. Retrying... log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 2 SHOULD_RETRY log.js:68 WARNING: mount[2] failed on attempt 2 of 3. Retrying... log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 2 SHOULD_RETRY log.js:68 ERROR: mount[2] failed on attempt 3 of 3. Retrying... log.js:68 ERROR: Mount with samba failed with FAILED log.js:68 ERROR: Sending err response to popup log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 3 SHOULD_RETRY log.js:68 WARNING: mount[3] failed on attempt 1 of 3. Retrying... log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 3 SHOULD_RETRY log.js:68 WARNING: mount[3] failed on attempt 2 of 3. Retrying... log.js:24 NACL ERROR: Error performing mount:smbc_opendir: errno=110 errtxt=Connection timed out log.js:68 ERROR: rejecting message 3 SHOULD_RETRY log.js:68 ERROR: mount[3] failed on attempt 3 of 3. Retrying... log.js:68 ERROR: Mount with samba failed with FAILED log.js:68 ERROR: Sending err response to popup ""
SMB functionality has now been built natively into Chrome OS. On Chrome 71 or higher you can.
1) Open the files app 2) Click the "three dot menu" in the top right 3) Choose "Add New Service" 4) Choose "SMB file share"
A dialog in settings will open (in 72 and later it's a standalone dialog). Enter your share information as before.
You can uninstall the chrome app as it will be deprecated in the near future. The new implementation is an order magnitude or two faster and much more reliable.
If you have bugs with the new implementation you can open them at crbug.com under component "Platform>Apps>FileManager"
FYI there will be no further development on this implementation.
I tried to mount a file for my new job and we were unable to share the mount? It says "share could not be mounted"
We have the username and password correct, with case sensitivity. We also imputed the share bath as stated: "//00.0.00.000/Files" With the correct numbers.
Any help?