Recommended Posts

Hi,

 

I have run up against an odd issue which I would very much appreciate some help with.

 

Background: I had shielded cat 7 cables installed throughout apartment under floors (which I was assured were tested) before fitting wooden floors etc. All cables are fine except the (most important) one running from the router in the kitchen to the main switch (switch 2) in the living room (the living room main switch goes on to provide Ethernet to the rest of the apartment). Final bit of background, the kitchen router is wired to a switch (switch 1) and used for Nest, Hue, etc.

 

So, the kitchen-living room cable is actually corrupted, upon continuity testing it was found that the orange cable creates a circuit with the shielding so must have been pierced. To get round this I swapped the orange pair with the brown pair at both ends (in the connectors) in the hope of achieving 100mbps. This worked but only under one set of circumstances as follows:

 

Router - switch 1 - PC

 

I was hoping for Router - any configuration including switch 2 but none provide internet: Router - PC nope, Router - switch 1 - switch 2 - PC nope, router - switch 2 - pc nope.

 

Any help with this would be much appreciated, I can't understand how it works in the original configuration listed but not in any others. 

 

Thanks in advance for any help and/or advice.

 

Cheers,

 

D

Link to comment
https://www.neowin.net/forum/topic/1319256-corrupted-cat-7-cable-attempted-fix/
Share on other sites

Just now, dunderdo said:

HI, if only as simple, the cable is under a wooden floorboards which run from the front to the back of the apartment, a layer of plywood and the original wooden flooring as well as being routed up through 2 walls.

use the existing cable to pull new cable, tie the cable to the end and pull it through. 

5 minutes ago, sc302 said:

use the existing cable to pull new cable, tie the cable to the end and pull it through. 

This is Plan A, the renovators (who installed the cable) are visiting tomorrow and I am very much hoping this will be possible. I have a bad feeling they may have stapled the thing hence the piercing, if this is the case replacement would require ripping the whole floor up as well as tearing chunks out of my walls and probably uninstalling part of the kitchen (Plan D). 

This is why I had hoped to find a solution by negating the orange pair even though it cost me Gbps connection as a plan B.

Plan C would be to install a wireless access point into switch 2.

 

if they installed the cable, They are responsible for making it work correctly in the first place, they should have tested before floorboards or other fitting had been done to ensure this would not happen.

 

if you have not yet decorated, could you not just pull off the skirting board / baseboard and run a new cable behind?

 

  • Like 2

You can remove any connectors to the cable and test each pair with an Ohm meter if they are no shorted you should see no resistance or very little depending upon how long the run is. Then short each pair at one end -blue orange green brown and then test again with an Ohm meter if any pair is open it will be bad. But if at all possible use it as a pull string..

  • Like 1

If somehow a staple went through the cable - then you might have a hard time using it to pull a new cable through.  But yeah best course of action is replace the cable.

 

I would think if you paid a company to run the cable they should of tested and validated it was good.  But if your saying that they ran it, and then there was more construction - and this is when the cable got damaged.. That would not be fault of the company that laid the cable, but you could prob hold the company that did the added construction to pay for the repair.  If you had warned them that there were cables?  Or the cables were visible when they were doing the new construction of the floors?

 

Bit unclear of the order of events.. But seems you had cable run before the floors were put in?  Did you actually validate the cable worked before the floor construction?

  • Like 1
2 hours ago, BudMan said:

If somehow a staple went through the cable - then you might have a hard time using it to pull a new cable through.  But yeah best course of action is replace the cable.

 

I would think if you paid a company to run the cable they should of tested and validated it was good.  But if your saying that they ran it, and then there was more construction - and this is when the cable got damaged.. That would not be fault of the company that laid the cable, but you could prob hold the company that did the added construction to pay for the repair.  If you had warned them that there were cables?  Or the cables were visible when they were doing the new construction of the floors?

 

Bit unclear of the order of events.. But seems you had cable run before the floors were put in?  Did you actually validate the cable worked before the floor construction?

