• February 26, 2025, 02:56:34 AM
  • 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: odd problem - files inaccessible from one network client  (Read 3495 times)

jjjiii

  • Level 1 Member
  • *
  • Posts: 14
odd problem - files inaccessible from one network client
« on: August 22, 2009, 07:07:04 PM »

I have a home LAN consisting of a router running dd-wrt, a dns-323, and two WinXP systems, one a laptop, the other a desktop tower.

I can connect to \\dns-323\volume_1\ from both systems, and view the files at the root share.  When I connect, I connect using the same authentication credentials, regardless of which system I am connecting from.  In other words, I've set up a single user account on the dns-323, and am using that account from either PC.

On the /volume_1/ share, I have a subdirectory named AV, where I have music and video files stored.  Up until recently, both PC's were able to get into the AV directory without any trouble at all.  But for some reason, I recently lost the ability to browse inside of /Volume_1/AV from the tower PC.  The laptop continues to be able to access the contents of this directory, but for some reason, no matter what I do, I cannot get inside there from the tower PC. 

I've tried everything I can think of; rebooting all boxes, disconnecting/remapping network drives, creating a second user and trying to authenticate as the second user from the tower PC, blowing out the user accounts and share permissions and re-assigning them, connecting to the share via ftp instead of as a samba share, resetting the dns-323 to its factory default settings, and even upgrading the firmware on the dns-323 to 1.08b5, and this problem stubbornly persists. 

Does anyone have any idea what could be causing the problem, and what can I do to fix the issue?
« Last Edit: August 22, 2009, 07:08:37 PM by jjjiii »
Logged

lizzi555

  • Level 5 Member
  • *****
  • Posts: 605
Re: odd problem - files inaccessible from one network client
« Reply #1 on: August 23, 2009, 12:06:17 AM »

As connection laptop <-> DNS-323 works as expected, there seems to be no problem with them.
But if your tower can't connect you should look there what has changed.

New windows updates ?
software firewall updated or you changed some settings ?
newly installed programs ?
network connection to other shares is OK ?

Try to share a folder on your laptop. Can you access it from the tower ?
Logged

jjjiii

  • Level 1 Member
  • *
  • Posts: 14
Re: odd problem - files inaccessible from one network client
« Reply #2 on: August 23, 2009, 07:12:56 PM »

Ah, thanks for your suggestion.  I believe I have figured out part of the problem!

I remembered, things were working fine from both systems... until after I had turned on Jumbo Frames on the Advanced properties of the NIC on my tower.  I just tried disabling Jumbo Frames on the NIC, and as soon as I did that, I regained access to the directory on the DNS-323. 

Oddly, the reason I turned Jumbo Frames on in the first place was that I wanted to see if I could get faster throughput to the DNS-323 -- and I did.  I was getting maybe 3000-4000 kbps with Jumbo Frames disabled, and after turning it on I was seeing anywhere from 7000-12000 kbps.  And, obviously, not getting errors with being able to access the DNS-323 at first.  I backed up around 400GB of files that way, in much less time than it had been taking before I turned Jumbo Frames on.

Since turning the feature off seems to have helped somehow, but turning it on in the first place didn't completely cause it to fail, I wonder what else there is to understand about this in order for it to make sense.

Ideally, I'd like to be able to keep Jumbo Frames enabled, and not have this problem.  The NIC on the Tower is a Realtek 8169/8100 Family Gigabit NIC, and it supports Jumbo Frames up to 7000, so I enabled Jumbo Frames on the DNS-323 and set it to 7000 as well.  Perhaps it will work better at a lower setting... I'll try playing with it.
Logged