our sites cannot be seen by clients of certain isp [Archive]

View Full Version : our sites cannot be seen by clients of certain isp

hotwired

10-15-2004, 04:28 PM

The problem…

clients of certain isp cannot connect to my sites

Have any of you yet had the problem where no one from a particular isp could:
1. see any of your websites
2. engage in any email via your mail server

(this includes clients of that isp as well as workers there)
I've got one such problem with prexar.com - In fact, I challenge any of you to get an email thru to anyone there. support@prexar.com is valid if you want to try. I've been going back and forth for 2 months now and Manny is currently on the job trying to finally track it down but I thought I'd check in the forum to see if anyone else had ever had this happen. We know what it's NOT

1. nameservers are squeaky clean
2. our ips are not blocked at prexar
3. prexars ips are not "obviously" blocked at hostdime
4. prexar does not subscribe to any spam lists which would cause this.

It may be a network issue on either side but each side says it's the other!

sawbuck

10-15-2004, 05:19 PM

Originally posted by hotwired
We know what it's NOT
1. nameservers are squeaky clean
Maybe. Doing a dig on prexar.com returns this:

; <<>> DiG 9.2.1 <<>> prexar.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13985
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;prexar.com. IN A
;; ANSWER SECTION:
prexar.com. 520 IN A 142.167.5.14
;; AUTHORITY SECTION:
com. 153758 IN NS C.GTLD-SERVERS.NET.
com. 153758 IN NS D.GTLD-SERVERS.NET.
com. 153758 IN NS E.GTLD-SERVERS.NET.
com. 153758 IN NS F.GTLD-SERVERS.NET.
com. 153758 IN NS G.GTLD-SERVERS.NET.
com. 153758 IN NS H.GTLD-SERVERS.NET.
com. 153758 IN NS I.GTLD-SERVERS.NET.
com. 153758 IN NS J.GTLD-SERVERS.NET.
com. 153758 IN NS K.GTLD-SERVERS.NET.
com. 153758 IN NS L.GTLD-SERVERS.NET.
com. 153758 IN NS M.GTLD-SERVERS.NET.
com. 153758 IN NS A.GTLD-SERVERS.NET.
com. 153758 IN NS B.GTLD-SERVERS.NET.

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Oct 15 14:18:00 2004
;; MSG SIZE rcvd: 268

dig prexar.com @142.167.5.14
; <<>> DiG 9.2.1 <<>> prexar.com @142.167.5.14
;; global options: printcmd
;; connection timed out; no servers could be reached

eWebtricity

10-17-2004, 12:26 AM

Something else to try, is a ping from the client site to your web / email server if it works then you know the "highway" is there and they aren't blocking you by IP address.

Then try a telnet to port 80 like this

debian:/home# telnet 69.20.37.114 80

Then type this after it connects (if it connects)

get index.html

It should look somthing like this

debian:/home# telnet 69.20.37.114 80
Trying 69.20.37.114...
Connected to 69.20.37.114.
Escape character is '^]'.
get index.html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>400 Bad Request</TITLE>
</HEAD><BODY>
<H1>Bad Request</H1>
Your browser sent a request that this server could not understand.<P>
Invalid URI in request get index.html<P>
<HR>
<ADDRESS>Apache/1.3.28 Ben-SSL/1.51 Server at www.webhostingtalk.com Port 80</ADDRESS>
</BODY></HTML>
Connection closed by foreign host.
debian:/home#

If you get the same results as above then it's not the ISP and it's not your server, it's something on the client side.