Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gunrunnerjohn]

With a wired connection, boot in Safe Mode with Networking and see if that changes anything.

[TomTieDom]

Doesn't change anything. Same error message.

[Buhric]

Are you by any change using the same drive letters when mapping you office shares and Home shares ?
If so try changing letter....

Also try setting the workgroup field in the DNS to the same name as your Office Domain name...

[TomTieDom]

Thanks for the suggestion, but still the same result.

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.

I am getting desperate ...

[Buhric]

Try checking your event log... it might contain more explanation on what is failing when you try to access the network drive...

And theres actually a service in Windows called "Remote Procedure Call (RPC)" that should be set to start Automatic...
And leave the "Remote Procedure Call (RPC) Locator" service set to Manual

[TomTieDom]

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

[gunrunnerjohn]

This is not a typical issue with the DNS-323, that's for sure.

On the Advanced tab under Network Access, you have SMB selected, do you have any user accounts established, or are you running with only anonymous shares?  Can you ping the DNS-323 with the network name from the Setup, Device menu?

[mesostinky]

Things I would try..

I know you said you disabled the windows firewall. If your using either the Norton or Mcafee internet security suites uninstall them completely.

Reset the DNS-323 completely to 100% factory specs with brand new shares and usernames. Put in a brand new formatted temp HD while doing this.

Make another account on your windows machine and try connecting using that instead of the one you are currently using.

Boot off of a live cd like UBC4Win(preferably) or a linux live cd and try connecting to the share(s) then. Then at least you'll know if its your Windows install.

Good luck.

[TomTieDom]

@gunrunnerjohn
I have reset the device to factory settings. I have created no new users so admin is the only user known on the device. I have created 2 anonymous SMB shares ("All accounts").

The problem still occurs: From Win7 I can map a share using the Easy_Search utility and also directly in Explorer. They appear in Explorer as connected drives. When I try to access the mapped drives I still get the error "An unexpected network error occurred".

I can ping the device using the name in the Setup -> Device menu.

[TomTieDom]

@mesostinky
I have reset the device to factory settings as above.

Your suggestions will take me a little longer. I am pretty sure it is the combination of the new Win7 install and the DNS-323. It all worked with the previous WinXP install on my laptop and currently still does on another XP laptop.

[gunrunnerjohn]

Don't create any accounts, just leave the NAS "wide open".

[Emman]

Try this....

Control Panel - Administrative Tools - Local Security Policy

Local Policies - Security Options



Network security: LAN Manager authentication level
Send LM & NTLM responses

Minimum session security for NTLM SSP
Disable Require 128-bit encryption


This is a known fact between linux and windows. The fixed I mentioned above has been tested with Windows 7 Pro and Ultimate and both works. Goodluck!

[gunrunnerjohn]

This was also fixed in most recent editions of SAMBA.  Since I've never seen this with either the DNS-321 or DNS-323 and three different Windows 7 installation, I have to believe this isn't the reason for this issue. I also have a friend with a DNS-323 and Windows 7, he has no issues connecting to his NAS either.

[Buhric]

Me two.. I have Windows 7 64bit Rc1 and Windows 7 32bit both ultimate on 2 different computers
and neither has issues access the DNS-323

[TomTieDom]

Try this....

Network security: LAN Manager authentication level
Send LM & NTLM responses

Minimum session security for NTLM SSP
Disable Require 128-bit encryption

Tried this and it made no difference, unfortunately.