Most Profession Cable people certify a job when finished. Under normal situation, a cable will not go bad. A good place to look is the last place or area any construction or work was done. I was at a site where all the cables were in a conduit. Running that conduit must have not been easy in a 3 story building..

  • Like 1
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Samsung messages is still alive and well. They reversed that and decided to our more effort into it.
    • I think every American should have a course in a 'dry sense of humour' at school; and perhaps 'using sarcasm in jest' oh, and also 'the use or irony in humour'.
    • What they really need to do is automatically spell "loses" and "lose" correctly since nobody seems to know how to anymore. Then they blame spellcheck/autocomplete and don't realize autocomplete is just filling in the word for them automatically so it was misspelled in the first place.
    • If someone chooses to continue using SB and therefore goes through the manual intervention in the thread, afterwards the BSOD problem is gone. Whether they then re-enable the task doesn't matter, they're done, though on such machines it might pay to keep it disabled in case the next update (if there is a next) causes the same problem. OTOH, if someone disables SB in the BIOS, the problem is also gone. Incidentally, I noticed that this task exists even on machines that don't support SB. It's just installed across the board...and runs. Doing what on such machines is a little hazy.
    • qBittorrent 5.2.2 by Razvan Serea The qBittorrent project aims to provide a Free Software alternative to µtorrent. qBittorrent is an advanced and multi-platform BitTorrent client with a nice user interface as well as a Web UI for remote control and an integrated search engine. qBittorrent aims to meet the needs of most users while using as little CPU and memory as possible. qBittorrent is a truly Open Source project, and as such, anyone can and should contribute to it. qBittorrent features: Polished µTorrent-like User Interface Well-integrated and extensible Search Engine Simultaneous search in most famous BitTorrent search sites Per-category-specific search requests (e.g. Books, Music, Movies) All Bittorrent extensions DHT, Peer Exchange, Full encryption, Magnet/BitComet URIs, ... Remote control through a Web user interface Nearly identical to the regular UI, all in Ajax Advanced control over trackers, peers and torrents Torrents queueing and prioritizing Torrent content selection and prioritizing UPnP / NAT-PMP port forwarding support Available in ~25 languages (Unicode support) Torrent creation tool Advanced RSS support with download filters (inc. regex) Bandwidth scheduler IP Filtering (eMule and PeerGuardian compatible) IPv6 compliant Available on most platforms: Linux, Mac OS X, Windows, OS/2, FreeBSD qBittorrent 5.2.2 changelog: FEATURE: Use D-Bus to show file in file managers (Chocobo1) #24340 BUGFIX: Fix friendlyUnitCompact precision calculation (vafada) #24323 BUGFIX: Remove all top-level folders (glassez) #24333 BUGFIX: Use proper API for checking exit status (Chocobo1) #24349 BUGFIX: Delete stale lockfile when hostname mismatch (TurboTheTurtle, glassez) #24363 BUGFIX: Fix wrong removal procedure of watched folder paths (Chocobo1) #24413 BUGFIX: Don't reannounce before interface changes are applied (glassez) #24447 BUGFIX: Use Latin script for Bosnian locale name (Andy Ye) #24342 WEBUI: Fix performance of global checkbox toggling (tehcneko) #24316 WEBUI: Fix Safari transfer list header misalignment (Piccirello) #24377 WEBUI: Fix error when submitting magnet before metadata loads (Piccirello) #24378 WEBUI: Use correct row id when updating Rss Downloader feed selection (Chocobo1) #24402 WEBUI: Use SameSite=Lax for session cookie to fix cross-site login (Piccirello) #24422 WEBUI: Bring back properties panel expand/collapse button (vafada) #24430 WEBAPI: Only use X-Forwarded-Host header when reverse proxy support is enabled (Chocobo1) #24457 RSSS: Fix "RSS Smart Episode Filter" RegEx (nathanon-akk, glassez) #24398 RSS: Fix previously matched episode format (glassez) #24452 WINDOWS: Fix Python fallback search path (TurboTheTurtle) #24325 WINDOWS: NSIS: Allow to install x64 binary on ARM64 (Chocobo1) #24358 Download: qBittorrent 5.2.2 | 41.1 MB (Open Source) Download: qBittorrent 64-bit installer (qt6) | 43.6 MB Links: qBittorrent Home page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      Twozo Technologies earned a badge
      One Month Later
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
    • One Year In
      Twozo Technologies earned a badge
      One Year In
    • Veteran
      branfont went up a rank
      Veteran
    • Reacting Well
      Almohandis earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      497
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      126
    4. 4
      Steven P.
      85
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!