[SOLVED] Errors In, but no Errors Out and No Collisions on both WAN

[Sergei_Shablovsky]

@mer said in [SOLVED] Errors In, but no Errors Out and No Collisions on both WAN:

@sergei_shablovsky Amazing how often physical connectivity is the problem. Copper that works fine for 10M could have all kinds of problems at 10G. Fiber? Need to make sure everything matches.

In exactly this case both the misconfiguration / changes in ISP work and length of cable impact.

Lesson to take away:
Check physical first :)

Need to re-read our “Resolving uplink physical connection problems” checklist ;)

[mer]

@sergei_shablovsky Another thing with copper cables that I've run into: cheap ones "seem" to work, but will cause problems. Especially at higher speeds and longer distances. The distance is part that everyone overlooks. Oh that 110m cat-4 should be fine, it worked before.

Glad that it was simple to correct.

[Sergei_Shablovsky]

@mer said in [SOLVED] Errors In, but no Errors Out and No Collisions on both WAN:

Another thing with copper cables that I've run into: cheap ones "seem" to work, but will cause problems. Especially at higher speeds and longer distances. The distance is part that everyone overlooks.

Thank You, I forgot to mention this.

Of course, our rules would be Using for copper link as much quality as available from local distributor.
Because You make cabling one time in 2-3-5-8 years, up to the next applience upgrade ;)

[mer]

@sergei_shablovsky said in [SOLVED] Errors In, but no Errors Out and No Collisions on both WAN:

Of course, our rules would be Using for copper link as much quality as available from local distributor.
Because You make cabling one time in 2-3-5-8 years, up to the next applience upgrade ;)

That is a very good rule. Even for your home network.