Wrestling Forum banner

JEWS DID THIS

2K views 21 replies 12 participants last post by  JM 
#1 ·
Hey,

Haven't been able to access the forum at all, all day. I'm getting...

""The connection has timed out

The server at www.wrestlingforum.com is taking too long to respond."

...(and the equivalent) on both Chrome and Firefox.

Once I realised the site wasn't down for everyone, I managed access a very broken (maybe cached?) version of WF via Ninja Proxy. This version has a lot of dead links, a blank chatbox etc., but somehow I can post VMs and, presumably, in threads. It's just very difficult to find a route via live links to these parts of the board.

After speaking to LC about it (see her VMs), I've noticed that I can access (what seems to be) a full working version of the site via Cloud internet on my phone.

Perhaps a problem relating to my ISP/DNS???

I have no issues with any other websites!

Any suggestions and/or help?

:CENA
 
See less See more
#12 ·
Try checking you're trying to go to correct ip address. You can also try pinging the ip. also see end of post if you want to try alternate free DNS servers such as Google Public DNS and OpenDNS just in case your isp dns is flaky or something.


The IP of the box this forum is hosted on:
Name: www.wrestlingforum.com
Address: 50.97.177.66


Wrestlingforum's old IP address is: 174.36.87.134, so if you see that, your dns server somehow got way outdated info. Since softlayer host moved things around, and consolidated into 1 server, making it easy for Verticalscope to move purchased forums to same box for easier control.


On windows, Start, then in search type cmd, you'll see command line, run it and at prompt type: nslookup www.wrestlingforum.com
See if it shows same IP as above.

With Command line open type: ping 50.97.177.66
see if you get replies. Replies should look similar to:
Pinging 50.97.177.66 with 32 bytes of data:

Reply from 50.97.177.66: bytes=32 time=35ms TTL=55
Reply from 50.97.177.66: bytes=32 time=35ms TTL=55
Reply from 50.97.177.66: bytes=32 time=35ms TTL=55
Reply from 50.97.177.66: bytes=32 time=34ms TTL=55

Ping statistics for 50.97.177.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 35ms, Average = 34ms

Just going to that IP in web browser won't get you to this forum since that 1 box uses multiple "Virtual Hosts".
The real hostname of their ip address uses is: 42.b1.6132.ip4.static.sl-reverse.com

The Autonomous System (AS) number 36351 is assigned to SoftLayer Technologies Inc.. AS36351 is assigned on 2005-12-12 by the Regional Internet Registry arin.

Servers hosted by: http://www.softlayer.com/
But All the forums purchased and owned by: http://www.verticalscope.com/index.html


Few Virtual Hosts all sharing this same server, so you need to make sure to check when you do a "nslookup" on the server domain it's going to right ip, but you can't use the ip itself to get to vhost without using a plugin to modify your 'get' request, so it requests the correct host without requiring the domain.
Code:
ftp.prcforum.com	
www.tennisforum.com	
42.b1.6132.ip4.static.sl-reverse.com	
www.prcforum.com	
m.wildcatforums.net	
dev.basketballforum.com	
img.basketballforum.com	
www.wrestlingforum.com	
www.xtratime.org	
img.xtratime.org	
img.wrestlingforum.com	
mobile.wildcatforums.net	
www.wildcatforums.net	
www.menstennisforums.com	
host.prcforum.com	
ftp.wildcatforums.net	
www.basketballforum.com	
webmail.prcforum.com	
webmail.wildcatforums.net
Of course Softlayer has several ip's or boxes with hosted sites owned by vertical scope of course. But the .66 ip is where this site sits, for now.
And the admin hasn't configured their default webserver to redirect to the hosting server's, or the primary company, or a list of hosted sites yet.
http://50.97.177.66/


Some isp's may get trouble with their DNS servers.
sometimes they don't recache correctly or domain names not propagate out correctly or whatnot if that's the case once the TTL on wrestlingforum.com domain expires then to the dns server that has a problem the name disappears after the ttl expires. Normally stuff just get's recached from a top level dns and propagates outward to the millions of isp and home user dns servers.

If you'd like to see if maybe it's a dns issue.

Google does offer free "GoogleDNS" you can swap in and use, instead of your isp dns servers, or you can use OpenDNS's dns servers also.

Many dumb isp's overseas block websites just using their dns servers which many folks realized how silly it was since anyone can manually change the dns server they use online and swapping to a US or whatnot dns server they bypassed their isp blocks :p until they actually began firewalling or redirecting traffic.

But here ya go with some instructions if you'd like to test if changing dns will fix problem, if it does, just fire off email or call ISP and tell them their dns server is b0rked.


Google DNS:
https://developers.google.com/speed/public-dns/?hl=en

Try it out

Configure your network settings to use the IP addresses 8.8.8.8 and 8.8.4.4 as your DNS servers.
Or, read our configuration instructions (IPv6 addresses supported too).

If you decide to try Google Public DNS, your client programs will perform all DNS lookups using Google Public DNS.

Or


OpenDNS (Main Site): https://www.opendns.com/

Info you need for using their public dns: https://use.opendns.com/

Put in the OpenDNS server addresses, 208.67.222.222 and 208.67.220.220, as your DNS server settings and save/apply.

If your ISP is having issues with its DNS service, switching to OpenDNS' DNS will get you back online in just a few quick steps. Follow the instructions for your operating system or router below.

If you have friends, family, or colleagues who have the same ISP as you, send them this info to help them get back online. Text them or call them with the IP address http://67.215.71.202.

