Date: Wed, 17 Jan 2001 18:01:53 -0700 (MST) From: "Forrest W. Christian" <forrestc@imach.com> To: J & C Frazier <admin@csocs.com> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Problems with sendmail and NSI Message-ID: <Pine.BSF.4.21.0101171755000.22366-100000@workhorse.iMach.com> In-Reply-To: <3A663DD1.ADD8C36D@csocs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
You need to get in touch with CAble and wireless and/or internic and have them troubleshoot this. I can traceroute all the way there: Type escape sequence to abort. Tracing the route to ns1.netsol.com (216.168.224.200) 1 bordercore3-serial5-0-12.Denver.cw.net (166.48.100.49) [AS 3561] 44 msec 36 msec 28 msec 2 acr2.Denverden.cw.net (208.172.162.62) [AS 3561] 32 msec 60 msec 40 msec 3 acr1-loopback.Restonrst.cw.net (206.24.178.61) [AS 3561] 80 msec 68 msec 80 msec 4 bar1-loopback.Restonrst.cw.net (206.24.178.3) [AS 3561] 136 msec 176 msec 144 msec 5 network-solutions-inc.Restonrst.cw.net (206.24.181.134) [AS 3561] 136 msec 164 msec 168 msec 6 * 216.168.224.4 [AS 6245] 116 msec 116 msec 7 ns1.netsol.com (216.168.224.200) [AS 6245] 124 msec * 80 msec It appears there is some sort of filter or routing problem on either hop 4 or 5 above (your hop 5 or 6) in relation to your IP address. I would suspect a corrupted routing entry in network solutions router (hop 5 above) for your route, OR a filter in either 4 or 5 above. If you can get a hold of network solution's network engineer, have them check the route on their router for you. On Wed, 17 Jan 2001, J & C Frazier wrote: > Date: Wed, 17 Jan 2001 17:50:25 -0700 > From: J & C Frazier <admin@csocs.com> > To: Forrest W. Christian <forrestc@imach.com> > Cc: freebsd-isp@FreeBSD.ORG > Subject: Re: Problems with sendmail and NSI > > # traceroute ns1.netsol.com > traceroute to ns1.netsol.com (216.168.224.200), 30 hops max, 40 byte packets > 1 cw-gateway20.colocateusa.net (207.49.20.1) 2.167 ms 3.106 ms 3.305 ms > 2 bar2-serial4-0-0-12-0.Washingtondck.cw.net (206.24.234.65) 12.522 ms 4.748 > ms 4.979 ms > 3 acr2-loopback.Washingtondck.cw.net (206.24.226.62) 5.420 ms 5.669 ms 8.822 > ms > 4 acr1-loopback.Restonrst.cw.net (206.24.178.61) 19.793 ms 25.926 ms 9.228 > ms > 5 bar1-loopback.Restonrst.cw.net (206.24.178.3) 13.981 ms 18.486 ms 10.529 > ms > 6 * * * > > "Forrest W. Christian" wrote: > > > Looks like your upstream is Cable and Wireless and this address is > > from their block (a /14 to be specific). I can get to your port > > fine, but again, I'm directly connected to cable and wireless as one of > > our upstreams. > > > > The symptoms below are consistent with some sort of routing issue. The > > DNS timeouts mean the DNS queries are not getting to their destination, > > which is consistent with your telnet timing out. > > > > Have you tried a traceroute to ns1.netsol.com? Where does it die? > > > > On Wed, 17 Jan 2001, J & C Frazier wrote: > > > > > Date: Wed, 17 Jan 2001 17:30:24 -0700 > > > From: J & C Frazier <admin@csocs.com> > > > To: Forrest W. Christian <forrestc@imach.com> > > > Cc: Edwin Culp <eculp@EnContacto.Net>, freebsd-isp@FreeBSD.ORG > > > Subject: Re: Problems with sendmail and NSI > > > > > > The IP is 207.49.21.231 (csocs.com). Also note the following: > > > > > > # nslookup > > > Default Server: localhost.csocs.com > > > Address: 127.0.0.1 > > > > > > > networksolutions.com > > > Server: localhost.csocs.com > > > Address: 127.0.0.1 > > > Non-authoritative answer: > > > Name: networksolutions.com > > > Address: 216.168.224.69 > > > > > > > ns1.netsol.com > > > Server: localhost.csocs.com > > > Address: 127.0.0.1 > > > Non-authoritative answer: > > > Name: ns1.netsol.com > > > Address: 216.168.224.200 > > > > > > > server ns1.netsol.com > > > Default Server: ns1.netsol.com > > > Address: 216.168.224.200 > > > > > > > csocs.com > > > Server: ns1.netsol.com > > > Address: 216.168.224.200 > > > *** Request to ns1.netsol.com timed-out > > > > > > > networksolutions.com > > > Server: ns1.netsol.com > > > Address: 216.168.224.200 > > > *** Request to ns1.netsol.com timed-out > > > > > > This tells me there's evidently some sort of dns issue I guess. > > > > > > J.C. Frazier > > > > > > > > > "Forrest W. Christian" wrote: > > > > > > > If you don't have TCP connectivity between you and them, there is > > > > definately some sort of routing or filtering issue between point a and b. > > > > > > > > Would you be kind enough to (perhaps privately) send me the IP address of > > > > the machine in question so I can see what it looks like routing-wise from > > > > here (perhaps I can see something). > > > > > > > - Forrest W. Christian (forrestc@imach.com) AC7DE > > ---------------------------------------------------------------------- > > iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com > > Solutions for your high-tech problems. (406)-442-6648 > > ---------------------------------------------------------------------- > - Forrest W. Christian (forrestc@imach.com) AC7DE ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0101171755000.22366-100000>