Network drive

irhut · 03-23-09, 04:57 PM

Hello all,

I have a problem that is driving me mad! I bought a ATMT HD363N External Network Hard Drive which has been working really well. I am able to access using my laptop and main PC. I then installed the network folder plugin on my axim x50v so that I could map the drive to my axim.

The first time I did this it worked perfectly and I was able to map the folder with all my music in. Fantastic!

The next day I switched my axim on and the mapped drive was gone. So I tried to map it again but i hit a problem. Although the plugin finds my drive (Called disk) it will not display any of the sub folders below it.

The attached picture shows what I mean. Notice how I can see all the shred drives on my main PC, but I am unable to see the same thing under Disk. This did work the first time - but it no longer does.

I have installed the network folder plugin again, I have reinstalled WM6. I have updated the firmware on the network drive.

I have even tried using Resco Explorer to do the same thing, but I get the same result. I just can't get the shared folders to show. It is driving me mad because it did work!

Sorry for long post. Any help would be much appreciated.

Ian Hutton

Box · 03-23-09, 07:03 PM

One thought, It might be a firewall issue.

**breley** · 03-23-09, 07:58 PM

It almost looks like a file/drive permission issue, as though the Axim is not "allowed" to view the folder contents.

irhut · 03-24-09, 05:53 PM

I don't think it is a firewall thing as Laptop can connect without any problems. Also it did work once!
I can't think why the Axim would not be allowed to connect. There are certainly no settings on the network drive that I can change.

Thanks for the help so far. Really not sure what to try now.

Ian

**breley** · 03-25-09, 07:53 AM

There should be settings that you can change for the network enclosure...namely whether it uses DHCP or static IP. It's possible there is an IP conflict. For that unit it should have some means of direct access control, like http://storage . I've found it's manual here...

Hopefully the drive isn't trying to act as the network DHCP server and conflicting with another DHCP server, or that its IP lease is up and got assigned to another network device. You might want to check and see if all your network devices have unique IP addresses and also that the network drive doesn't have one starting with 169.254.0.x...

irhut · 03-26-09, 02:32 PM

Originally Posted by breley

There should be settings that you can change for the network enclosure...namely whether it uses DHCP or static IP. It's possible there is an IP conflict. For that unit it should have some means of direct access control.

Hopefully the drive isn't trying to act as the network DHCP server and conflicting with another DHCP server, or that its IP lease is up and got assigned to another network device. You might want to check and see if all your network devices have unique IP addresses and also that the network drive doesn't have one starting with 169.254.0.x...

Thanks for the above.

I have it set to a fixed IP address 192.168.1.100
subnet mask - 255.255.255.0
gateway - is the ip address for my wireless router

There are settings for DHCPS which is set to DISABLE. I am able to connect to the drive from both my main PC and my laptop.

I trhink I am just going to have to give up! It is driving me mad!

Ian

**breley** · 03-31-09, 10:07 AM

Hm, so the unit has a FIXED IP address...does your PC and laptop also have fixed IPs or do they use DHCP? The reason I ask is that the DHCP server on your router or whatever just doles out IP addresses, often starting at 192.168.x.100 (frequent defaults for many router manufacturers, but not always true). So, if you have the drive set to x.x.x.100 but the range of DHCP addresses is x.x.x.100 to some other number, that means the router and other network devices might behave oddly when trying to enumerate the network device x.x.x.100 since dhcp addresses are usually awarded sequentially from high to low. Just for kicks change the ip address of the drive to something like x.x.x.200 or some such, perhaps reboot the router to err on the side of caution, then reboot your pc and laptop and see what happens.