Maybe trying alternate dns settings could help, but if you can ping the IP from command line then your computer can definitely see it. So I'd look more at your browser or if you run dd-wrt on your router and depending on what security plugins/watchdogs you got running check it if it firewalled the site.


Anyhow just some ideas without going into detail, like resetting your browser, or opening browser in safemode or try turning off plugins and trying just to rule shit out.
 
#13 ·
Thanks for the excellent post, @prodnoss. Here's what I've got so far...

- I'm going to the correct IP for WF
- When I ping WF I just get "Request timed out" over and over. 100% loss.
- If I go to 42.b1.6132.ip4.static.sl-reverse.com, in a browser, I get the same time out error I'd get if I typed "wrestlingforum.com" into the address bar.
- For the record, I've now noticed I'm also unable to access basketballforum.com, menstennisforums.com etc. etc. by typing their URLs into the address bar.
- Trying alternate DNS settings doesn't work
- Safe mode doesn't help
- I haven't tried running dd-wrt on my router yet
- @JM My IP, according to cmd.exe, is different to the one I sent you. I'll PM you again.
- @Headliner thanks for drawing my attention to Prodnoss's post
- @AryaDark :cry
 
#14 ·
Yea, if you go to this server's ip address, http://50.97.177.66 or it's actual hostname, http://42.b1.6132.ip4.static.sl-reverse.com

you'd see this unconfigured webspace:



Just out of curiosity...

go here: https://zend2.com/
in that webpage type or copy/paste http://www.wrestlingforum.com

click surf, see if the forum loads.

Note: Do not log in from there! only see if it loads the forum

that's bouncing you off a proxy, from another ip then back to the forum. I'm curious if it loads.

By the way, are you in US? or what country? and if so what provider? Of course you don't have to answer. I'm just curious.


if none of this server's Virtual Hosts websites load then it's not just this website it's entire box, you can't reach.

if the server admin can traceroute your ip address from the command prompt on this server or and then see if he can ping your current ip address of course some home routers have icmp echo disabled, but you should be "traceroutable". :p


If the admin can't ping your ip from this server's console, then the admin does a traceroute to your ip from this server's console, and then you do a traceroute from your computer to this site.

then compare the 2 traces and see where it's stopping. If you notice you both stop getting replies from the same router, then something is wrong on that router, and contact it's owner, if admin can traceroute all the way to you, but you can't back, where does it stop? as that means this server sees you, you cant see it, etc. It helps paint a better picture when you trace from 2 directions toward each other and see where ya meet in middle if something drops out, helps troubleshoot.

or I know this forum does block some anonymous proxies like hideme and such, it's possible there is a firewall of a entire netblock that your provider is getting caught in.


if you would like to traceroute and see where it stops if you are in Windows.
open command prompt just as if you were pinging

and do this but give it to the admin or mod helping you, as the first few hops will identify your provider if you don't want it known.

tracert -d 50.97.177.66

Tracing route to 50.97.177.66 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms ......
2 3 ms 3 ms 4 ms ......
3 7 ms 7 ms 6 ms ......
4 13 ms 14 ms 13 ms .....
5 13 ms 13 ms 13 ms ......
6 13 ms 13 ms 12 ms 198.32.132.90
7 35 ms 35 ms 35 ms 173.192.18.134
8 35 ms 35 ms 35 ms 173.192.18.217
9 37 ms 36 ms 37 ms 173.192.118.141
10 35 ms 35 ms 34 ms 50.97.177.66

Trace complete.
I'm kinda surprised I'm only technically 6 hops after i leave my isp to this server, of course looks like the server is in Dallas, Texas, based on the router in front of it.


by the way notice the IP address right before you hit this server in my traceroute. That's the router sitting in front of this server, you won't be able to ping it as it has icmp echo requests turned off apparently. And i don't want to go through teaching you how to udp/syn ping unless you know how. But if you traceroute and you do see that IP listed below or in my #9 spot. Then that tells me you can at least reach the router directly in front of the server.


Name: po2.fcr02.sr02.dal05.networklayer.com
Address: 173.192.118.141






Also for "shits and giggles" let's try some other website this company owns that are on other IP's.


Go here: http://www.verticalscope.com/

at top of page see link that says "Our Verticals"
all the sports forums are on this same box as wrestlingforum.com

but it looks like each "Genre" is all hosted on 1 box.

Try Automotive forums, so Verticalscope then "Our Verticals" then "automotive" then pick one. For example I just tried:
http://www.cadillacforums.com/

it's on IP address: 108.168.211.86

The good thing is it's hosted by the same company "Softlayer". So see if you can hit any of those forums on Vertical Scope's list.

Each genre's tons of forums are on it's own shared IP.
 
#11 ·
I do not mind the title so much as this is a rerun. There was another thread with same title and same subject a couple days ago. What is this, Hollywood.
 
#20 ·
Well if the BT folks had issue last week required resetting router then I'd suggest doing a reset not just reboot and should clear up.

If they had to reset routers only thing that pops in my head is your ARP cache is fubar. Normally high end routers or if you run dd-wrt and have access to command line you can clear the ARP cache manually but a reset is simple also.


What is ARP cache for?
http://www.tcpipguide.com/free/t_ARPCaching.htm

There are "ARP poisoning" attacks:
http://security.stackexchange.com/questions/19638/why-is-arp-poisoning-killing-all-network-activity


And just for general info, Cisco guys , where ccna and ISP employees hang out when they need a bit of help. Discussing difference between clearing ARP cache and clearing the IP ARP in Cisco ios
https://supportforums.cisco.com/dis...ence-between-clear-arp-cache-and-clear-ip-arp
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top