Thread: Misplaced of access to a particular site

I owe 4 computers on a local network, where 3 out of the 4 are wireless and only 1 is a wired. For the last 2 weeks, I’m not able to access to one site from the 3 of them. I have also made an attempt to ping and trace the route without any success. I have also reset my router, tried to open both the DNS as well as my ISP DNS. A friend of mine who is using the similar ISP is not encountering with the issue that I’m suffering from. The problem appears to be with the start when the site which was attacked and its host took it down for certain hours. This has affected the Firefox 3, Thunderbird 2, IE 7 in my computer. The machines are all running XP there is a cable modem & digital phone interface for the connection.

From one of the working computers, and one of the non-working ones, please do the following.

Hold the Windows key and press the R key, then type CMD for opening of a command prompt:

In the command prompt window which opens, type the following command:

TRACERT wnycomsoc.org

Right click in the command window and choose Select All, then hit the Enter key to copy the stuff to the clipboard. Paste the results in a message here.

If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.

I would also had made the same mistake as the above user did--not realize that 3 meant that all 4.

Well, there is a big difference between 3 and 4. Try contacting it with a proxy site and see to it that there might be a routing problem with your ISP, which is what seems to look like from here. Since you have cut off the IP address in the header of the TRACERT, what is the IP that the URL has solved while you trace it? I’m getting 72.51.43.110, inquisitive if you get the same address.

Contacting all the way through a proxy works, but I’m finding it difficult to access the cookies. How do I FIX this problem as it is conflicting while working around

You can get in touch with the ISP as well as hammer them. Since the proxy who works, I suppose that this is an ISP internal network routing problem, not your issue.I've also seen that this generally arise when I had a Comcast. It took me three weeks and a dozen of calls to fix it; they also kept me testing from a remote location and maintain it all worked. I had to get pretty rude to get them to really test nearby and detach the issue.