April 30, 201214 yr Yesterday, I was very happy because I thought I had fixed my network transfers issues from getting dropped packets, errors and frames. Today, I woke up and checked my system log, and ethernet info and this is what I've found: 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: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes NIC driver info (from ethtool -i) driver: e1000 version: 7.3.21-k8-NAPI firmware-version: bus-info: 0000:02:06.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:19220 errors:2 dropped:6 overruns:0 frame:1 TX packets:1186 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1439364 (1.3 MiB) TX bytes:408953 (399.3 KiB) syslog-2012-04-30.txt
April 30, 201214 yr Author I forgot to mentioned. Yesterday, I had jumbo frames enable in my W7 PC, as well as MTU=9000 in my server's network config file. It was working fine, but I had to reset my server because for some reason or another it went from 1000 MB/s full duplex to 100 MB/s connection only. I had to change everything back to how it was W7 PC disabled jumbo frames, and MUT= "blank" in my server's network config file. I re-booted my W7 PC, Server, router and switch, and I was able to get the 1000 MB/s full duplex back. This morning I got the error mentioned above. I've changed the cables going from the switch to the server. That one is good I know 100%. I've checked the cable going from my switch to the W7 PC with a cable checker tool and it says the connection is fine. I terminated that cable myself. Both cables are Cat5e. I will be ordering Cat6 cables for my server and PC today. May be that will fix the issue.
April 30, 201214 yr I've checked the cable going from my switch to the W7 PC with a cable checker tool and it says the connection is fine. I terminated that cable myself. Both cables are Cat5e. I will be ordering Cat6 cables for my server and PC today. May be that will fix the issue. How far back are you untwisting the cables to put them in the plugs? The twists should ideally be maintained all the way into the end of the clear plastic, with the cable jacket inserted into the crimped portion of the plug. I've seen quite a few cables with the pairs visible beyond the end of the clear plastic, and they may work, or may not. Here is an image that shows what I mean. http://www.make-my-own-house.com/images/wiresinend.jpg
April 30, 201214 yr Author I've checked the cable going from my switch to the W7 PC with a cable checker tool and it says the connection is fine. I terminated that cable myself. Both cables are Cat5e. I will be ordering Cat6 cables for my server and PC today. May be that will fix the issue. How far back are you untwisting the cables to put them in the plugs? The twists should ideally be maintained all the way into the end of the clear plastic, with the cable jacket inserted into the crimped portion of the plug. I've seen quite a few cables with the pairs visible beyond the end of the clear plastic, and they may work, or may not. Here is an image that shows what I mean. http://www.make-my-own-house.com/images/wiresinend.jpg Yeah, my are further back. I will try to cut them shorted and see how that works. A friend of mine (IT dude) said that it should really matter as long as the pairs are hooked up correctly, but at this point, I am willing to try anything.
May 1, 201214 yr Author I order some cat6 cables already terminated. I'll just wait for those to get here rather than mess around with cutting the cables. They should be here today .
May 2, 201214 yr Author Ok, I just finished running the Cat6 cable from my giga switch to the server, and from the giga switch to the W7 PC. This is what I've got after rebooting both. 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: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes NIC driver info (from ethtool -i) driver: e1000 version: 7.3.21-k8-NAPI firmware-version: N/A bus-info: 0000:02:06.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:253 errors:0 dropped:0 overruns:0 frame:0 TX packets:254 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22297 (21.7 KiB) TX bytes:229055 (223.6 KiB) The rest of the house still running on Cat5e. We'll see what happens throughout the day. I am wondering if I will still get errors, dropped and frames if any of the other cables (cat5e), which I terminated aren't changed for ones that came terminated. I will try to re-terminate them tomorrow. I got new boot covers for the rj45 ends, and I will try to make it look like a professional did it. I didn't know if you leave the strands expose could have an impact. syslog-2012-05-01.txt
May 2, 201214 yr I got new boot covers for the rj45 ends, and I will try to make it look like a professional did it. I didn't know if you leave the strands expose could have an impact. It's not the exposed strands, it's the lack of consistent twist. Parallel untwisted wires can pick up interference from poorly shielded equipment, causing random data corruption. The less you alter the twist rate, the less interference it will pick up, or more correctly, the more the interference will effect both wires equally, thus cancelling itself out.
May 2, 201214 yr Author I got new boot covers for the rj45 ends, and I will try to make it look like a professional did it. I didn't know if you leave the strands expose could have an impact. It's not the exposed strands, it's the lack of consistent twist. Parallel untwisted wires can pick up interference from poorly shielded equipment, causing random data corruption. The less you alter the twist rate, the less interference it will pick up, or more correctly, the more the interference will effect both wires equally, thus cancelling itself out. Got it. Thanks.
May 2, 201214 yr I've checked the cable going from my switch to the W7 PC with a cable checker tool and it says the connection is fine. I terminated that cable myself. Both cables are Cat5e. I will be ordering Cat6 cables for my server and PC today. May be that will fix the issue. How far back are you untwisting the cables to put them in the plugs? The twists should ideally be maintained all the way into the end of the clear plastic, with the cable jacket inserted into the crimped portion of the plug. I've seen quite a few cables with the pairs visible beyond the end of the clear plastic, and they may work, or may not. Here is an image that shows what I mean. http://www.make-my-own-house.com/images/wiresinend.jpg Yeah, my are further back. I will try to cut them shorted and see how that works. A friend of mine (IT dude) said that it should really matter as long as the pairs are hooked up correctly, but at this point, I am willing to try anything. at 100Mb/s perhaps. At 1000Mb/s, he is mistaken.
May 2, 201214 yr Author I've checked the cable going from my switch to the W7 PC with a cable checker tool and it says the connection is fine. I terminated that cable myself. Both cables are Cat5e. I will be ordering Cat6 cables for my server and PC today. May be that will fix the issue. How far back are you untwisting the cables to put them in the plugs? The twists should ideally be maintained all the way into the end of the clear plastic, with the cable jacket inserted into the crimped portion of the plug. I've seen quite a few cables with the pairs visible beyond the end of the clear plastic, and they may work, or may not. Here is an image that shows what I mean. http://www.make-my-own-house.com/images/wiresinend.jpg Yeah, my are further back. I will try to cut them shorted and see how that works. A friend of mine (IT dude) said that it should really matter as long as the pairs are hooked up correctly, but at this point, I am willing to try anything. at 100Mb/s perhaps. At 1000Mb/s, he is mistaken. Thanks Joe L. I will re-terminate the other cables. I came back from work and check the ethernet info via unmenu, and this is what I've got: 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: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes NIC driver info (from ethtool -i) driver: e1000 version: 7.3.21-k8-NAPI firmware-version: N/A bus-info: 0000:02:06.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18691 errors:2 dropped:26 overruns:0 frame:1 TX packets:1568 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1429697 (1.3 MiB) TX bytes:597911 (583.8 KiB) syslog-2012-05-02.txt
May 2, 201214 yr Author I've created a map of my network. I've isolated the tower/server and W7PC to be directly in the 8 port Trendnet Gigabit switch. However, I didn't have enough ports in the router, so I had to connect my 5 port Netgear giga switch to the 8 port. Everything else is connected to the WNDR3700 router. My question is since I know that my tower/server and W7 PC cables and hooked up are done correctly, will I be getting the errors, dropped packet, frames, etc due to one or more of the other ethernet cables?
May 2, 201214 yr Author I just order 5 more cat6 cables to replace the ones hooked up to the 2 xboxes, ps3 and dune media player. The only cable I probably won't be changing will the one from my master bedroom (5 ports giga switch) to the living room (8 ports gigabit switch). That's like a 100 feet long cable, which runs from the living room, to the out side back yard, running along the inside of the roof all the way to the master bedroom's wall to the 5 port giga switch to the xbox.
May 2, 201214 yr Author I feel so freaking stupid. I didn't know that the strands from the cat cable would go through RJ45 plug...no wonder I wasn't able to make it look like a already terminated cable. I youtubed how to terminate a Cat5e/Cat6 cable with RJ45 plugs.......and I was like....STUPID STUPID STUPID!!!
May 2, 201214 yr The only cable I probably won't be changing will the one from my master bedroom (5 ports giga switch) to the living room (8 ports gigabit switch). That's like a 100 feet long cable, which runs from the living room, to the out side back yard, running along the inside of the roof all the way to the master bedroom's wall to the 5 port giga switch to the xbox. Not trying to pile on here, but I must warn you that unless you ran outdoor rated cable, you will likely be rerunning that one anyway in a year or 2. The jacket material on standard cable just isn't made for exposed use. It will get brittle and crumble at the slightest touch. If there truly is no way to run it indoors, I'd get some pvc pipe and make a conduit for it. At least that way it's sheltered. You didn't staple it to the house did you? Bare staples will damage the wires inside the jacket. You can get cable attachment staples that have plastic guides that don't pinch the wires. I know it sounds like I'm beating you up about your wiring, but I'm just trying to help, really I am.
May 3, 201214 yr Author The only cable I probably won't be changing will the one from my master bedroom (5 ports giga switch) to the living room (8 ports gigabit switch). That's like a 100 feet long cable, which runs from the living room, to the out side back yard, running along the inside of the roof all the way to the master bedroom's wall to the 5 port giga switch to the xbox. Not trying to pile on here, but I must warn you that unless you ran outdoor rated cable, you will likely be rerunning that one anyway in a year or 2. The jacket material on standard cable just isn't made for exposed use. It will get brittle and crumble at the slightest touch. If there truly is no way to run it indoors, I'd get some pvc pipe and make a conduit for it. At least that way it's sheltered. You didn't staple it to the house did you? Bare staples will damage the wires inside the jacket. You can get cable attachment staples that have plastic guides that don't pinch the wires. I know it sounds like I'm beating you up about your wiring, but I'm just trying to help, really I am. It is rated for outdoor, and no I didn't staple it to the roof, but the wire that was there before was stapled by the U-Verse tech. I used plastic loop holders.
May 7, 201214 yr Author Today, I came home from work, and found this: 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: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes NIC driver info (from ethtool -i) driver: e1000 version: 7.3.21-k8-NAPI firmware-version: N/A bus-info: 0000:02:06.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9002608 errors:1444 dropped:32 overruns:0 frame:832 TX packets:12558571 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4248651620 (3.9 GiB) TX bytes:4245427972 (3.9 GiB) I also in my system log that "carrier lost." What can be causing this? The cable connected from my W7 PC to the 8 port gigag router is Cat6 brand new. The cable connected from my tower to 8 port giga switch is Cat 6 brand new. All the other cables are Cat5e, which I re-terminated and checked with network cable tool, and they are all good. The next thing I can think of is may be my router? I just ripped a SD movies, which was 3.38 GB file, and it transfer at a rate of 17 MB/s. I usually get 31 to 35 MS/s. I'm going crazy with this issue. syslog-2012-05-07.txt
May 9, 201214 yr May 5 21:25:58 Tower dhcpcd[993]: eth0: renewing lease of 192.168.1.2 May 5 21:25:59 Tower dhcpcd[993]: eth0: acknowledged 192.168.1.2 from 192.168.1.1 May 5 21:25:59 Tower dhcpcd[993]: eth0: leased 192.168.1.2 for 86400 seconds May 6 09:25:59 Tower dhcpcd[993]: eth0: renewing lease of 192.168.1.2 May 6 09:25:59 Tower dhcpcd[993]: eth0: acknowledged 192.168.1.2 from 192.168.1.1 May 6 09:25:59 Tower dhcpcd[993]: eth0: leased 192.168.1.2 for 86400 seconds May 6 10:49:26 Tower dhcpcd[993]: eth0: carrier lost May 6 10:49:26 Tower kernel: e1000: eth0 NIC Link is Down May 6 10:49:29 Tower dhcpcd[993]: eth0: carrier acquired May 6 10:49:29 Tower dhcpcd[993]: eth0: rebinding lease of 192.168.1.2 May 6 10:49:29 Tower kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX May 6 10:49:29 Tower dhcpcd[993]: eth0: acknowledged 192.168.1.2 from 192.168.1.1 May 6 10:49:29 Tower dhcpcd[993]: eth0: checking for 192.168.1.2 May 6 10:49:34 Tower dhcpcd[993]: eth0: leased 192.168.1.2 for 86400 seconds May 6 22:49:35 Tower dhcpcd[993]: eth0: renewing lease of 192.168.1.2 May 6 22:49:35 Tower dhcpcd[993]: eth0: acknowledged 192.168.1.2 from 192.168.1.1 May 6 22:49:35 Tower dhcpcd[993]: eth0: leased 192.168.1.2 for 86400 seconds I would try resetting your router or try another NIC. You could also test this by taking the router out completely, just remove the cable that goes from your router to the gigabit switch your server & win7pc are on and set the ip manually on your win7pc. See what happens to your copies etc. when the router isn't connected. Might also be worth rebooting the server before you test the speed again.
May 10, 201214 yr Author So, I've changed my 8 Trendnet Gigabit switch for a Netgear 8 port gigabit switch. I also changed several cables that were connected to this switch for cables that were pre-terminated. I turned off the server, and I also moved my Intel Pro 1000 NIC PCI to the other PCI slot just for the hell of it. I proceeded to turn on the server and everything was clean. No dropped packets, errors, etc. I then proceeded to transfer a 19 GB file. I noticed the speed was erratic going from 9 MB/s to 15 MB/s. After two minutes, I noticed the speed remained constant at 18.5 MB/s. After 4 min. the speed increased and remained constant at 19.2 MB/s until the file completed transferring. I kept updtating the System Info / Ethernet Info vi unmenu throughout the transfer. It never got any errors, or dropped packets. As soon as the file completed it showed 1 dropped packet. 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: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes NIC driver info (from ethtool -i) driver: e1000 version: 7.3.21-k8-NAPI firmware-version: N/A bus-info: 0000:02:05.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14445830 errors:0 dropped:1 overruns:0 frame:0 TX packets:1904210 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4070329491 (3.7 GiB) TX bytes:137704126 (131.3 MiB) syslog-2012-05-09.txt
May 12, 201214 yr Author Well, I've been replacing Cat5e cables for Cat6 cable, and 8 port gigabit Trendnet routers fro 8 gigabit Netgear routers. I proceeded to do some testing pinging www.google.com from my W7 PC, and from my server. I also pinged W7 PC with the server, and I got no errors or dropped packets from my network. I then proceeded to transfer a 2.2 GB file from my W7 PC to the server. I logged in to unmenu and uses the ethernet info. I noticed 2 errors and 143 dropped packets after completing the file transfer. I then logged in to telnet and ran the ifconfig, and got no errors by using telnet to server. So, which one do I go by? I don't understand why one would show errors and the other one doesn't. This is from unmenu / 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: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes NIC driver info (from ethtool -i) driver: e1000 version: 7.3.21-k8-NAPI firmware-version: N/A bus-info: 0000:02:05.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4901397 errors:2 dropped:143 overruns:0 frame:1 TX packets:7034368 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3136111339 (2.9 GiB) TX bytes:4205939061 (3.9 GiB) Telnet to server (ifconfig) Tower login: root Linux 3.1.1-unRAID. root@Tower:~# ifconfig eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4901509 errors:2 dropped:143 overruns:0 frame:1 TX packets:7034430 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3136120000 (2.9 GiB) TX bytes:4205948771 (3.9 GiB) 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:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:962 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:143678 (140.3 KiB) TX bytes:143678 (140.3 KiB)
May 12, 201214 yr This is from unmenu / ethernet info Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4901397 errors:2 dropped:143 overruns:0 frame:1 TX packets:7034368 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3136111339 (2.9 GiB) TX bytes:4205939061 (3.9 GiB) Telnet to server (ifconfig) Tower login: root Linux 3.1.1-unRAID. root@Tower:~# ifconfig eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4901509 errors:2 dropped:143 overruns:0 frame:1 TX packets:7034430 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3136120000 (2.9 GiB) TX bytes:4205948771 (3.9 GiB) 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:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:962 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:143678 (140.3 KiB) TX bytes:143678 (140.3 KiB) Both ways show the same to me.2 errors 143 dropped
May 12, 201214 yr This is from unmenu / ethernet info Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4901397 errors:2 dropped:143 overruns:0 frame:1 TX packets:7034368 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3136111339 (2.9 GiB) TX bytes:4205939061 (3.9 GiB) Telnet to server (ifconfig) Tower login: root Linux 3.1.1-unRAID. root@Tower:~# ifconfig eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4901509 errors:2 dropped:143 overruns:0 frame:1 TX packets:7034430 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3136120000 (2.9 GiB) TX bytes:4205948771 (3.9 GiB) 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:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:962 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:143678 (140.3 KiB) TX bytes:143678 (140.3 KiB) Both ways show the same to me.2 errors 143 dropped +1 It appears you still have a problem, for some reason packets are getting dropped Did you try going back to basics? I would try connecting your PC directly to the unRAID server with a crossover cable and set the IPs manually, then do your file transfers and check for any drops.
May 13, 201214 yr Author I've tried connecting my pc to the server directly, but I wasn't able to connect / communicate with it. I'll try it again see what happens.
May 13, 201214 yr To directly connect you must manually set IP addresses on both machines. Easiest is to check what IP's you have now, and manually set the addresses to what they automatically are getting right now. That way you can confirm your manually set addresses are working before you unplug from the switch. Actually, you shouldn't even need to shut down after you confirm the manual addressing is working, just switch the network cables.
Archived
This topic is now archived and is closed to further replies.