December 31, 200916 yr Hi Hope someone can help. I think i have missed something really simple as i am unable to play back any of me saved media on my new unraid box. My Vista HTPC hangs everytime i try to open a file. I have read all the vista posts and tried all the tweaks but to no avail. I am a newb when it comes to networks so suspect this is where problem lies. My system: model name : Intel® Celeron® CPU 430 @ 1.80GHz Motherborad: Gigabyte G31M-ES2L x2 1GM DDR2 memory sticks Ethernet info NIC info (from ethtool)Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: Not reported Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pg Wake-on: d Current message level: 0x0000003f (63) Link detected: yesNIC driver info (from ethtool -i)driver: atl1cversion: 1.0.0.1-NAPIfirmware-version: N/Abus-info: 0000:02:00.0Ethernet config info (from ifconfig)eth0 Link encap:Ethernet HWaddr 00:24:1d:b3:96:33 inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2154 errors:0 dropped:0 overruns:0 frame:0 TX packets:2515 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:291814 (284.9 KiB) TX bytes:1654398 (1.5 MiB) Interrupt:26 ipconfig Microsoft Windows [Version 6.0.6002] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Windows\system32>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : IPv4 Address. . . . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 7: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2d6:34b0:3e67:3f57:fffd Link-local IPv6 Address . . . . . : fe80::34b0:3e67:3f57:fffd%11 Default Gateway . . . . . . . . . : :: C:\Windows\system32> ifconfig eth0 Tower login: root Linux 2.6.31.6-unRAID. root@Tower:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:24:1d:b3:96:33 inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2126 errors:0 dropped:0 overruns:0 frame:0 TX packets:2490 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:287797 (281.0 KiB) TX bytes:1643069 (1.5 MiB) Interrupt:26 root@Tower:~# net lookup master/net lookup HTPC2 Tower login: root Linux 2.6.31.6-unRAID. root@Tower:~# net lookup master 192.168.0.2 root@Tower:~# net lookup HTPC2 192.168.0.2 These are the highlighted items from the syslog...i see some warnings... Jan 1 18:01:37 Tower kernel: Linux version 2.6.31.6-unRAID (root@Develop) (gcc version 4.2.3) #6 SMP Thu Dec 3 10:00:15 MST 2009 Jan 1 18:01:37 Tower kernel: 1147MB HIGHMEM available. Jan 1 18:01:37 Tower kernel: 889MB LOWMEM available. Jan 1 18:01:37 Tower kernel: SMP: Allowing 4 CPUs, 3 hotplug CPUs Jan 1 18:01:37 Tower kernel: Kernel command line: initrd=bzroot BOOT_IMAGE=bzimage Jan 1 18:01:37 Tower kernel: Memory: 2011980k/2086784k available (2620k kernel code, 73552k reserved, 1316k data, 292k init, 1175432k highmem) Jan 1 18:01:37 Tower kernel: Detected 1799.872 MHz processor. Jan 1 18:01:37 Tower kernel: Console: colour VGA+ 80x25 Jan 1 18:01:37 Tower kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3599.74 BogoMIPS (lpj=17998720) Jan 1 18:01:37 Tower kernel: CPU0: Intel® Celeron® CPU 430 @ 1.80GHz stepping 01 Jan 1 18:01:37 Tower kernel: Total of 1 processors activated (3599.74 BogoMIPS). Jan 1 18:01:37 Tower kernel: ACPI Warning: Incorrect checksum in table [TAMG] - 9E, should be 9D 20090521 tbutils-246 Jan 1 18:01:37 Tower kernel: ata1.01: HPA detected: current 2930275055, native 2930277168 Jan 1 18:01:37 Tower kernel: scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD154UI 1AG0 PQ: 0 ANSI: 5 Jan 1 18:01:37 Tower kernel: scsi 1:0:1:0: Direct-Access ATA SAMSUNG HD154UI 1AG0 PQ: 0 ANSI: 5 Jan 1 18:01:37 Tower kernel: sda: Jan 1 18:01:37 Tower kernel: scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD154UI 1AG0 PQ: 0 ANSI: 5 Jan 1 18:01:37 Tower kernel: sdc: sda1 Jan 1 18:01:37 Tower kernel: sd 1:0:0:0: [sda] Attached SCSI disk Jan 1 18:01:37 Tower kernel: sdb: sdc1 Jan 1 18:01:37 Tower kernel: sd 2:0:0:0: [sdc] Attached SCSI disk Jan 1 18:01:37 Tower kernel: sdb1 Jan 1 18:01:37 Tower kernel: sd 1:0:1:0: [sdb] Attached SCSI disk Jan 1 18:01:37 Tower kernel: scsi 0:0:0:0: Direct-Access Lexar JD FireFly 1100 PQ: 0 ANSI: 0 CCS Jan 1 18:01:37 Tower kernel: sdd: sdd1 Jan 1 18:01:37 Tower kernel: sd 0:0:0:0: [sdd] Assuming drive cache: write through Jan 1 18:01:37 Tower kernel: sd 0:0:0:0: [sdd] Attached SCSI removable disk Jan 1 18:01:37 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Jan 1 18:01:37 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Jan 1 18:01:37 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 hw ether 00:24:1D:B3:96:33 Jan 1 18:01:37 Tower ifplugd(eth0)[1056]: client: SIOCSIFHWADDR: Device or resource busy - you may need to down the interface Jan 1 18:01:37 Tower ifplugd(eth0)[1056]: client: Polling for DHCP server on interface eth0: Jan 1 18:01:38 Tower logger: /etc/rc.d/rc.inet1: /sbin/dhcpcd -d -t 30 -h Tower eth0 Jan 1 18:01:38 Tower dhcpcd[1087]: broadcasting DHCP_DISCOVER Jan 1 18:01:38 Tower dhcpcd[1087]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.0.255 Jan 1 18:01:38 Tower dhcpcd[1087]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 1 18:01:38 Tower dhcpcd[1087]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 1 18:01:38 Tower dhcpcd[1087]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 1 18:01:38 Tower dhcpcd[1087]: DHCP_OFFER received from (192.168.0.1) Jan 1 18:01:38 Tower dhcpcd[1087]: broadcasting DHCP_REQUEST for 192.168.0.4 Jan 1 18:01:38 Tower dhcpcd[1087]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 1 18:01:38 Tower dhcpcd[1087]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 1 18:01:38 Tower dhcpcd[1087]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 1 18:01:38 Tower dhcpcd[1087]: DHCP_ACK received from (192.168.0.1) Jan 1 18:01:38 Tower ifplugd(eth0)[1056]: client: dhcpcd: MAC address = 00:24:1d:b3:96:33 Jan 1 18:01:38 Tower ifplugd(eth0)[1056]: client: dhcpcd: your IP address = 192.168.0.4 Jan 1 18:01:38 Tower ifplugd(eth0)[1056]: client: dhcpcd: MAC address = 00:24:1d:b3:96:33 Jan 1 18:01:38 Tower ifplugd(eth0)[1056]: client: dhcpcd: your IP address = 192.168.0.4 Jan 1 18:01:38 Tower emhttp: unRAID System Management Utility version 4.5 Jan 1 18:01:38 Tower emhttp: Copyright © 2005-2009, Lime Technology, LLC Jan 1 18:01:38 Tower emhttp: Pro key detected, GUID: 05DC-A761-B6Z7-44YBL1GTGFSA Jan 1 18:01:38 Tower emhttp: Device inventory: Jan 1 18:01:38 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host1 (sda) ata-SAMSUNG_HD154UI_S1Y6J1KSB04667 Jan 1 18:01:38 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 host1 (sdb) ata-SAMSUNG_HD154UI_S1Y6J1KSB04669 Jan 1 18:01:38 Tower emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 host2 (sdc) ata-SAMSUNG_HD154UI_S1Y6J1KSB04657 Jan 1 18:01:38 Tower emhttp: shcmd (1): rmmod md-mod >>/var/log/go 2>&1 Jan 1 18:01:38 Tower emhttp: _shcmd: shcmd (1): exit status: 1 Jan 1 18:01:38 Tower emhttp: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,16,8,32,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1 Jan 1 18:01:38 Tower kernel: xor: automatically using best checksumming function: pIII_sse Jan 1 18:01:38 Tower kernel: pIII_sse : 6491.200 MB/sec Jan 1 18:01:38 Tower kernel: xor: using function: pIII_sse (6491.200 MB/sec) Jan 1 18:01:38 Tower kernel: md: unRAID driver 0.95.3 installed Jan 1 18:01:38 Tower emhttp: Spinning up all drives... Jan 1 18:01:38 Tower kernel: md: import disk0: [8,0] (sda) SAMSUNG HD154UI S1Y6J1KSB04667 offset: 63 size: 1465138552 Jan 1 18:01:38 Tower kernel: md: import disk1: [8,16] (sdb) SAMSUNG HD154UI S1Y6J1KSB04669 offset: 63 size: 1465137496 Jan 1 18:01:38 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG HD154UI S1Y6J1KSB04657 offset: 63 size: 1465138552 Jan 1 18:01:38 Tower kernel: mdcmd (2): set md_num_stripes 1280 Jan 1 18:01:38 Tower kernel: mdcmd (3): set md_write_limit 768 Jan 1 18:01:38 Tower kernel: mdcmd (4): set md_sync_window 288 Jan 1 18:01:38 Tower kernel: mdcmd (5): set spinup_group 0 0 Jan 1 18:01:38 Tower kernel: mdcmd (6): set spinup_group 1 0 Jan 1 18:01:38 Tower kernel: mdcmd (7): set spinup_group 2 0 Jan 1 18:01:38 Tower kernel: mdcmd (: spinup 0 Jan 1 18:01:38 Tower kernel: mdcmd (9): spinup 1 Jan 1 18:01:38 Tower kernel: mdcmd (10): spinup 2 Jan 1 18:01:38 Tower emhttp: shcmd (3): /usr/local/sbin/set_ncq sda 1 >/dev/null Jan 1 18:01:38 Tower emhttp: shcmd (4): /usr/local/sbin/set_ncq sdb 1 >/dev/null Jan 1 18:01:38 Tower emhttp: shcmd (5): /usr/local/sbin/set_ncq sdc 1 >/dev/null Jan 1 18:01:38 Tower kernel: mdcmd (12): start STOPPED Jan 1 18:01:38 Tower kernel: unraid: allocating 18220K for 1280 stripes (3 disks) Jan 1 18:01:38 Tower kernel: md1: running, size: 1465137496 blocks Jan 1 18:01:38 Tower kernel: md2: running, size: 1465138552 blocks Jan 1 18:01:39 Tower emhttp: shcmd (6): mkdir /mnt/disk1 Jan 1 18:01:39 Tower emhttp: shcmd (7): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 >/dev/null 2>&1 Jan 1 18:01:39 Tower kernel: mdcmd (14): check Jan 1 18:01:39 Tower kernel: md: recovery thread woken up ... Jan 1 18:01:39 Tower emhttp: shcmd (7): mkdir /mnt/disk2 Jan 1 18:01:39 Tower emhttp: shcmd (: mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 >/dev/null 2>&1 Jan 1 18:01:39 Tower kernel: md: recovery thread has nothing to resync Jan 1 18:01:39 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Jan 1 18:01:39 Tower kernel: REISERFS (device md1): using ordered data mode Jan 1 18:01:39 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Jan 1 18:01:39 Tower kernel: REISERFS (device md2): using ordered data mode Jan 1 18:01:39 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 1 18:01:39 Tower kernel: REISERFS (device md1): checking transaction log (md1) Jan 1 18:01:39 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 1 18:01:39 Tower kernel: REISERFS (device md2): checking transaction log (md2) Jan 1 18:01:39 Tower kernel: REISERFS (device md1): Using r5 hash to sort names Jan 1 18:01:39 Tower kernel: REISERFS (device md2): Using r5 hash to sort names Jan 1 18:01:39 Tower emhttp: shcmd (10): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Jan 1 18:01:39 Tower emhttp: _shcmd: shcmd (10): exit status: 1 Jan 1 18:01:39 Tower emhttp: shcmd (11): cp /etc/exports- /etc/exports Jan 1 18:01:39 Tower emhttp: shcmd (12): killall -HUP smbd Jan 1 18:01:39 Tower emhttp: shcmd (13): /etc/rc.d/rc.nfsd restart | logger Jan 1 18:01:39 Tower emhttp: shcmd (13): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Jan 1 18:01:39 Tower emhttp: shcmd (14): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Jan 1 18:01:39 Tower emhttp: shcmd (15): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Jan 1 18:01:39 Tower emhttp: shcmd (16): crontab /var/spool/cron/crontabs/root I hope someone can see what is going on from all of the above. Thanks Andy
December 31, 200916 yr Hi Hope someone can help. I think i have missed something really simple as i am unable to play back any of me saved media on my new unraid box. My Vista HTPC hangs everytime i try to open a file. I have read all the vista posts and tried all the tweaks but to no avail. I am a newb when it comes to networks so suspect this is where problem lies. My system: model name : Intel® Celeron® CPU 430 @ 1.80GHz Motherborad: Gigabyte G31M-ES2L x2 1GM DDR2 memory sticks Ethernet info NIC info (from ethtool)Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: Not reported Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pg Wake-on: d Current message level: 0x0000003f (63) Link detected: yesNIC driver info (from ethtool -i)driver: atl1cversion: 1.0.0.1-NAPIfirmware-version: N/Abus-info: 0000:02:00.0Ethernet config info (from ifconfig)eth0 Link encap:Ethernet HWaddr 00:24:1d:b3:96:33 inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2154 errors:0 dropped:0 overruns:0 frame:0 TX packets:2515 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:291814 (284.9 KiB) TX bytes:1654398 (1.5 MiB) Interrupt:26 ipconfig Microsoft Windows [Version 6.0.6002] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Windows\system32>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : IPv4 Address. . . . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 7: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2d6:34b0:3e67:3f57:fffd Link-local IPv6 Address . . . . . : fe80::34b0:3e67:3f57:fffd%11 Default Gateway . . . . . . . . . : :: C:\Windows\system32> ifconfig eth0 Tower login: root Linux 2.6.31.6-unRAID. root@Tower:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:24:1d:b3:96:33 inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2126 errors:0 dropped:0 overruns:0 frame:0 TX packets:2490 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:287797 (281.0 KiB) TX bytes:1643069 (1.5 MiB) Interrupt:26 root@Tower:~# net lookup master/net lookup HTPC2 Tower login: root Linux 2.6.31.6-unRAID. root@Tower:~# net lookup master 192.168.0.2 root@Tower:~# net lookup HTPC2 192.168.0.2 I hope someone can see what is going on from all of the above. Thanks Andy It appears as if you have three machines on your LAN all assigned the same IP address of 192.168.0.2 The equivalent would be if you had three sons and named them all "George" and then called their name. (Real-life-example) You need to assign a DIFFERENT IP address to "master" and another different one to HTPC2. and yet a third different one on your Vista PC. (It appears as if the unRAID server has been assigned 192.168.0.4, so don't use that address, and your router has 192.168.0.1, so don't use that either. Use numbers from 192.168.0.5 through 192.168.0.254 When more than one machine on a LAN tries to respond to the same IP address, all kinds of things will lock up, just as you described, as they all expect to be unique. Joe L.
January 1, 201016 yr It does appear your unraid is using an appropriate ip address 192.168.0.4, so it's probably not one you need to mess with. Unless master and htpc2 are the same machine, one of those needs to change.
January 1, 201016 yr Author Ha...I knew it must be me! Thanks guys...time to Google on how to change ip addresses! Oh...Happy NewYear Andy
January 1, 201016 yr Author Ok, i assigned ip addresses but i still get system hang. out of interest i tried to copy a file off the server and paste it onto my desktop and i got - "There is a problem accessing N:\Movies blah blah which is unraid location, and Make sure you are connected to the network and try again". On the network map i have HTPC2 - Gateway - Internet. Tower is listed as "The following discovered device canot be placed in the map"? new ip addresses for HTPC2: Microsoft Windows [Version 6.0.6002] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Windows\system32>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : IPv4 Address. . . . . . . . . . . : 192.168.0.6 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 7: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2d6:40f:3011:3f57:fff9 Link-local IPv6 Address . . . . . : fe80::40f:3011:3f57:fff9%11 Default Gateway . . . . . . . . . : :: Tower login: root Linux 2.6.31.6-unRAID. root@Tower:~# net lookup eth0 root@Tower:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:24:1d:b3:96:33 inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:31502 errors:0 dropped:0 overruns:0 frame:0 TX packets:33277 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:5344914 (5.0 MiB) TX bytes:11880397 (11.3 MiB) Interrupt:26 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:284 errors:0 dropped:0 overruns:0 frame:0 TX packets:284 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:34232 (33.4 KiB) TX bytes:34232 (33.4 KiB) root@Tower:~# net lookup htpc2 192.168.0.6 root@Tower:~# net lookup server 192.168.0.4 root@Tower:~# Microsoft Windows [Version 6.0.6002] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Windows\system32>ping 192.168.0.4 Pinging 192.168.0.4 with 32 bytes of data: Reply from 192.168.0.4: bytes=32 time<1ms TTL=64 Reply from 192.168.0.4: bytes=32 time<1ms TTL=64 Reply from 192.168.0.4: bytes=32 time<1ms TTL=64 Reply from 192.168.0.4: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.0.4: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Windows\system32>ping 192.168.0.1 Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms Microsoft Windows [Version 6.0.6002] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Windows\system32>ping 192.168.0.6 Pinging 192.168.0.6 with 32 bytes of data: Reply from 192.168.0.6: bytes=32 time<1ms TTL=128 Reply from 192.168.0.6: bytes=32 time<1ms TTL=128 Reply from 192.168.0.6: bytes=32 time<1ms TTL=128 Reply from 192.168.0.6: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.0.6: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Windows\system32> ???? Thanks Andy
January 1, 201016 yr Did you try rebooting all servers after changing IPs? Perhaps something wasn't fully flushed out or reset?
January 2, 201016 yr Couple of questions - 1. Who's 192.168.0.1 - Often it's the gateway and not in play in internal network transfers (unless of course it's the switch and so on). Showing us a ping to it isn't interesting (except to show that a computer can reach the outside world) 2. It appears that you kind of have two names for your unraid box - Tower (as shown in your terminal sessions) and server as shown in your windows sessions. That's a bit weird, I'd expect both to be tower.
Archived
This topic is now archived and is closed to further replies.