Need Help with DSL Please

[Laddyboy]

Ok, here is the situation. we got bellsouth ADSL at work as our main connection to the internet. It works fine except if we try to go to www.ups.com or www.fedex.com. we get an error 45 (I think)
We called bellsouth and they can't figure it out...we called UPS and they can't figure it out either...UPS says all is ok on there side...now here is where it really gets weird. We tried the dail-up, back up for Bellsouth and have the same problem...but I dialed into there other server and it works...Anyone have any clue what is up with this. Bellsouth says there DNS servers are up and working fine....Your help is needed.

Thanks

Laddyboy

 

[LordOfAll]

what exactly happens when you try?
Try a trace to that addy.
1. Open DOS box.
2. Type tracert www.ups.com or tracert www.fedex.com

The IP for ups is 153.2.228.50 try a trace to that.

If you can't get an IP by tracing the name it is a DNS issue.

 

[Laddyboy]

when we ping the ip address or www.ups.com it just times out.

we figured it was a DNS problem but Bellsout keeps saying there servers are fine. If I can go to them with more direct information about what the problem might be maybe we can get this resolved more quickley. Any suggestion on what to have them check on the DNS server?

Thanks

 

[Dag]

The ping is just a generic yes or no. Try the trace route that LordOfAll suggested. It will tell you EXACTLY who is dropping the ball on your way to www.ups.com. When you tell Bell South which router is dropping you (it may or may not be them) they should be able to track it down. You can also use something like ping plotter or visual route to trace it with.

Dag

 

[Laddyboy]

I will try that tomorrow when I get to work. Looking at my boss's note this morning, he already tried that, but I will seet what results he got and post back here. BTW, I just started there on Monday.

Laddyboy

 

[perry]

I'm on a Bellsouth ADSL line here at home. Both www.ups.com and www.fedex.com are working just fine in my browser. Traceroute to www.ups.com dies at outpost.ups.com (192.55.236.20). Traceroute to www.fedex.com doesn't make it to any fedex.com address. Wierd.

Trying them both from a friend's computer (cable modem). Same problem.

Trying them both from my webhosting account. Woops. Don't have the permissions to do that.

I guess it is something that is repeatable that you can complain to Bellsouth about.

 

[Laddyboy]

OK, I ran tracert on www.ups.com from our office and the request times out. do you think there could be something wrong on our end where it is not even getting out.

Laddyboy

 

[FullMoon]

Reinstall Internet Browser...

 

[Laddyboy]

it is on all 30 machines...so I doubt it is the browser

 

[abracadabra1]

nope!
i second that! same problem w/ my dsl. not the fedex problem, but i do get the ups problem.
there is no way for me to connect to ups.com. interestinly enough, i can connect to the job openings and other sites within ups.
here's a tracert i ran to ups.com


1 14 ms 17 ms 14 ms adsl-61-44-1.mia.bellsouth.net [208.61.44.1]
2 14 ms <10 ms 14 ms 209.215.49.65
3 14 ms 14 ms <10 ms 205.152.144.203
4 13 ms 14 ms 14 ms 500.Pos3-1.GW2.MIA4.ALTER.NET [157.130.80.49]
5 14 ms 27 ms 28 ms 155.at-6-0-0.XR2.ATL5.ALTER.NET [146.188.233.190
]
6 28 ms 27 ms 28 ms 192.ATM3-0.TR2.ATL1.ALTER.NET [152.63.80.234]
7 41 ms 41 ms 55 ms 109.at-6/0/0.TR2.DCA8.ALTER.NET [146.188.138.190
]
8 41 ms 41 ms 55 ms 152.63.35.250
9 55 ms 42 ms 41 ms 188.ATM4-0.BR2.DCA8.ALTER.NET [152.63.35.193]
10 41 ms 41 ms 41 ms uu-gw.wswdc.ip.att.net [192.205.32.133]
11 41 ms 41 ms 41 ms gbr4-p50.wswdc.ip.att.net [12.123.9.54]
12 55 ms 55 ms 55 ms gbr4-p90.attga.ip.att.net [12.122.2.177]
13 55 ms 55 ms 55 ms gbr1-p60.attga.ip.att.net [12.122.5.209]
14 55 ms 55 ms 68 ms ar13-a3120s1.attga.ip.att.net [12.123.21.13]
15 55 ms 68 ms 69 ms 12.124.55.30
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20

 

[perry]

Me thinks that ups.com has a firewall and won't let the traceroutes through. Mine have died at outpost.ups.com and pyro.ups.com. Here's the latest:

Tracing route to ups.com [153.2.228.50]
over a maximum of 30 hops:

1 30 ms 20 ms 20 ms adsl-78-140-1.atl.bellsouth.net [216.78.140.1]
2 10 ms 10 ms 20 ms 209.149.96.65
3 10 ms 10 ms 10 ms 205.152.37.248
4 10 ms 10 ms 10 ms 500.POS3-1.GW6.ATL3.ALTER.NET [157.130.216.41]
5 10 ms 10 ms 20 ms 150.ATM3-0.XR1.ATL1.ALTER.NET [146.188.233.210]

6 10 ms 10 ms 10 ms 295.ATM2-0.TR1.ATL1.ALTER.NET [146.188.232.90]
7 30 ms 31 ms 30 ms 109.at-6-0-0.TR1.DCA8.ALTER.NET [146.188.138.138
]
8 30 ms 30 ms 30 ms 0.so-5-0-0.XR1.DCA8.ALTER.NET [152.63.25.38]
9 30 ms 30 ms 30 ms 189.ATM5-0.BR2.DCA8.ALTER.NET [152.63.35.189]
10 30 ms 30 ms 30 ms uu-gw.wswdc.ip.att.net [192.205.32.133]
11 30 ms 30 ms 30 ms gbr4-p50.wswdc.ip.att.net [12.123.9.54]
12 40 ms 50 ms 40 ms gbr4-p10.attga.ip.att.net [12.122.2.161]
13 40 ms 51 ms 40 ms gbr2-p100.attga.ip.att.net [12.122.1.198]
14 40 ms 50 ms 40 ms ar13-a300s2.attga.ip.att.net [12.123.21.17]
15 50 ms 40 ms 40 ms 12.124.55.30
16 50 ms * 50 ms pyro.ups.com [207.24.0.25]

Then it died... Seeing a couple of complaints, I don't think that this is the cause of Laddyboy's troubles. Gotta be something else. Dunno what, but I don't think that these traceroutes are gunna explain anything.

Laddyboy, see if you can ping 207.24.0.25. Copy that traceroute in here and let's see what you get.

How long has that problem been going on?

 

[Laddyboy]

All fixed guys...here is what was going on. After UPS said it wasn't them and Bellsouth said it wasn't them. I did the tracert and found out it was getting dropped in NJ just like other people were getting. Apparently there is a forum just on this on Bellsouth's news group. Anyway. I called UPS and told them I was getting dropped from there server in NJ and if they could take another look at it. Well they called back and found out that they blocked those IP address because they were getting hacked into. They rerouted us through another server and we are back in business. Thanks to all that help me out.

Laddyboy