imperium2335

never mind still have massive latencies occasionally

RIP was off, would that have made a difference? It's on now and seems to be well :/

Thanks for your advice, going to buy another router in a moment. So is it bad practise to have the router set as one of the DNS servers in a client config? Should I just have the server as the DNS?

Here are the trace routes from my workstation to a computer on the top floor ( me > switch > switch > workmate) And then me > switch > server : Tracing route to Halil-Turkey [192.168.0.8] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms Halil-Turkey [192.168.0.8] Trace complete. C:\Users\Tom>tracert 192.168.0.253 Tracing route to EAL-CORE [192.168.0.253] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms EAL-CORE [192.168.0.253] Trace complete.

That is my workstation > switch > router I believe.

Here is a trace route btw: Tracing route to 192.168.0.1 over a maximum of 30 hops 1 414 ms 284 ms 608 ms 192.168.0.1 Trace complete.

Getting the same sorts of numbers from different machines. When it goes that high our IP phones cut off too and the internet becomes unavailable. It will be fine for a few minutes, latency under 1ms, then suddenly we get a surge for a minute or two of high latencies. Could the router be creating lots of unnecessary traffic? This only seems to happen when we have lots of people logged on, like now, this morning when only a few staff were on it was working fine.

This is what I get when pinging the router... Reply from 192.168.0.1: bytes=32 time=822ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1778ms TTL=64 Reply from 192.168.0.1: bytes=32 time=806ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1241ms TTL=64 Reply from 192.168.0.1: bytes=32 time=537ms TTL=64 Reply from 192.168.0.1: bytes=32 time=688ms TTL=64 Reply from 192.168.0.1: bytes=32 time=418ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1002ms TTL=64 Reply from 192.168.0.1: bytes=32 time=926ms TTL=64 Reply from 192.168.0.1: bytes=32 time=299ms TTL=64 Reply from 192.168.0.1: bytes=32 time=609ms TTL=64 Request timed out. Reply from 192.168.0.1: bytes=32 time=380ms TTL=64 Reply from 192.168.0.1: bytes=32 time=436ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1056ms TTL=64 Reply from 192.168.0.1: bytes=32 time=886ms TTL=64 Ping statistics for 192.168.0.1: Packets: Sent = 338, Received = 314, Lost = 24 (7 Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 2537ms, Average = 433ms

Ok, thanks for all your help! The staff will be coming in soon so hopefully the problem has passed and shit doesn't hit the fan once again

is an average of 4400 packets per second a lot?

I've downloaded this thing called wireshark, would it help if I posted some of the results from it from my server?

Thanks, I'll have another stab at VLANs. Tried it yesterday but couldn't get the printers to work properly. Shared resources like printers, server and router all need to be in every group am I right in thinking?

Hi, How do I reduce or eliminate this ARP traffic?

Nothing weird in the server event logs, except a lot of XPS print failures from my workstation under 'System' logs

The switch in the cab has 48 10/100 ports, about half are taken up.