[ShokwaveRider]

I have been using my HD-7000 for some time with a Smartstor NS4300N NAS 4tb Mirrored to 2Tb. I am experienceing a few anomolies and wonder if there are similar stories and perhaps by some fluke of chance a solution.

The main issue I have is that when the NAS is on and has been communicating fine with PCs in the network, 99% of the time when the TViX is set to read it, nothing appears and it cannot read the NAS. No matter how many times I try.

It can read it's internal OK, it can read it's USB OK, it can ping the NAS OK, just cannot read the directories as set.

The only way I can fix this is terminate all communication from the other PCs, Turn off the Nas, Turn off the HD-7000. Then power up the 7000. When Boot and loading are complete start the Nas, when the Nas comes on line then it works OK. Usually.

Any Ideas?

SWR

[Hi-Jack]

If an empty dir shows it often means access rights for public / guest account is not allowed. However if you can reach it in the way you describe, it shows it can... Kind of puzzling me how this can happen...

Can you try using a user account on the TViX to make the connection? I'm pretty sure it has some deeper meaning in access rights...

[ShokwaveRider]

Originally Posted by Hi-Jack If an empty dir shows it often means access rights for public / guest account is not allowed. However if you can reach it in the way you describe, it shows it can... Kind of puzzling me how this can happen... Can you try using a user account on the TViX to make the connection? I'm pretty sure it has some deeper meaning in access rights...

HiJack:

As usual thanks for the insight. I am not sure I understand your suggested test. Currently I am using the NAS IP security to gain access. I have hard IPs on both the NAS and the TVix.

Not sure what you mean by setting up a user account??

From the PC. I just use Windows obviously to got to //nas and bam it gets there, all subs have access and are visible, they use a user account as normal.

From the TVix I use the menus. (Video, audio, Photo) The TViX knows it is there cause of the ping 5 of 5 OK. When I select say Video, it shows the path of the NAS Master directory //Volume1/MediaMaster/ at the bottom of the page, but never shows the dirs under it. (Unless I go through the sequence mentioned) I have set up all 4 available NFS ports on the TViX to the same but on 2 I have omitted the trailing "/" which frankly does not make a difference either way.

Both are connected directly to a LinkSys GigaBit switch on adjacent ports (1&2). Under the MediaMaster directory on the Nas I have 3 other directories, Video, Audio & Photo + the default recycler etc.

SWR

[TurningFrench]

When you shut down all equipment and restart things in a specific order, ensuring stuff works again, this is very symptomatic of equipment startup order throwing a spanner in the works.

Static IP addresses on the network or assigned by DHCP?

If static, check that two devices have not been allocated the same IP address (by you).

If DHCP, you'll have to check in your router settings that there isn't a dependancy on the order you start up your equipment. Some routers have the facility to bind an IP address to a MAC address, so the router will perform static address handling for you. Check this out and if it exists, use it. Other routers just assign an IP address on a first come first served basis. This might explain your predicament, since although you can ping the IP address set in the TViX, what are you pinging exactly? The NAS, or some other piece of equipment? A correct ping does not mean a correct setup, it simply means that the address you pinged is in use by something that answered. Also check out the lease time that your router uses. The lease time controls the interval after which the router will drop an IP address and reallocate. If your lease time is low, extend it, to say 1 month. Then restart all equipment in your specific order required to get correct operation. At least then you'll have a month without problems.

Don't give up, lots of people here will help.

[ShokwaveRider]

TurningFrench:

Thanks for the input, I think I have all the items you suggested addressed. See prevous post.

SWR

[desray]

I am using the same set-up as you...but I have no problem at all. Enjoying from day 1...

If you can't see the directory - its because you never add in the IP address of your TViX into NS4300N NAS.

[ShokwaveRider]

I think I have solved the problem. Not sure but it worked today. I set the DviCO to point at a subdirectory of the Nas rather than the top level. for example, //NAS/Video as opposed to //NAS/ or //NAS it does not seem to have an issue with this.

Video goes to Video and Phot to Photo and Audio to Audio etc. I use each of the 4 setting to go to the one I want. A little extra stuff to do but it "seems" to work.

Oh for some updated Firmware....

SWR

[ShokwaveRider]

Originally Posted by ShokwaveRider I think I have solved the problem. Not sure but it worked today. I set the DviCO to point at a subdirectory of the Nas rather than the top level. for example, //NAS/Video as opposed to //NAS/ or //NAS it does not seem to have an issue with this. Video goes to Video and Phot to Photo and Audio to Audio etc. I use each of the 4 setting to go to the one I want. A little extra stuff to do but it "seems" to work. SWR

I spoke too soon! Still get the problem. Have to shut off both units fire up the 7000 and then the nas.

SWR

[ShokwaveRider]

Even with the New FirmWare from Promise and Divco I still get intermittent connection issues to the NAS.

It works only when it is powered up in a certain sequence that seems to change depending on the phase of the moon and where Jupiter is aligned, along with a certain time on Wednesday afternoon....

But when it works it is great....

SWR

[theles92843]

Hi ShockwaveRider, i think I have same setup and issue with you. My NAS is a HP MediaSmart Home Server. My question is the path should be
\\HPSERVER\VIDEO
\\HPSERVER\PHOTO
etc.
in my case (and something similar in yours) yet I couldnt find the backward slash sign (\) on the remote! Pressing #1 would give forward slash (/), which was the one you seemed to be using.

Is it correct? So they are the same? You mentioned connection worked intdiesermitenly in your case. Does it still? Thanks!