imperium2335
Members-
Posts
24 -
Joined
-
Last visited
Content Type
Forums
News
20th
EduGeek EDIT Conference
Blogs
Everything posted by 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.
-
We only have one Because we are a small/medium business at the moment and not heavily web based just yet.
-
Could it be caused by one of the workstations? perhaps a virus or something that is constantly sending out loads of traffic? But I can't see how a client on a 100mbps would saturate 1gbps :/
-
Staffordshire
-
Unfortunately not We would have to order another one in only if I can confirm this one is broken.
-
Thanks, I will have a look tomorrow and hopefully all is well.
-
What's a good way to check for excessive packets or loop backs?
-
But why would the internet fail? Since the server and router are not connected to each other, they are both on separate ports on the switch BTW, each workstation is configured with the server as primary DNS, and the router as secondary DNS.
-
Hi Angry, Yes, the server contains files that are shared to users. If I constantly ping, I see that every 5 to 10 mins, I get no response from the server address, can't access the net either, which is why I think it's some kind of congestion? Someone suggest VLANs might be a solution but I don't see how that could apply here since the network is in one building with everyone working together.
-
Hi, We have had our network setup for a few months and was all working well. But now for no apparent reason, all workstations lose connection to the server and all the shared resources etc for about 10 seconds every 5 to 10 minutes but can be less frequent, it seems random.. For some strange reason, connection to the internet is also lost at the same time. I have ruled out the 2 switches on the network as I am able to continually ping workstations throughout the building with no disruption. We have a switch on the ground floor which is connected to the switch in the top floor via a cat6 cable on a 1gbps port. The server is then connected to the switch on the ground floor to the other 1gbps port, all other workstations are connected to the other 100mbps ports. Both switches are Netgear Prosafe 48port switches. The router is connected to one of the 100mbps ports. We also have a phone server that is attached to one of the 100mbps ports (which I can ping continuously fine). We have about 40 PCs, 40 ip phones and 8 printers on the network. Any help is much appreciated.
