I am currently on a college network and trying to get the game Dungeons and Dragons to work. I have been in contact over the past few weeks with the Network Admin here and with Tech support at Turbine (the company that released DDO) and we seemed to have hit a dead end. The network is configured properly to allow me to play the game (right ports are opened), but there seems to be a leak of packets somewhere while connecting to the server. Many other games work fine here and this is the first problem I have encountered. Here is a tracert result:
tracert gls.ddo.com
Tracing route to gls.ddo.com [206.16.13.87]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms core-firewall.oneonta.edu [137.141.2.254]
2 2 ms <1 ms 1 ms gateway-internet.oneonta.edu [137.141.1.254]
3 1 ms 1 ms 1 ms rrcs-24-97-70-21.nys.biz.rr.com [24.97.70.21]
4 14 ms 16 ms 20 ms srp0-0.bnghnyplz-rtr04.nyroc.rr.com [24.94.34.14
7]
5 1977 ms 9 ms 2961 ms srp8-0.bnghnyplz-rtr02.nyroc.rr.com [24.94.32.90
]
6 13 ms 13 ms 13 ms son0-0-2.albynywav-rtr03.nyroc.rr.com [24.92.224
.162]
7 15 ms 13 ms 2967 ms pop1-alb-p2-0.atdn.net [66.185.133.233]
8 13 ms 14 ms 14 ms bb1-alb-p0-0.atdn.net [66.185.148.96]
9 17 ms 16 ms 16 ms bb2-nye-p3-0.atdn.net [66.185.152.71]
10 18 ms 16 ms 18 ms pop2-nye-p1-0.atdn.net [66.185.151.67]
11 20 ms 21 ms 322 ms aol-gw.n54ny.ip.att.net [192.205.32.217]
12 25 ms 2635 ms 22 ms tbr1-p010401.n54ny.ip.att.net [12.123.3.57]
13 20 ms 20 ms 19 ms gar4-p300.n54ny.ip.att.net [12.123.3.2]
14 24 ms 23 ms 24 ms mdf1-gsr12-2-pos-7-0.bos1.attens.net [12.122.255
.134]
15 23 ms 23 ms 24 ms 12.130.0.126
16 25 ms 26 ms 27 ms 12.130.10.69
17 27 ms 27 ms 29 ms 206.16.13.87
Trace complete.
I wasn't sure if there was any way to track down specific problems from a tracert report. I doubt there is, but I figured I would ask.
Thanks everyone!
tracert gls.ddo.com
Tracing route to gls.ddo.com [206.16.13.87]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms core-firewall.oneonta.edu [137.141.2.254]
2 2 ms <1 ms 1 ms gateway-internet.oneonta.edu [137.141.1.254]
3 1 ms 1 ms 1 ms rrcs-24-97-70-21.nys.biz.rr.com [24.97.70.21]
4 14 ms 16 ms 20 ms srp0-0.bnghnyplz-rtr04.nyroc.rr.com [24.94.34.14
7]
5 1977 ms 9 ms 2961 ms srp8-0.bnghnyplz-rtr02.nyroc.rr.com [24.94.32.90
]
6 13 ms 13 ms 13 ms son0-0-2.albynywav-rtr03.nyroc.rr.com [24.92.224
.162]
7 15 ms 13 ms 2967 ms pop1-alb-p2-0.atdn.net [66.185.133.233]
8 13 ms 14 ms 14 ms bb1-alb-p0-0.atdn.net [66.185.148.96]
9 17 ms 16 ms 16 ms bb2-nye-p3-0.atdn.net [66.185.152.71]
10 18 ms 16 ms 18 ms pop2-nye-p1-0.atdn.net [66.185.151.67]
11 20 ms 21 ms 322 ms aol-gw.n54ny.ip.att.net [192.205.32.217]
12 25 ms 2635 ms 22 ms tbr1-p010401.n54ny.ip.att.net [12.123.3.57]
13 20 ms 20 ms 19 ms gar4-p300.n54ny.ip.att.net [12.123.3.2]
14 24 ms 23 ms 24 ms mdf1-gsr12-2-pos-7-0.bos1.attens.net [12.122.255
.134]
15 23 ms 23 ms 24 ms 12.130.0.126
16 25 ms 26 ms 27 ms 12.130.10.69
17 27 ms 27 ms 29 ms 206.16.13.87
Trace complete.
I wasn't sure if there was any way to track down specific problems from a tracert report. I doubt there is, but I figured I would ask.
Thanks everyone!