On Tue, 20 Aug 1996, Kim Hubbard wrote:
For the record, I did not refuse to acknowledge your problem. I refused to acknowledge your wild accusations that Network Solutions was purposely singling out your network number for filtering. You refused to acknowledge that there could be any other possible reason for your problem.
You forgot to point out that his evidence below indicates that this is an MCI problem in Washington. Besides the fact that Network Solutions isn't anyone's provider...
According to my traceroute, I see that they get filtered out at network-solutions which is your provider. Will you be able to assist? Thanks...
traceroute to rs.internic.net (198.41.0.6), 30 hops max, 40 byte packets 1 eth-3.gw-4.hck.idt.net (169.132.32.254) 2.907 ms 2.026 ms 3.068 ms 2 eth-0.gw-1.hck.idt.net (169.132.34.250) 107.054 ms 121.335 ms 77.012 ms 3 10.255.255.1 (10.255.255.1) 82.342 ms 70.764 ms * 4 192.41.177.181 (192.41.177.181) 55.270 ms 48.858 ms 42.972 ms 5 core2-hssi2-0.Washington.mci.net (204.70.1.213) 40.422 ms 40.915 ms 43.822 ms 6 border7-fddi-0.Washington.mci.net (204.70.74.51) 33.906 ms 78.689 ms 75.278 ms 7 * * *
Michael Dillon - ISP & Internet Consulting Memra Software Inc. - Fax: +1-604-546-3049 http://www.memra.com - E-mail: michael@memra.com