eircom link/routing problems

ednwireland

i have a problem connecting to a specific isp in the states their mailservers to be specific if i dialin using utv or indigo no probs but i dial in with eircom free or pay accounts then i can't connect to these addresses ? the address is 216.119.106.129
just find it weird that this problem only occurs when i dial into eircom and route through the sligo routers
eircom support don't get the problem routing out through dublin

anyone any ideas as to why this would happen.

Frank Grimes

When you say connecting to them, do you mean you can't check/send mail via that IP address you posted, or that you cannot ping/trace to it when dialled into Eircom?
If you can ping/trace to it, is it possible that the ISP has some sort of IP restrictions on the mailserver that could be causing it?
If you can't fully trace to it, post the traces here.

ednwireland

cant connect to mailservers ping nothing to those specific ip's using eircom or eircomfree (which link us through eircom sligo node ), any other isp i've tried is ok

traceroute example

Tracing route to mail12.webcontrolcenter.com [216.119.106.128]
over a maximum of 30 hops:

1 109 ms 126 ms 114 ms as1.sligo1.eircom.net [159.134.238.250]
2 119 ms 114 ms 126 ms fe0-0.edge1.rtd.sligo.eircom.net [159.134.248.11
4]
3 141 ms 127 ms 126 ms 159.134.125.37
4 129 ms 127 ms 120 ms 159.134.125.33
5 202 ms 197 ms 191 ms pos5-0-0.core1.8av.newyork.eircom.net [159.134.1
91.106]
6 213 ms 202 ms 196 ms 206.24.193.157
7 204 ms 203 ms 190 ms agr3-loopback.NewYork.cw.net [206.24.194.103]
8 188 ms 203 ms 203 ms dcr1-so-6-2-0.NewYork.cw.net [206.24.207.57]
9 199 ms 185 ms 203 ms above-gw.cgcil.ip.att.net [192.205.32.197]
10 193 ms 189 ms 204 ms tbr1-p010401.n54ny.ip.att.net [12.123.3.57]
11 223 ms 222 ms 210 ms tbr1-p012101.cgcil.ip.att.net [12.122.10.2]
12 223 ms 209 ms 216 ms tbr2-p012501.cgcil.ip.att.net [12.122.9.134]
13 214 ms 223 ms 216 ms tbr2-p012301.sl9mo.ip.att.net [12.122.10.46]
14 254 ms 245 ms 258 ms tbr2-p012501.dlstx.ip.att.net [12.122.10.89]
15 282 ms 260 ms 267 ms gbr2-p30.phmaz.ip.att.net [12.122.2.106]
16 260 ms 267 ms 261 ms gar2-p370.phmaz.ip.att.net [12.123.142.49]
17 289 ms 274 ms 266 ms 12.125.99.94
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.


working example follows

Tracing route to mail14.webcontrolcenter.com [216.119.106.130]
over a maximum of 30 hops:

1 149 ms 159 ms 149 ms 194.125.144.87
2 170 ms 148 ms 149 ms 194.125.144.41
3 140 ms 229 ms 148 ms 194.125.144.185
4 180 ms 169 ms 158 ms fe1-1-0.core2.adl.dublin.eircom.net [159.134.240
.12]
5 179 ms 179 ms 159 ms pos0-7.corea.cra.dublin.eircom.net [159.134.192.
245]
6 220 ms 249 ms 219 ms pos5-0-0.core1.8av.newyork.eircom.net [159.134.1
91.106]
7 239 ms 228 ms 219 ms 206.24.193.157
8 230 ms 219 ms 228 ms agr3-loopback.NewYork.cw.net [206.24.194.103]
9 249 ms 229 ms 229 ms dcr1-so-6-2-0.NewYork.cw.net [206.24.207.57]
10 230 ms 239 ms 249 ms above-gw.cgcil.ip.att.net [192.205.32.197]
11 251 ms 217 ms 249 ms tbr1-p010401.n54ny.ip.att.net [12.123.3.57]
12 271 ms 238 ms 247 ms tbr1-p012101.cgcil.ip.att.net [12.122.10.2]
13 261 ms 237 ms 230 ms tbr2-p012501.cgcil.ip.att.net [12.122.9.134]
14 280 ms 239 ms 239 ms tbr2-p012501.sl9mo.ip.att.net [12.122.10.10]
15 261 ms 259 ms 258 ms tbr2-p012501.dlstx.ip.att.net [12.122.10.89]
16 290 ms 268 ms 298 ms gbr2-p40.phmaz.ip.att.net [12.122.10.86]
17 310 ms 288 ms 268 ms gar2-p370.phmaz.ip.att.net [12.123.142.49]
18 300 ms 288 ms 279 ms 12.125.99.94
19 301 ms 308 ms 299 ms 216.119.107.1
20 370 ms 374 ms 409 ms 216.119.107.10
21 300 ms 289 ms 264 ms 216.119.107.14
22 280 ms 269 ms 289 ms mail14.webcontrolcenter.com [216.119.106.130]

