50M Poor VM Connection, strange TBB quality monitor etc.. - Page 9

Rashboots · 11-12-2012, 08:48

Definitely getting a bit too deep for me! Although I do love learning and having a challenge to face ;-)

The PT took the test hub away last night, so i only have mine to go on now.

He said to ignore the think broadband graphs because the latency caused by the NAS drive shouldnt affect our connection... I don't feel overly comfortable doing that if I'm honest as its my way of knowing what's going on. But the NAS drive needs to be investigated.

I won't let this one beat me!

Sephiroth · 11-12-2012, 09:36

Quote:

Originally Posted by Rashboots

Definitely getting a bit too deep for me! Although I do love learning and having a challenge to face ;-)

The PT took the test hub away last night, so i only have mine to go on now.

He said to ignore the think broadband graphs because the latency caused by the NAS drive shouldnt affect our connection... I don't feel overly comfortable doing that if I'm honest as its my way of knowing what's going on. But the NAS drive needs to be investigated.

I won't let this one beat me!

I'm also disappointed by that answer as it stands. I mean, he's right that the NAS shouldn't have any network impact. But if we've proved that it has network impact, and on the face of it it seems so, then we need to get to the bottom of that.

Also, rewinding a bit, it's the TBB graph that brought the PT in, wasn't it? And it needs explaining. As I said, next step is tpo turn off all SH wireless functions with thr NAS attached and see what that produces.

qasdfdsaq · 11-12-2012, 15:12

Wireshark will tell you what the NAS is sending, and therefore what is causing the latency problem.

Sephiroth · 11-12-2012, 15:39

You'd have to have the NAS mapped onto the PC (which we're keeping off the network to eliminate it from what's going on). But, forgive my ignorance, if the NAS on its own is generating WAN traffic or being called from outside, then where does Wireshark come into it? Clearly I don't know enough about Wireshark.

ferretuk · 11-12-2012, 19:49

Quote:

Originally Posted by Sephiroth

But, forgive my ignorance, if the NAS on its own is generating WAN traffic or being called from outside, then where does Wireshark come into it? Clearly I don't know enough about Wireshark.

You can run Wireshark in promiscuous mode so it captures all network traffic on your LAN that is presented to the PC's network card. However,in this instance, I'm not convinced it would work as the traffic will be unicast and effectively 'filtered' by switch* function of the SH.

*Assuming the 4 LAN ports are part of a switch and not a hub.

Sephiroth · 11-12-2012, 20:14

Thanks. All these years of Wireshark and never reached that!

ferretuk · 11-12-2012, 20:30

Promiscuous mode works really well if you've got a network switch that supports port mirroring...

---------- Post added at 20:30 ---------- Previous post was at 20:27 ----------

Quote:

Originally Posted by Rashboots

But the NAS drive needs to be investigated.

I won't let this one beat me!

Remove the default gateway from the NAS - You'll still be able to access it locally but it won't know about the WAN...

Not sure you've mentioned yet (and apologies if you have) the make and model?

qasdfdsaq · 11-12-2012, 23:18

Quote:

Originally Posted by ferretuk

Promiscuous mode works really well if you've got a network switch that supports port mirroring...

That's why I said get a proper router or connect it via a PC with two network cards.

Sephiroth · 12-12-2012, 08:59

.... and as said, it's getting too complex for the OP. We should stick to belt and braces.