• November 01, 2024, 11:23:36 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Can't reconnect to DNS-320L after firmware update  (Read 4351 times)

guile42

  • Level 1 Member
  • *
  • Posts: 2
Can't reconnect to DNS-320L after firmware update
« on: July 29, 2016, 10:26:17 PM »

I'm afraid I made a grave mistake in updating the firmware to 1.08. My second mistake was not saving the configuration settings before updating the firmware.

Immediately after it rebooted after the firmware update, I was unable to access the mapped drive on Windows 10. The other computer in the house is Windows 7 and it's still able to access just fine.

I've tried all of the following:

1. Removing the mapped drive and re-mapping it. It keeps asking for credentials. When I enter the admin username and password it says "Access is denied." I know the password is correct because I can log into the web interface with it. The message in the log is "CIFS: Authentication for user [admin] has FAILED."

2. I tried creating and entering a different username and password and get this message:

\\DLINK-AEAEC8\Volume_1 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

There is no message in the log when I try to use the different username.

3. Tried downgrading the firmware back to 1.03. Still can't connect, still get all the same error messages.

4. Tried using the "D-Link Storage Utility" to map the drive. Get the error message "Failed to map drive."

5. Tried using the "DNS-320L Setup Wizard" on the off chance it might reset something. It gets stuck at the "Configure Device LAN" screen. Clicking "Next" does nothing - the button turns grey for a couple of minutes then turns white again without moving to the next screen. The log shows it spends two minutes modifying the admin password

6. I even tried going into the Credential Manager and removing and re-adding the Windows credentials. Still says "Access is denied."

7. Finally, reset the unit to factory default. Tried using the Setup Wizard again, it was able to set the administrator password but that's it. Logged in to finish setup through web UI. Still get the same "Access is denied" message when trying to map the network drive. Tried reloading the configuration settings I saved before resetting to factory default and still no dice.

Sorry that's so long but I wanted to cover everything I've tried. Can somebody, anybody please help?
Logged

ivan

  • Level 8 Member
  • ***
  • Posts: 1480
Re: Can't reconnect to DNS-320L after firmware update
« Reply #1 on: July 30, 2016, 03:35:51 AM »

It sounds as if you are trying to use the admin/password combination that is only used to access the webUI to access the shares.

There is NO WAY that the webUI password can be used to access drive shares.

I assume you have setup a user with a password that has access to some folders via SMB/CIFS.  This is the username and password you should be using to access and map the drive/folders.
Logged

guile42

  • Level 1 Member
  • *
  • Posts: 2
Re: Can't reconnect to DNS-320L after firmware update
« Reply #2 on: July 30, 2016, 07:09:17 AM »

Hi,

I've been using the webUI password to access the shares all along, up until now, and it's been fine.

I've created a user with read/write access to the entire Volume_1 share. When I try to map the network drive I get the message:

\\DLINK-AEAEC8\Volume_1 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

Logged