Trace complete.

any ideas as to whats going on welcome

lynchie

Below is a traceroute from Eircom I-Stream. You can see that the site is reachable but also the route taken is different. So the original route must be screwed up and the packets are now being routed over sprintlink instead. Try and trace it again.

Tracing route to mail12.webcontrolcenter.com [216.119.106.128]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms xxxx [192.168.1.1]
2 <10 ms <10 ms <10 ms xxxx [192.168.7.1]
3 47 ms 46 ms 47 ms virtual.bas1.dbn.dublin.eircom.net [159.134.155.
4]
4 94 ms 62 ms 110 ms fe0-0.edge1.dbn.dublin.eircom.net [159.134.155.8
1]
5 63 ms 109 ms 266 ms pos0-0-0.core1.thn.london.eircom.net [159.134.19
1.98]
6 172 ms 63 ms 94 ms sl-gw22-lon-2-6.sprintlink.net [213.206.130.37]

7 203 ms 78 ms 63 ms sl-bb21-lon-9-0.sprintlink.net [213.206.128.98]

8 156 ms 141 ms 187 ms sl-bb21-tuk-10-0.sprintlink.net [144.232.19.69]

9 141 ms 141 ms 265 ms sl-bb23-pen-10-3.sprintlink.net [144.232.20.118]

10 235 ms 250 ms 140 ms sl-bb22-pen-14-0.sprintlink.net [144.232.8.178]

11 172 ms 281 ms 188 ms sl-bb21-fw-15-0.sprintlink.net [144.232.9.31]
12 203 ms 187 ms 188 ms sl-bb20-fw-14-0.sprintlink.net [144.232.11.217]

13 172 ms 187 ms 172 ms sl-bb22-fw-14-0.sprintlink.net [144.232.11.225]

14 250 ms 203 ms 219 ms sl-bb22-ana-8-1.sprintlink.net [144.232.9.249]
15 203 ms 203 ms 234 ms sl-gw15-ana-10-0.sprintlink.net [144.232.1.218]

16 203 ms 203 ms 219 ms sl-timewarner-3-0.sprintlink.net [144.232.192.34
]
17 203 ms 203 ms 219 ms core-01-ge-0-3-0-0.lsag.twtelecom.net [168.215.5
4.89]
18 203 ms 360 ms 218 ms core-01-so-0-0-0-0.phnx.twtelecom.net [168.215.5
5.114]
19 219 ms 203 ms 250 ms hagg-01-ge-0-3-0.phnx.twtelecom.net [209.234.146
.46]
20 188 ms 250 ms 281 ms 207.250.65.142
21 187 ms 235 ms 281 ms 216.119.107.1
22 250 ms 250 ms 391 ms 216.119.107.10
23 250 ms 203 ms 360 ms 216.119.107.14
24 297 ms 266 ms 219 ms mail12.webcontrolcenter.com [216.119.106.128]

ednwireland

nope still doesn't work when routed out through eircom sligo node ( i know it works from eircom'd dublin node)
must be something with routing across to eircom new york node as all the other routes go across via london eircom node and work !