Unable to Map NAS Drive on Windows 7 Ultimate
-
dimanche 29 avril 2012 20:30
I have a D-Link DNS-321 Media Hub (NAS) which my Windows 7 Ultimate Workstation refuses to map to. I have a Vista workstation and the D-Link Easy Search software maps a drive just fine to, but again, not to the Windows 7 machine. I can access the setup/sign on screen by typing the IP address of the NAS through the Windows 7 machine as well as "ping" the IP address also.
I have tried contacting D-Link and they have thus far been unable to help. I am also using the latest releases of the D-Link Easy Search Utility. They have mentioned that it has to do with Windows 7. I have also tried the modification of the Local Policy as suggested in this forum as well, without any luck.
Any suggestions would be greatly appreciated.
MEtten59
Toutes les réponses
-
lundi 30 avril 2012 07:08
Test it first with firewall disabled. Chances are that needed port is blocked.
Alternative to this is analysis with network monitor which would reveal the possible bloccking
Regards
Milos
-
lundi 30 avril 2012 15:20
Hi Milos,
Yes, I have tested with the Firewall off and I am still unable to map the drive. Thank you though.
MEtten59
-
lundi 30 avril 2012 19:31
What is the name of your dlink on the network? For instance, mine is dlinkmedia. Try browsing too \\dlinkmedia\ and see if that helps. If that works, right click the folder you want and then map the network drive.
Wesley
-
lundi 30 avril 2012 20:57
Hi Wesley,
Thanks for the idea. I tried using the Internet Browser to locate by typing \\MediaHub\ but no luck. : (
MEtten1959
-
lundi 30 avril 2012 21:16What is the IP address of your system and that of the NAS? Are you both on the same subnet?
Wesley
-
lundi 30 avril 2012 23:15
The IP Address of the Windows 7 workstation is 192.168.1.1 and the NAS is 192.168.1.6. Both are managed by DHCP with the same subnet mask.
MEtten59
-
mardi 1 mai 2012 08:04Have you tried changing your IP address? I know, its seems odd, but I have had stranger things happen.
Wesley
-
mardi 1 mai 2012 17:41
Hi Wesley,
Yes, just tried both turning off the DHCP on the NAS as well as manually changing the IP and both attempts proved unsuccessful. Thanks though !
MEtten59
-
mardi 1 mai 2012 21:57
HI MEtten59,
Try this,
Go to TCP/IP properties, Advanced section, DNS Tab, Here should be tick following
1) Append primary and connection specific DNS suffix
2)Append parent suffix of primary DNS Suffix
3)Register this connection addresses in DNS
4)Use this connection in DNS suffix in DNS registration
-Or-
1)Append this DNS suffix in order and add your Domain name
2)Register this connection addresses in DNS
3)Use this connection in DNS suffix in DNS registration
Try to flush DNS
Please tell me you are to connectivity like ping from Windows 7 machine to any another PC in the same network.
Rakesh Kumar
-
mercredi 2 mai 2012 02:21Modérateur
Hi,
What is the error message? If you have subfolder on the device, please try to map \\192.168.1.6\share for a test.
Meanwhile, you can use a command net use Z: \\192.168.1.6\Share. You will get an error number if it fails. Please let me know the error.
Niki Han
TechNet Community Support
-
mercredi 2 mai 2012 15:48
Hi Rakesh,
I am aware of how to do what you are speaking on, however, I will first mention I do not use a Domain Name in my network. It is just a Home Network where it was given the name of Network. So I am uncertain as to what exactly I would be appending and registering. I do not believe I have a DNS suffix as referred to.
MEtten59
-
mercredi 2 mai 2012 15:56
Hi Niki,
Mapping Results - Suggestion 1
When I tried to map the Z: drive to \\192.168.1.6\share, I receive the dialog box error message of "Windows cannot access \\192.168.1.6\share. The details of the error message provides an error code of 0X800704CF.
Net Use Results - Suggestion 2
When entering net use z:\\192.168.1.6\share, I receive an error message of "System Error 67 has occured". In follow-up, I still am able to type ping 192.168.1.6 and receive a successful acknowledgement.
Thanks Niki !
MEtten59
-
vendredi 4 mai 2012 16:46
Would you try to catch network traffic by network monitor. This would give us more information on processes "behind the scene".
Regards
Milos
-
vendredi 4 mai 2012 17:25
Hi Milos,
Any particular recommended (free) network monitoring software to use that would provide a detailed report?
MEtten59
Addendum: I just downloaded TCPEye Network Monitoring software and tried to map the NAS again using the D-Link Easy Search software and found that I could suddenly connect. Not certain as to why, but something tells me that there must be a component in the TCPEye software (a free utility) that opened the port???
- Modifié MEtten59 vendredi 4 mai 2012 17:41 Addendum
-
samedi 5 mai 2012 05:24
Hello MEtten59
1. "Native" Microsoft network monitor gives detailed information. From open source there is widely used Wireshark.
2. I have not used TCPEye. The only possible reason may be promiscuous mode, or perhaps the cleaning cache.
3. "Clean" solution stem from using "independent" computer and network hub instead of switch. With hub you can listen on subnet, while "switched" solution mean point to point communication.
4. Whenever I change any configuration in IP (DNS) or in name resolution, I issue cleaning with ipconfig and-or ntbstat. This is the prerequisite for successful troubleshooting to start from "zero".
Regards
Milos
- Modifié Milos PuchtaMicrosoft Community Contributor samedi 5 mai 2012 18:20
- Marqué comme réponse Niki HanMicrosoft Contingent Staff, Moderator jeudi 17 mai 2012 07:55
-
lundi 14 mai 2012 19:11
- Open gpedit.msc from from Start | Run
- From Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options
- Locate the Network Security: LAN Manager Authentication level
- Change value to "Send LM & NTLM - use NTLMv2 session security if negotiated (see screenshot)
This should resolve your issue...
Debonairone
- Marqué comme réponse Niki HanMicrosoft Contingent Staff, Moderator jeudi 17 mai 2012 07:55
.png)
