NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AEBS: Bad Packets Unrecovered TCP Retransmits NV and NV+
Bad Packets Unrecovered TCP Retransmits TCP Retransmits w ReadyNAS NV NV+ and Airport Extreme Base Station 5th Generation I got an Airport Extreme Base Station (AEBS), 5th generation this past Nove...
Fixed I think.
Sorry for the delayed response. I have been traveling followed by being sick for the past couple weeks.
As it turns out I think my entire problem was all due to BAD CABLE.
I had some bad cable to begin with and so ordered a bunch of Cat 6 and Cat6a cable from Monoprice since I have always had great luck with them before. This time I ordered a 1' Cat6a, a 5' Cat6a, a 10' Cat6a, and 2 10'Cat 6 cables from them.
All 3 10' lengths turned out to produce bad packets and TCP Retransmits no matter how they were hooked up.
After wasting a weeks time trying to reconnect everything in different ways, I started from scratch and looked more specifically at the cables with greater depth. They weren't producing massive errors like my old bad cables. In fact it took a while for the Cat6a cable to produce errors…. I had to work at copying, transferrring files, playing various videos and audio files before I noticed it started spitting out errors on each of my servers (a ReadyNAS and then the ReadyNAS+) directly connected to the mac mini 2010 .
I have never had a bad cable from them before and got 3 this time.
So far it seems that the 1' Cat6a and the 5' Cat6a are performing well without any errors. It does make me sick to click on the Show Errors box as of now for sheer terror of seeing an error. But so far so good.
Anyhow…. it cost me a lot of time to figure this out.
I thought the AEBS or the Switch might be bad, but in the end it was simply the brand new cable.
So I don't need to change out my AEBS or my Procurve Switch.
I will need to pick up some new cables somewhere else since my packaging for the cables got tossed a bit ago.
-----------------------------
Here is my current setup:
Mac Mini 2010
HP Procurve 1400 8G switch
AEBS 5th Generation
ReadyNAS NV
ReadyNAS NV+
The mini is connected via the 1' Cat 6a cable to the HP Switch
The NV+ is connected via an apple Cat5e to the HP Switch
The NV is connected via the 5' Cat6a cable to the HP Switch
Mac Configuration
Ethernet Configured using DHCP with manual address; Static IP for the Network. (192.168.168.*)
Hardware - configured: automatic; speed 1000baseT; duplex: full duplex,flow control; MTU 1500
Wifi on mac mini enabled to connect via wireless N to the AEBS for internet connectivity and to share the internet connection with my wife's work network too.
NV and NV+
Both don't have jumbo frames enabled since I guess it isn't needed and doesn't help in wireless N
Both running Auto-negotiation at 1000baseT; MTU 1500
Both have a static IP for the Network (192.168.168.*)
Lesson learned… it can be the simplest thing leading to errors including new out of the package cable.
Sorry for the delayed response. I have been traveling followed by being sick for the past couple weeks.
As it turns out I think my entire problem was all due to BAD CABLE.
I had some bad cable to begin with and so ordered a bunch of Cat 6 and Cat6a cable from Monoprice since I have always had great luck with them before. This time I ordered a 1' Cat6a, a 5' Cat6a, a 10' Cat6a, and 2 10'Cat 6 cables from them.
All 3 10' lengths turned out to produce bad packets and TCP Retransmits no matter how they were hooked up.
After wasting a weeks time trying to reconnect everything in different ways, I started from scratch and looked more specifically at the cables with greater depth. They weren't producing massive errors like my old bad cables. In fact it took a while for the Cat6a cable to produce errors…. I had to work at copying, transferrring files, playing various videos and audio files before I noticed it started spitting out errors on each of my servers (a ReadyNAS and then the ReadyNAS+) directly connected to the mac mini 2010 .
I have never had a bad cable from them before and got 3 this time.
So far it seems that the 1' Cat6a and the 5' Cat6a are performing well without any errors. It does make me sick to click on the Show Errors box as of now for sheer terror of seeing an error. But so far so good.
Anyhow…. it cost me a lot of time to figure this out.
I thought the AEBS or the Switch might be bad, but in the end it was simply the brand new cable.
So I don't need to change out my AEBS or my Procurve Switch.
I will need to pick up some new cables somewhere else since my packaging for the cables got tossed a bit ago.
-----------------------------
Here is my current setup:
Mac Mini 2010
HP Procurve 1400 8G switch
AEBS 5th Generation
ReadyNAS NV
ReadyNAS NV+
The mini is connected via the 1' Cat 6a cable to the HP Switch
The NV+ is connected via an apple Cat5e to the HP Switch
The NV is connected via the 5' Cat6a cable to the HP Switch
Mac Configuration
Ethernet Configured using DHCP with manual address; Static IP for the Network. (192.168.168.*)
Hardware - configured: automatic; speed 1000baseT; duplex: full duplex,flow control; MTU 1500
Wifi on mac mini enabled to connect via wireless N to the AEBS for internet connectivity and to share the internet connection with my wife's work network too.
NV and NV+
Both don't have jumbo frames enabled since I guess it isn't needed and doesn't help in wireless N
Both running Auto-negotiation at 1000baseT; MTU 1500
Both have a static IP for the Network (192.168.168.*)
Lesson learned… it can be the simplest thing leading to errors including new out of the package cable.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
