[waqaspai]

I have a few websites hosted, which are working fine on all isps.
Except that a few of my clients have taken dedicated ips from their isps-
they use the same ip to connect to the internet / browse the internet , check email etc -

so unlike a normal user which is given a new ip every time he connects to the internet, my client has a fixed ip.

what is happening is that his website is not visible on his fixed ip , but is working fine when he connect to another isp, or even if he changes the ip of that same isp.

One such client is fpcci.com.pk
he has a fixed ip 202.63.215.248 , but his website is not accessible thru that ip.
However, his isp gave him a new ip : 202.63.215.31 and it seems to work fine and get the website and emails etc.

This is happening to a few more other clients, who have taken fixed ips from various isps - but are unable to get their site on the fixed ip - however when they change their ip or use another isp their website and emails are working fine.

Is my webhost blocking the ip ?
or is it isp related issue ?

I am pasing the result of tracert i did with both the ips :

Traced from 202.63.215.31 (Alternate IP assigned to FPCCI)
C:\Documents and Settings\Administrator>tracert fpcci.com.pk

Tracing route to fpcci.com.pk [66.96.144.174]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms 202.63.215.16
2 <1 ms 1 ms 1 ms 202.63.197.2
3 1 ms 1 ms 1 ms 202.133.70.137
4 2 ms 1 ms 1 ms 203.81.230.141
5 2 ms 2 ms 2 ms tw31-static89.tw1.com [117.20.31.89]
6 2 ms 2 ms 1 ms tw112-static117.tw1.com [221.132.112.117]
7 98 ms 98 ms 98 ms pal6-transworld-2.pal.seabone.net [195.22.198.61]
8 217 ms 217 ms 217 ms new51-new11-racc1.new.seabone.net [195.22.216.193]
9 214 ms 215 ms 215 ms te1-2.ccr02.jfk05.atlas.cogentco.com [154.54.9.25]
10 219 ms 219 ms 219 ms te2-4.ccr04.jfk02.atlas.cogentco.com [154.54.7.9]
11 * * * Request timed out.
12 225 ms 225 ms 226 ms endurance-international-group.demarc.cogentco.com [38.97.106.34]
13 225 ms 224 ms 224 ms 242.252.148.207.static.yourhostingaccount.com [207.148.252.242]
14 222 ms 223 ms 221 ms 174.144.96.66.static.eigbox.net [66.96.144.174]
Trace complete.


Traced from 202.63.215.248/30 (FPCCI official IP pool)
Tracing route to mail.fpcci.com.pk [66.96.144.174]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 202.63.215.250
2 2 ms 1 ms <1 ms 202.63.197.53
3 1 ms <1 ms 1 ms 202.63.197.2
4 1 ms 1 ms 2 ms 202.133.70.137
5 2 ms 1 ms 1 ms 203.81.230.141
6 2 ms 1 ms 2 ms tw31-static89.tw1.com [117.20.31.89]
7 2 ms 2 ms 3 ms tw128-static137.tw1.com [119.63.128.137]
8 98 ms 101 ms 99 ms pal6-transworld-2.pal.seabone.net [195.22.198.61]
9 213 ms 215 ms 213 ms new51-new11-racc1.new.seabone.net [195.22.216.193]
10 217 ms 216 ms 216 ms te1-2.ccr02.jfk05.atlas.cogentco.com [154.54.9.25]
11 * * * Request timed out.
12 224 ms 224 ms 223 ms te2-2.ccr02.bos01.atlas.cogentco.com [154.54.5.242]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Kindly look in to this issue and advice.

[waqaspai]

my webhosting company claims that they are not blocking any ips - and this may be isp related issue.

isp claims that there is not issue with their network and this is hosting related issue.

I am left in a fix.

[JohnWill]

Looks like your ISP has a routing issue in their network.

From the good trace:

9 214 ms 215 ms 215 ms te1-2.ccr02.jfk05.atlas.cogentco.com [154.54.9.25]
10 219 ms 219 ms 219 ms te2-4.ccr04.jfk02.atlas.cogentco.com [154.54.7.9]
11 * * * Request timed out.
12 225 ms 225 ms 226 ms endurance-international-group.demarc.cogentco.com [38.97.106.34]

From the problem trace:

9 213 ms 215 ms 213 ms new51-new11-racc1.new.seabone.net [195.22.216.193]
10 217 ms 216 ms 216 ms te1-2.ccr02.jfk05.atlas.cogentco.com [154.54.9.25]
11 * * * Request timed out.
12 224 ms 224 ms 223 ms te2-2.ccr02.bos01.atlas.cogentco.com [154.54.5.242]
13 * * * Request timed out.
14 * * * Request timed out.

Note that the trace looks fine up to hop 10, then they diverge. Obviously, there is nothing wrong with your machine, and whoever owns that node at hop 10 in the error trace would be the people that I'd be talking to.