Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 1015894" data-attributes="member: 18896">At least you had the knowledge that it 'worked' on your LAN, because fixing something when you can fallback on a working setup to compare agaist is much better then to be totally in the dark.&nbsp;Now that you have narrowed things down more a few suggestions come to mind. Importing a collection, no matter how small creates a ton of connections. A bad cable can easaly cause little 'jitter' to occur, just enough to upset a mass connection import process as the one MP-TVSeries does with TheTVdB. Forcing 100Mbps Full Duplex and not allow 1Gbps auto-detect can sometimes be enough to fix that. And these connection issues on a bad cable are exactly what you experiece. It will work 80% of the time, but then be intermittend for the other 20%. Enough to pull your hair out.&nbsp;And it might not even be the cable itself (although it is most often the case), but I've seen it go wrong with a NIC driver, NIC settings, BIOS (when NIC is onboard), and even as crazy as a printer driver that was conflicting.</blockquote>

[QUOTE="RoChess, post: 1015894, member: 18896"] At least you had the knowledge that it 'worked' on your LAN, because fixing something when you can fallback on a working setup to compare agaist is much better then to be totally in the dark. Now that you have narrowed things down more a few suggestions come to mind. Importing a collection, no matter how small creates a ton of connections. A bad cable can easaly cause little 'jitter' to occur, just enough to upset a mass connection import process as the one MP-TVSeries does with TheTVdB. Forcing 100Mbps Full Duplex and not allow 1Gbps auto-detect can sometimes be enough to fix that. And these connection issues on a bad cable are exactly what you experiece. It will work 80% of the time, but then be intermittend for the other 20%. Enough to pull your hair out. And it might not even be the cable itself (although it is most often the case), but I've seen it go wrong with a NIC driver, NIC settings, BIOS (when NIC is onboard), and even as crazy as a printer driver that was conflicting. [/QUOTE]

Verification