Error accessing NAS shares

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Enterprise
       #1

    Error accessing NAS shares


    Hello,

    I have a DLink DNS-323 NAS device and since I have upgraded my laptop to Windows 7 Enterprise 64 bit I have problems accessing shares.

    I am able to map a drive (both manually as via Explorer), but when I try to access the mapped drive I get an error "An unexpected network error occurred". See below an example from the commandline

    This happens in all situations:
    - When a username and password are required for the share. It does not matter whether the username and password are the same as a user on the laptop or a different one
    - When access to the share is open for "ALL"
    - Connecting via wireless and cable
    - Addressing the devide by IP address, hostname and fully qualified hostname.

    From another laptop with Windows XP PRO I still have access like I used to.

    C:\>net use z: \\192.168.100.102\Docs /user:xxxxx
    The command completed successfully.

    C:\>z:
    An unexpected network error occurred.


    Please Help!
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    TomTieDom said:
    Hello,

    I have a DLink DNS-323 NAS device and since I have upgraded my laptop to Windows 7 Enterprise 64 bit I have problems accessing shares.

    I am able to map a drive (both manually as via Explorer), but when I try to access the mapped drive I get an error "An unexpected network error occurred". See below an example from the commandline

    This happens in all situations:
    - When a username and password are required for the share. It does not matter whether the username and password are the same as a user on the laptop or a different one
    - When access to the share is open for "ALL"
    - Connecting via wireless and cable
    - Addressing the devide by IP address, hostname and fully qualified hostname.

    From another laptop with Windows XP PRO I still have access like I used to.

    C:\>net use z: \\192.168.100.102\Docs /user:xxxxx
    The command completed successfully.

    C:\>z:
    An unexpected network error occurred.


    Please Help!

    I suspect you are using "homegroup" for your networking. Homegroup is for win 7 only networks. Since yoou have XP on the network youo should be using "workgroup" for networking. there is a tutorial for leaving homegroup here. Homegroup - Leave


    ken
      My Computer


  3. Posts : 7
    Windows 7 Enterprise
    Thread Starter
       #3

    I'm not part of a homegroup: "There is currently no homegroup on your network. Because this computer belongs to a domain, you can't create your own homeegroup"
      My Computer


  4. Posts : 1,426
    7 Pro
       #4

    try disabling ipv6
      My Computer


  5. Posts : 7
    Windows 7 Enterprise
    Thread Starter
       #5

    I have now disabled IPv6, but still the same problem

    What puzzles me is the fact that I am able to map the drive, so there is no problem with the credentials, but when I try to access the drive it gives a network error. Every once in a while it says something about a remote procedure call that did not succeed.
    Last edited by TomTieDom; 06 Feb 2010 at 06:44.
      My Computer


  6. Posts : 7
    Windows 7 Enterprise
    Thread Starter
       #6

    I have made a network dump with Wireshark. I am not an SMB expert so I don't know if the below is normal behaviour.

    Can somebody help me?

    1. I map the directory \\NAS\DIR on drive letter Z:\
    2. Win7 does a Session Setup twice
    3. Win7 tries to open \desktop.ini. The NAS says it does not exist
    4. Win7 tries to open '\'. The NAS opens it and says it's a directory.
    5. Win7 does a Session Setup four times
    6. Win7 gives the error "Z:\ is not accessible - An unexpected network error occurred."

    No. Time Source Destination Protocol Info
    32 14.963008 192.168.100.146 192.168.100.102 SMB Negotiate Protocol Request
    33 14.977313 192.168.100.102 192.168.100.146 TCP microsoft-ds > 49568 [ACK] Seq=1 Ack=160 Win=6432 Len=0
    34 14.983507 192.168.100.102 192.168.100.146 SMB Negotiate Protocol Response
    35 15.183500 192.168.100.146 192.168.100.102 TCP 49568 > microsoft-ds [ACK] Seq=160 Ack=96 Win=17425 Len=0
    43 22.724227 192.168.100.146 192.168.100.102 SMB Session Setup AndX Request, User: DOMAIN\user; Tree Connect AndX, Path: \\NAS\DIR
    44 22.755653 192.168.100.102 192.168.100.146 SMB Session Setup AndX Response; Tree Connect AndX
    45 22.954996 192.168.100.146 192.168.100.102 TCP 49568 > microsoft-ds [ACK] Seq=368 Ack=214 Win=17307 Len=0
    46 23.255229 192.168.100.146 192.168.100.102 SMB Session Setup AndX Request, User: DOMAIN\user
    48 23.267427 192.168.100.102 192.168.100.146 SMB Session Setup AndX Response
    49 23.270984 192.168.100.146 192.168.100.102 SMB Session Setup AndX Request, User: DOMAIN\user
    50 23.277999 192.168.100.102 192.168.100.146 SMB Session Setup AndX Response
    51 23.476956 192.168.100.146 192.168.100.102 TCP 49568 > microsoft-ds [ACK] Seq=568 Ack=406 Win=17115 Len=0
    52 23.591795 192.168.100.146 192.168.100.102 SMB Session Setup AndX Request, User: DOMAIN\user
    53 23.602934 192.168.100.102 192.168.100.146 SMB Session Setup AndX Response
    54 23.603464 192.168.100.146 192.168.100.102 SMB NT Create AndX Request, Path: \desktop.ini
    55 23.617925 192.168.100.102 192.168.100.146 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_OBJECT_NAME_NOT_FOUND
    56 23.620749 192.168.100.146 192.168.100.102 SMB Session Setup AndX Request, User: DOMAIN\user
    57 23.645069 192.168.100.102 192.168.100.146 SMB Session Setup AndX Response
    58 23.645242 192.168.100.146 192.168.100.102 SMB NT Create AndX Request, FID: 0x12a6, Path: \
    59 23.647636 192.168.100.102 192.168.100.146 SMB NT Create AndX Response, FID: 0x12a6
    60 23.651410 192.168.100.146 192.168.100.102 SMB Session Setup AndX Request, User: DOMAIN\user
    61 23.677782 192.168.100.102 192.168.100.146 SMB Session Setup AndX Response
    62 23.845908 192.168.100.146 192.168.100.102 SMB Session Setup AndX Request, User: DOMAIN\user
    63 23.855544 192.168.100.102 192.168.100.146 SMB Session Setup AndX Response
    64 23.864421 192.168.100.146 192.168.100.102 SMB Session Setup AndX Request, User: DOMAIN\user
    65 23.873746 192.168.100.102 192.168.100.146 SMB Session Setup AndX Response
    66 23.876494 192.168.100.146 192.168.100.102 SMB Session Setup AndX Request, User: DOMAIN\user
    67 23.891579 192.168.100.102 192.168.100.146 SMB Session Setup AndX Response
    68 24.092971 192.168.100.146 192.168.100.102 TCP 49568 > microsoft-ds [ACK] Seq=1374 Ack=1128 Win=16393 Len=0
      My Computer


  7. Posts : 17
    Windows 7 Ultimate
       #7

    There is an apparant error with Windows 7. I opened a request with microsoft professional Help some weeks ago on this subject and they have been delving into my machine remotely to try and resolve the problem. I have three PC's on my home network. One using Windows XP, one with Vista and one with Windows 7. The XP and Vista macj=hine can both access my NAS either by mapping or from the network ico. Windows 7 will only access the NAS as a mapped drive.

    Microsoft have made network traces from my Visat and Win 7 machines and advise that Win 7 sends the correct signals to the NAS but onlt get errors back. The same apparantly happens with the Vista machine but Vista ignores the errors and access the drive. I have tried unsuccessfully to obtain new firmware for the NAS and am waiting to see if Microsoft have any ideas. There are evidently more Security and Permissions additions in Win 7 over and above Vista. I suggest these are the problem.

    It may be that we have to stick with the mapped drive route if MS do not offer any add ons.
      My Computer


  8. Posts : 7
    Windows 7 Enterprise
    Thread Starter
       #8

    spamnchips said:
    Microsoft have made network traces from my Visat and Win 7 machines and advise that Win 7 sends the correct signals to the NAS but onlt get errors back. The same apparantly happens with the Vista machine but Vista ignores the errors and access the drive. I have tried unsuccessfully to obtain new firmware for the NAS and am waiting to see if Microsoft have any ideas. There are evidently more Security and Permissions additions in Win 7 over and above Vista. I suggest these are the problem.

    It may be that we have to stick with the mapped drive route if MS do not offer any add ons.
    Thanks for your reaction. I still have not solved my problem and the mapped drive workaround does not work either. Please keep me posted from any progress you make with Microsoft. I am also willing to provide them with my network traces.
      My Computer


  9. aem
    Posts : 2,698
    Windows 7 Ultimate 64Bit
       #9

    Instead of mapping via command line. Can you go to start > type in the search box \\192.168.100.102\Docs and hit enter. See if it works.
      My Computer


  10. Posts : 7
    Windows 7 Enterprise
    Thread Starter
       #10

    No, but I get a different errormessage:
    "\\192.168.100.102\Docs" is not accessible. You might not have permission to use this network resource. Contact the network administrator of this server to find out if you have access permissions. - The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you."

    All shares on the NAS are open is open for ALL.

    I find the last part of this error message strange: "Please ensure that you can contact the server that authenticated you." Which server has authenticated me?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:45.
Find Us