View Single Post
Old 12-21-2007, 01:15 AM   #6
Appeselve

Join Date
Oct 2005
Posts
520
Senior Member
Default
I wouldn't do that at all - don;t rule out first line support, they have and do spot lots of errors that people forget or don't think important. Like DSL dropping out becuase a sky box is on the line and unfiltered. You'd be suprised at how many times when I was doing 3rd line support that the customer hand't actually done anything which first line had asked them to, such as reboot modems etc...

If I was you, I'd monitor pings, and tracerts to set IPs throughout the day (say 5 ip of game servers not all on the same host/network). Then email that to their support team. You can prove during the day network performance is ok, and that it's unlikely to be an error on your property / config as it's time related. Then you can prove that during peak hours, the connection is saverly lagged / oversubscribed.

Tracerts will also point the finger at certain switches / routers that could need looking at.
Have actually done stuff like tracerts before in order to help BT tech support identify stuff, and although I dont consider myself silly enough to make the kind of errors that an average customer would make I see no harm in collecting the data before I contact them at least.

As a previous support person exactly what do you recomend I send to them? I actually have forgotten how to do a tracert for a start since its been that long . Something like tracert in cmd or something isnt it? And you need to find the ip's of different things to test? Its mainly my wow server I am sorried about though its a global problem with all pings so I wonder how I could get the ip of my wow server...
Appeselve is offline


 

All times are GMT +1. The time now is 03:44 PM.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Design & Developed by Amodity.com
Copyright© Amodity