Print

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

[Phane]

The DNS-320 is accessible as a mapped network drive or by manually connecting to it by typing \\NAME into explorer, but it's invisible when I try to browse for it on my Network using a Windows 7 computer.

I've tried all manners of troubleshooting this issue.  I've tried the 2.00, 2.01b and 2.02b firmwares and all of them have this issue.  The NAS shows up under "Network" in Windows 7 *sometimes* but not all of the time.  There doesn't seem to be any rhyme or reason as to when it works or doesn't.  Sometimes it works when I have another SMB device on the network (a linux client with Samba installed connects or activating Samba in DD-WRT on my Linksys E-3000).  If I get it to work this way, as soon as I disconnect the other SMB device, the DNS-320 disappears again.

Sometimes one computer can see it while another can't, other times none see it.  ipconfig /release and ipconfig /renew can fix it occasionally.  Sometimes I have to completely shutdown and incrementally restart my whole network from the cable modem up.  Whenever I manage to get it to work, it'll continue working indefinitely until I eventually power it completely down (restarting through the web interface doesn't seem to break it).  At that point, I sometimes have to restart my whole network several times to get it to function properly.

I've tried it with LLTD enabled and disabled, DHCP and static IP, the Workgroup is correct.  I've tried different ethernet patch cords and different wall ports as well as different ports directly into the switch.

Network config is Cable Modem <-> Ooma Hub <-> IP Fire 2.9 core 51 <-> Netgear gigabit switch <-> Other computers, DNS-320, Linksys E-3000 (running DD-WRT).  I've tried it with and without the E-3000 powered on, it has no impact unless I turn on Samba to use the SMB client trick.

Calling Linksys phone support was less than useless.

[airprox]

This is of no use to you from a troubleshooting point of view, but I'm running a couple of Win 7 PC's (one 64bit the other 32bit) and have no issue with this.  Shares are always available.  I use a BT Home Hub Router > Asus Gigabit switch > DNS 320, PC's, WDTV Live etc.  and I'm running FW 2.00

Cheers
Al

[Phane]

What are your Advanced sharing settings on those computers?  I think what I have should be working but I've been playing musical chairs with the settings that it's possible I may have configured something wrong.  I have:

Network Discovery: On
File and Printer Sharing: On
Public folder sharing: On
Media streaming: Off
File sharing connections: Use 128 bit
Password protected sharing: Off
Homegroup connections: Allow windows to manage

If any of your PC's are running Linux with Samba installed, that could be why it's working.  The WDTV Live has the ability to browse samba shares, so it may or may not also be fixing the issue for your.  The BT Home Hub Router also seems to have an undocumented feature for hosting a USB drive over the network, so it might have Samba as well.  If any of those devices show up when you browse to your network, they might be why yours is working.  I've left my E-3000 running an empty samba share as a quick fix on my end.

I also left out a few other devices that might impact it.  I have a Logitech Revue and a Tivo HD also connected to the network through the switch that are always on.  I suppose I'll try disconnecting those from the network and see if one resolves the issue.

Edit: I disconnected the Revue and Tivo HD as well as everything else so that my switch was completely dark.  I booted Cable modem -> Ooma -> IP Fire -> DNS-320 and then booted up one computer, which saw it after the second refresh on network.  I then shut that computer down, went upstairs to another computer and it won't see the DNS-320 no matter how many times I refresh.  The Ooma and Cable modem are both firewalled from the DNS-320 and I have no ports forwarded to it.  I have no other devices with active connections to my switch except for the DNS-320 and the computer I am trying to use to access it.  I shut down the computer that first saw it from the power strip before booting the second one.

[airprox]

The only difference to the advanced settings is the Media Streaming, mine is switched on (not entirely sure why, I'm sure there was a good reason at the time!).  The WDTV could have something to do with it, but it's powered off overnight and for most of the day (not just standby, but off at the mains). 

As for the HH, I have used it in the past to network a USB drive (long time ago)... can't think of a way to test that without disabling the network in the process.  Actually, just checked under the network map and there are indeed 2 entries for the HH, one as "network infrastructure" the other as "other devices", that last one leads me to believe it's as you say, there is some sort of share been seen there.

Sorry I couldn't just say "aha! you've got that setting wrong", looks like there may be something going on within the firmware... maybe your quick fix will have to become a permanent one?

Cheers
Al

[Phane]

I believe I found at least one problem.  There seems to be an incompatibility between the DNS-320 and Oracle's "Virtualbox Bridged Networking Driver", even when Virtualbox isn't running.  Uninstalling this driver from the Local Area Connection Properties window resolved the issue (for now).  I have none of this trouble with other samba devices which leads me to believe that this compatibility issue is unique to the DNS-320's samba implementation.  It worked sometimes and not others, as well.  For now, it seems to be working on all computers and Windows doesn't spend anywhere near as much time looking.

I'll post again in this thread if my DNS-320 drops out again.

[t121anf]

only running windows 7 pro here and mine is always listed in network.  (also using a linksys router)

[Phane]

Update: Ever since uninstalling Virtualbox, all has been well.  I reinstalled Virtualbox to play with the Windows 8 developer preview and the issue returned.  Uninstalling it again fixed the issue.  So my issue was most likely a compatibility issue with Virtualbox, more specifically the bridged driver I mentioned in the above post.

[visor66]

i experienced the same thing when I'm trying to access the dns320 on my sons computer, under his user account (no admin rights).  I found out that when trying to connect to the 320, it sometimes will not discover the nas. However, when I login on the same computer with admin rights I can connect to the 320.