In case this happens to anyone with the same luck as me:

I connected to the drive from my windows network.  The web admin page for the NAS showed zero disks.  During storage, gravity managed to un-seat the SATA from the connector mounted on the case.  The drives are pushed onto the connector from the rear of the chasis.

The drives were re-seated on the connectors and the system was re-started.

The NAS was immediately detected and automatically configured.

/jph

Enabled DHCP server on internal network in WebAdmin (http://wiki.linuxmce.org/index.php/Network_Settings).  Verified that DHCP leases were issued in WebAdmin/Advanced/Network/DHCP Leases.

 Can see the storage device as a samba share from Kunbutu desktop but still not detected by lmce.

 No unknown devices in WebAdmin/Advanced/Configuration/Unknown Devices.

I have attached a NAS on eth1 (internal) but the device is not recognized.  There are no unrecognized devices in WebAdmin Advanced> Configuration > Unknown Devices.

________________
Result of ifconfig -a:

eth0      Link encap:Ethernet  HWaddr bc:ae:c5:9a:1a:7a 
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::beae:c5ff:fe9a:1a7a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16760 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12198 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20814810 (20.8 MB)  TX bytes:904542 (904.5 KB)
          Interrupt:210 Base address:0x6000

eth1      Link encap:Ethernet  HWaddr 00:0a:cd:1e:64:6c 
          inet addr:192.168.80.1  Bcast:192.168.80.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:211 Base address:0xa000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5707 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5707 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1222111 (1.2 MB)  TX bytes:1222111 (1.2 MB)

pan0      Link encap:Ethernet  HWaddr de:b5:96:6e:d2:a1 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

_______________________
result of dmesg | grep eth1:

[   15.534728] eth1: Identified chip type is 'RTL8168D/8111D'.
[   17.332139] udev: renamed network interface eth1 to eth0
[   17.382097] udev: renamed network interface eth0_rename to eth1
[   30.370848] r8168: eth1: link down
[   30.371212] ADDRCONF(NETDEV_UP): eth1: link is not ready
[  968.810670] r8168: eth1: link down
[  968.811330] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 1286.070497] r8168: eth1: link up
[ 1286.071095] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 1286.808195] r8168: eth1: link up
[ 1315.034173] r8168: eth1: link down
[ 1315.809017] r8168: eth1: link down
[ 1317.347774] r8168: eth1: link up
[ 1317.808191] r8168: eth1: link up
[ 1390.934504] r8168: eth1: link down
[ 1390.935402] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 1391.932527] r8168: eth1: link down
[ 1393.381991] r8168: eth1: link up
[ 1393.382317] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 1393.932516] r8168: eth1: link up
[ 1515.453913] r8168: eth1: link down
[ 1515.454503] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 1516.452528] r8168: eth1: link down
[ 1517.999381] r8168: eth1: link up
[ 1517.999708] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 1518.452521] r8168: eth1: link up

Ther does'nt appear to be dhcp service on eth1?  Any ideas?

Thanks for your help and your patience.

 I will start a new thread, if I continue to experience problems with the NAS.

//jph

I executed the update query directly on the database and verfied that the row was updated.  I re-loaded the orbitor and now eth0 (dhcp) and eth1(static) are both recognized in WebAdmin. In the Advanced/Network/Network settings I was able the refresh the the IP on eth0.  So far so good.

 I reconnected my NAS on eth1 where I have media from a previous installation.  If the dhcp server is active on eth1, should'nt the system recognize the NAS instaneously or will this take sometime?

/jhp

I found a very old post on a blog.  I don't know if it still applies or if it will lead to stability issues:

To recognize the second NIC:
UPDATE Device_DeviceData SET IK_DeviceData="eth0,dhcp|eth1,192.168.80.1,255.255.255.0" WHERE FY_DeviceDeviceData=32;

/jph

I ran the script which generated two error messages:
Stopping DHCP server - [FAIL]
Failed to send 'clear' to local ypserver RPC: Program not registeredUpdating passwd.byusid.
Followed by msg:  Now you can run ypinit -s dcerouter on all slave services.

In WebAdmin under Advanced/Network only eth1:1 (dhcp) and eth1 (static) were recognized.  No NIC were displayed in the device tree. The file /etc/network was re-written to eth1:1 (dhcp) and eth1 (stat).  I changed this back to eth0 (dhcp) and eht1 (static) and then restated the network to re-establish my internet connection.

/jph

Here is the result of ip addr:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0a:cd:1e:64:6c brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.20/24 brd 192.168.1.255 scope global eth1
    inet6 fe80::20a:cdff:fe1e:646c/64 scope link
       valid_lft forever preferred_lft forever
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether bc:ae:c5:9a:1a:7a brd ff:ff:ff:ff:ff:ff
    inet 192.168.80.1/24 brd 192.168.80.255 scope global eth0
4: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether be:6c:94:6d:9a:5f brd ff:ff:ff:ff:ff:ff

/jph

The query returns:
eth1:1,dhcp|eth1,192.168.80.1,255.255.255.0
one row in set

When I first loaded the system, I originally had an Intel Gigbit NIC card.  After LinuxMCE installation and connecting a NAS to the internal NIC I realised that the NIC was'nt recoginized since the system failed to acknowledge the NAS.  On giving up getting that card to work , I installed the Realtek NIC.  I know this card is functional. 

How do I correct the database?.  Specifically how do I log into the database and what SQL statements do I need to execute? (The link did'nt provide enough information).

Thanks for you asisstance:  Here is the output:

# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:9a:1a:7a", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0a:cd:1e:64:6c", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

I made eth0 internal and eth1 external in the interfaces file.  When I swapped the NIC cards using WebAdmin, it caused the system to reboot.  The system then overwrote the interface file to eth1:1 to dhcp (external) and eth1 to static.

Its an ASUS AT5IONT-I motherboard with one integrated NIC and a second NIC installed on the PCI-e slot.

There two RTL811/8168BB NIC cards installed both running the r6168 driver.  I have changed /etc/network/interfaces file to reflect two nics (eth0 external DHCP and eth1 static).  In the Advance/Network/settings , Linuxmce recognizes only eth1 and it creates a virtual NIC at eth1:1.  My changes to etc/network/interface get re-wrtten on re-boot to eth1 and eth1:1 consistent with the settings in  Advanced/Network/Settings.  Both cards are functional as verfied by switching eth0 and eth1 in /etc/udev/rules'/rules.d/70-persistent-net.rules.  What step am I missing?