Print

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

[Sambuccashake]

Hi!

I've been using the NAS with XBMC and other media extenders and I've never had any issues
with connectivity. All users inside my network can access my volumes and read/write.

All of a sudden, XBMC have started acting up at the most odd times.
Playback stops and I'm brought back to where I selected my media file, upon resuming, XBMC can't find the file any more. If I scan the library and retry, THEN it picks up and just carry on.

This can happen at any time, 1 hour into a movie, after a few minutes, or maybe not at all!

When looking in the NAS log, I see the following:
"CIFS: Authentication for user [Media] has FAILED"

What's up with that, my NAS is wide open for all users in my network!
And remember, it NEVER denies access when I access the media file initially. It's always after quite some time.

And while this happens, I can access the shares and whatnot with the laptop and so on so it's definitely isolated to the client. (My HTPC)

The one thing that is new in the equation is that the HTPC is connecting via WiFi.
I have no clue why this should play a part of anything but I'd thought I'd mention it since I
think the issues started then.
(And no, it's not a connectivity issue between HTPC --> Router)

Running the 2.00 firmware

Anyone got a clue here?

Thanks in advance!

[shabuboy]

I know you said it is not "HTPC --> Router" but that is where I would start. The error on the NAS could be due to a timeout error from the HTPC. Video packets are a lot more sensitive than regular data packages, so you might never see those drops, since they can recover. Same goes for voice, very sensitive.

I would imaging HTPC is saturating its wi-fi connection, only way to tell for sure? Put it back on the patch cable. disable wi-fi and test.

But if you have no other issues with the NAS at the same time and only from the HTPC, it sounds as the HTPC might not have a lot of system resources to deal with it, that could be from RAM, CPU, wi-fi, etc.

[Sambuccashake]

Thanks for your input!

[didn't work]After starting this topic I went into the network settings on the NAS and disabled some "power saving" options on the WiFi circuit itself[/didn't work] because it "feels" like the WiFi connection somehow goes into hibernation and wakes up when I refresh XBMC.

But then again, the error message in the NAS is throwing me off that track so it's still somewhat trial and error at this point.

Do you really think it would throw that kind of error when it comes to a time out?

[shabuboy]

 

Did you mean to say "network settings on the NAS and disabled some "power saving" options on the WiFi circuit itself"?

The DNS-320 does not have a wifi nic. At least my does not.

But as I said, before playing around with settings I would test it without the wifi, as previously setup and go from there.

But yes, hard to tell what errors at what devices a timeout error would log. Unless a TCP capture is set.

[Sambuccashake]

No no, my HTPC's WiFi settings. (And it didn't work)

[Sambuccashake]

I've been using a ethernet cable for a few days and I can't remember running into any problems.
But why would streaming over wireless be so picky and result in these kind of issues?

I've got bandwidth to spare (usually max 720p vid and the router is very very close) and I've never noticed any problems before this.

It's a D-link DIR-655 router by the way.

[shabuboy]

Video and voice packets cannot compare to data. They are just picky, nothing to do with wifi.

However, you might also have an issue with wifi, but that would be between the router and the client. Interference might be an issue, or wifi signals on same channel, or drivers, or router firmware, etc. Hard to tell.