ssaya wrote:Can't connect using either of those ip's for the realmslist.
tried ipconfig release/renew and flushdns
Do a traceroute to 5.135.143.130
type this in command prompt and copy/paste the output
tracert 5.135.143.130
here is my output (and i can successfully ping it)
Tracing route to ns2343269.ovh.net [5.135.143.130]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 172.16.81.252
2 2 ms 2 ms 1 ms 208.68.224.254
3 * * * Request timed out.
4 4 ms 4 ms 5 ms host-198-7-224-105.oshean.org [198.7.224.105]
5 8 ms 4 ms 4 ms xe-4-3-0.bar1.boston1.level3.net [4.53.54.21]
6 9 ms 9 ms 9 ms ae-1-51.edge3.newark1.level3.net [4.69.156.11]
7 9 ms 9 ms 9 ms ae-1-51.edge3.newark1.level3.net [4.69.156.11]
8 * * * Request timed out.
9 21 ms 19 ms 19 ms 192.99.146.84
10 18 ms 18 ms 20 ms vac3-0-a9.qc.ca.vaccum [198.27.73.245]
11 18 ms 18 ms 18 ms vac3-1-n7.qc.ca.firewall [198.27.73.242]
12 22 ms 17 ms 17 ms vac3-2-n7.qc.ca.tilera [198.27.73.247]
13 18 ms 18 ms 18 ms vac3-3-n7.qc.ca [198.27.73.237]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 110 ms 110 ms 110 ms ns2343269.ovh.net [5.135.143.130]
Trace complete.
I live in Rhode Island so it shoots up to Boston, MA, down to Newark, NJ, up to Quebec, Canada and then across the Atlantic Ocean to Europe.