Make sure both dip switches on the back of the NETDISK (if any) are in the position (Power off NETDISK completely before doing so). Or, plug NETDISK into a different USB port on your PC. Or try using a different USB cable. With Windows ME/2000/XP and MAC, NETDISK uses the Operating Systems built-in USB drivers, therefore, no software is necessary. If you are using Windows 98SE, please check our website for the latest USB drivers at http://www.iocellnetworks.com. If using Windows98SE/ME, and MAC, make sure that NETDISK is formatted to the supported files system. Windows Me requires FAT32. Mac has its own file system, but also supports FAT32. It is up to you to choose the appropriate one.
When used with USB mode, the software is not needed, therefore you will see a black dot (disconnected) in the system tray as that is an indicator for NETDISK (Ethernet) mode.
We do not recommend doing this, as your computer will be dependent on this location during software installation and removal. You may receive Windows Error Messages looking for a non-existing location.
This is a result of a bad connection between the computer and the NETDISK. Please make sure that you are using only network switches and routers, and that you are not using any network hubs. Also, if you have any software firewalls installed on your computer (i.e. Norton Internet Security, McAfee Personal Firewall, etc.), make sure to add ndasmgmt.exe and ndassvc.exe into their list of programs to Allow with full access. You can also try disabling your Antivirus software to see if that makes a difference. Please also try power cycling your NETDISK and switch as well.
The error codes are not actually specific codes, but simply indications that the NDAS driver has malfunctioned at some point. Now and then the same error code appears for different problems. You can see a list of Known Error Codes in the support knowledge base.
Please look at the services on your computer and see if you can start it manually, restart it or even set it to automatic so that NETDISKsvc.exe will run when the computer boots up.
Windows XP: click the start button, choose Run, then type services.msc in the box and click OK.
Vista or Win7: Click the start button, then type services.msc in the search box and hit enter. Find the NETDISK Service, right click and choose Start.
Try unplugging your NETDISK’s power cord, wait about 10 seconds, and plug it back in. If this does not work, restart your computer. Please disable your firewall/antivirus software (you may need to configure the software to allow your NETDISK to run). If this does not work, plug NETDISK via USB to see if it is recognized. If so, recover the data and reformat the drive. While in USB, delete the partition and bring the NETDISK back to the Ethernet and format the NETDISK. Formatting will erase any data on the drive.
Click on the NETDISK Device Management tool and choose Options. Select the Advanced Tab and choose “Disable Auto Play for all fixed hard drives.
Now and then, some background processes take hold of the NETDISK and do not allow shutdown or dismounting. They may also cause the computer to boot slowly as they resume their activity on the external drive. Some of the settings below have helped other users when this kind of thing happened. Anti-Virus program is accessing the drive (run Process Explorer to find it.) In Windows Device Manager Expand Disk Drives, Right Click the NETDISK Drive and choose properties, Select Policies tab, choose “Optimize for quick removal” Remove the NETDISK drive from System Recovery restore points (Control Panel; System Properties; System Protection) Remove the NETDISK drive from search indexing (Control Panel; Indexing Options; remove N drive) Some of these options may help, but there may be other things using the drive that are not known to you even though you do not see any programs running. NETDISK software version 3.7x will force the drive to dismount if you click the retry button 6 time
The permissions scheme may need to be reset. This kind of thing happened more often on drives that were formatted by XP at some time then accessed by newer computers running Windows 7 or Vista.
Click on the NETDISK Management in your System tray and make sure NETDISK is mounted. The status icon should be either Blue (Read/Write) or Green (Read Only). If it is a black colored dot, then please go to the FAQ: “I’ve installed my NETDISK and it shows up as a Black Dot.” If the NETDISK is mounted, open “Computer Management” by right-clicking on “My Computer.” Go to “Manage,” then click on “Disk Management.” Dismount and remount the drive to clearly identify the device. Make sure the drive is formatted. If it says “Not Intialized” or if you see “Unallocated” near the device, follow the steps in Chapter 8 to format the drive. If the drive is formatted, make sure it is using a structure that is recognized by your computer. NTFS is standard for Windows computers, but another type of operating system may have formatted the drive. Be Careful! Formatting/Repartitioning will erase any data on the drive.
When mounting takes a while, it is often caused by the mistaken installation of the ndasscsi disk driver.
Right Click on My Computer and choose manage. Open the Device Manager from the left side menu. Look for a yellow exclamation mark near the NETDISK SCSI Controller. Right click on the device and choose to update the driver. The driver should already be on the system, so it should load automatically. Reboot the computer and it should be able to restore the mapping.
This problem has many possible causes. Note: If you are using the NETDISK via USB or eSATA, then no software installation is required, therefore, please ignore the Black Dot. If you are connecting via LAN please check the following:
Try connecting via Ethernet cable. You can even plug the Ethernet wire direct to the computer to see if it remains stable. If it runs smoothly on the LAN then your wireless hardware is having a problem with the NETDISK connection protocol. It happens now and then with USB Wifi Adapters and with some comminations of hardware. Try updating the firmware on the router and the wifi adapters. Lastly, see if any friend with a laptop can maintain a steady connection by wireless. That can help rule out trouble with the router.
Try updating your Network Card’s drivers to the latest from the manufacturer. If you network card has the option of changing the transmit and receive buffers to both 128 (in the card’s properties in device manager), please try doing that. If you have an nForce chipset, try updating your Nvidia nForce drivers to the latest Unified Drivers from Nvidia’s website. Please also make sure that you are using 100/1000 MB switch as well.
It might just be a case of file system corruption. Mount the NETDISK to only one Computer. Then open up Command Prompt and run “chkdsk” for the NETDISK drive. Go to Start – Run – type in “cmd” without the quotation marks. Then, if, for example your drive were mounted as Drive F, you would type in: chkdsk F: /R And press the enter key. Then allow chkdsk to try and fix any corruption.
This happens when mulitple computers access the same bin. It remains a mystery why this happens only to a small minority of NETDISK users. Try disabling the recycle bin so that the computers delete files immediately rather than storing them in the Recycle Bin. This seems to happen most where there are XP computers using the same drive as Vista or Windows 7 computers. If you do not have much data on the drive, you can delete the original partition and reformat the drive from the newest computer. This will adjust the permissions to the proper UAC levels.
Create a batch file and place it in your startup folder. To create batch file: Open up notepad – type in “net share sharename=DriveLetter:path” (For example net share NETDISK =F:) Save the file as a .bat extension. For example, the file name would be called “NETDISK.bat”. This will prevent the shared device to get lost after a reboot.
By default, the suspend/sleep mode on windows PC’s is disabled when NETDISK connection software is installed. This is done because the computer treats the NETDISK drive as an internal disk, but if the connection is severed by a hibernation then restored in a different location, where the NETDISK is inaccessible, you may experience strange behaviour. Another reason is that if one PC changes the contents of the drive while another is sleeping, the sleeping PC will have a surprise when it wakes up. There is a way to allow or deny the suspend/hibernate process from the NETDISK software in Windows.
Click on the NETDISK manager icon in the taskbar > Choose options > Select the advanced tab in the window that pops up > Look for Suspend/Hibernation support Choose the way you would like the feature to operate.
If you will start the computer in another such place, please dismount the drive before removing the computer from the network.
Overall the NETDISK connection software worked well in Win7 since the beta release stage. There were some unusual incidents when it was fully released. Below are some things that helped in the unusual incidents. Permission Update: This helped when the external drive was originally used in Windows XP. Users either reformatted the drive from the Windows 7 machine or made the Administrators group owner of everything on the drive. BIOS and Component Firmware / Driver updates: Even a so-called “fresh install” may not provide the best driver for all on-board devices and components. Video cards, network adapters and other devices can share hardware interrupts. If you installed Windows 7 on existing hardware, there is a possibility that some of them are working with generic drivers or incompatible firmware. Check the manufacturer’s home page for upgrades to Network Card, Video Card, and mother board BIOS. NETDISK Driver Downgrade: Some NETDISK users had to connect to their device with earlier NETDISK software versions. Driver versions from 3.4x were tested and working on Windows 7 during the release stages. This solution was effective for users with NETDISK not created by Ximeta. There were changes to the LPX protocol in newer NETDISK Software versions which were unsupported by the manufacturers of some early NETDISKs. If your device is not made by Ximeta or IOCELL Networks, you might try this as a workaround.
When you get this type of error message it means something is grabbing a hold of your NETDISK Drive in the background. A way to find out which program is causing it is with a program called Process Explorer. http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx Download this and double click this program then do a search by handle, (click the little binoculars) and type in your NETDISK drive letter follow by a “:” Hit enter and Process Explorer will give you a list of programs that are accessing your drive. Kill those processes and you should be able to dismount. If you are sure you will not lose any data you can also force the drive to dismount if you click the retry button 6 times or by using the command line tools mentionedin chapter 10.
This only happens when incorrect characters are entered in the boxes. There are no letter “O”s; please verify that you have used the number “0″ (zero) for anything resembling an “O.” The Letter I is also not used so put a one in those places. Some other characters that have been confused are B and 8, S and 5, A and 4, H and 4, X and Y, G and 6, two V’s and W.
Connecting to the NETDISK with different interfaces at the same time is not supported. Please use only one kind of connection at a time. If you need to connect by USB or eSATA, perhaps for disk maintenance or to off-load data to your media player, you can simply unplug the Ethernet jack, then connect by one other interface. It would be good to notify the other computer users in case they are performing any kind of read write operations. The reason it only works by one interface at a time is that USB and eSATA are simply “single host access” protocols. There is no way to manage the access between hosts using those protocols. As far as the NDAS connection is concerned, it is just another form of connecting to a hard disk. However it has the unique property that each computer can also communicate and manage access because they are networked. If you need to connect by USB or eSATA the network connection will fail because the USB or eSATA connected device, like a media player, becomes the “single access host” and the network connection will drop. There is no technological way around this USB / eSATA protocol limitation. The actual precedence for usage is eSATA, USB then Network. So you cannot connect one computer by eSATA and another by USB either. The eSATA connection will become the single access host.
Yes, the drivers need to be installed on each computer that wants access to NDAS device. However, if you are using Windows Sharing, only one computer will need the software installed (Computer must be on as a “Host” computer). The other computers will not need it.
NDAS is a better alternative to NAS or SAN. NDAS is much more cost-effective, efficient and easy to use. It is for users looking for lower costs and storage associated with backup / archiving. Although both NDAS and NAS are storage devices that are implemented over a network, NDAS takes up less space than NAS or SAN products. NDAS utilizes NDAS technology allowing it to connect the hard disk directly to a network without a server. In NAS, the hard disk must be connected to a storage server, which must also be connected to the network.
The NETDISK 351 & 352 are basically compatible with all standard 3.5″ SATA hard disks. The 251 series currently has a 500GB capacity limit. The preferred choice would be Green IT series disks of different manufacturers. Samsung’s EcoGreen series or Caviar Green disks from Western Digital excelled during testing thanks to their extremely quiet operation and low power consumption. High performance hard disks, especially ones which have high starting current consumption of over 2.5 Amp, are not recommended.
NDAS devices can be used with a variety of applications. It is ideal for all users that cannot afford NAS systems, such as small to medium businesses, SOHO (Small Office Home Office), work-groups, departments, schools and public institutions. NDAS technology’s convenience and low cost provides the best storage solution for home/office networking.
Use as storage for Personal Computers and Home Networking (storing and sharing files, backup/archiving, etc.)
Expanding storage requirements
Business primary or secondary network storage Public institution’s storage for data archives, disclosed data, backups, and data conservation. Multimedia storage device (MP3s, Digital Photos, Digital Video) Multi-platform networking (Simultaneous read-only use from Macintosh and Windows) Non-PC/Non-Computing applications (security, CCTV, technograph recording, MRI, entertainment)
While the majority of network switches and routers are compatible with NDAS, there are a few known exceptions. NDAS has had trouble when using:
In some cases firmware updates or protocol settings have been reported to allow NDAS traffic, but we do not offer support for such workarounds. Some 2Wire users can use NDAS by installing a normal switch on the LAN and using the 2Wire product only as a modem. NDAS devices also will not work when connected to a network hub. The network hub does nothing to direct traffic on the lan. Devices connected by a hub, need programs installed to capture and filter the network packets. NDAS devices do not possess such operating system level functionality. So NDAS devices must connect to the LAN by a switch or router. Switches and routers are able to direct the NDAS traffic at the packet level.
For any other troubleshooting, please call our tech support at 609.799.1213.