We are a services company based in South Asia and our headquarters is
in Singapore and we have branch in India.

We used the services of Burlee (subsequently taken over by Interland
)to host a number of sites on the Internet.  All these sites are
hosted on a Windows 2000 platform.

One of our sites is not accessible by a select IP pool in India. Our
India office uses the services of VSNL, the largest ISP in India. 
However our leased line circuit, which comes under this range of IP
address, is unable to access this site.

We have checked with Burlee.com Support and Interland but they were
not able to help resolve this problem. They have confirmed that they
do not block individual IP addresses on their Windows servers.

We have checked with our ISP VSNL and were informed that they have not
blocked any IP pool and they were also not able to access this site.
Our ISP VSNL had sent a mail to AT & T in this regard but has not
received any reply.

We can ping and trace route but cannot access the Web or the FTP site.

We have just found out that our Singapore office is unable to access
the sites hosted thru two of the ISPs in Singapore.  However, through
Singtel, the largest ISP in Singapore, we are able to access these
same sites.
  
We are very upset with Interland services.  Our interest now is mainly
to sort out this problem.  We believe this could be a common problem
with a whole lot of Burlee/ Interland hosted sites.

Can anyone help resolve why this sort of access problem occurs?

Marrett,

I generally avoid answering specific "fix my broken technology" type
questions simply because without access to the user's system, it is
frequently very hard to test all possible cases of what might be
wrong.

In your case, this may very well be a problem specifically involving
the Burlee/Interland and VSNL computer networks. Without direct access
to these networks and knowledge of the IPs and routing technlogies
involved, it would be very difficult for somebody to do more than
guess at the numerous potential reasons for your access trouble.

/ephraim

Either your ISP or your web host has a firewall in place. Your ISP may
not want their subscribers accessing that IP range or the more than
likely situation is that your web host was not telling the truth. If
you can reach the service by pinging it, but no tcp traffic is
allowed, that is more than likely a firewall issue. Firewalls can
filter based on IP addresses, MAC addresses, Protocols such as
TCP,UDP,ICMP, source ports, and destination ports. If I had to put
money on what was wrong, it would be your web host blocking out that
IP range from connecting to their server. I run PSAD which is a port
scan attack detector and if I see someone sending packets to my
computer and it looks abnormal, I block that IP in my firewall rules
list. Your Webhost probably won't tell you that they are blocking IP
ranges because they know that if you knew they were for sure you would
switch hosting companies.

Eric
Scottsdalehosting.com
A+,CCNA,LinuxSec