Jump to content
LegacyGT.com

Can't access lgt from home

ebpda9

By ebpda9
in Site Suggestions / Questions

Recommended Posts

ebpda9 Mentor

ebpda9

Posted
Posted
I cannot access this website from home. I get a page cannot be displayed error. I do not have any problems accessing any other sites, and if i want to browse lgt on my cellphone it works. DNS is resolving, but still cannot ping it. It works fine from work. Did someone get a domain/IP ban that had cox.com as their domain? Please fix. I feel homeless when i am at home :mad:
Link to comment
Share on other sites
GateTwelve Apprentice

GateTwelve

Posted
Posted
I'd like to second this. I cannot access from my home, but can access from my office. Right now, I'm using a proxy server at my home, and it's working fine. My home and office ISP's are the same. I have a local provider "SRT".
Link to comment
Share on other sites
GateTwelve Apprentice

GateTwelve

Posted
Posted
Using my local providers DNS servers, and Qwest's primary and secondary, my computer is giving 208.111.32.138 for the IP. All packets time out while performing a ping. An online ping tool came up with the same IP for legacygt.com, however, their packets were returned.
Link to comment
Share on other sites
GateTwelve Apprentice

GateTwelve

Posted
Posted

I only use Qwest DNS because my local ISPs DNS can be extremely slow with getting propagations. The trade-off is that Qwest DNS servers are incredibly slow at responding to requests.

 

Unfortunately, I still can't get to LGT without using a web based proxy at home. All my LGT pages now have a banner at the top asking me to hook up with 50+ year old cougars in my area :-(

Link to comment
Share on other sites
LuckyBob Mentor

LuckyBob

Posted
Posted
Using my local providers DNS servers, and Qwest's primary and secondary, my computer is giving 208.111.32.138 for the IP. All packets time out while performing a ping. An online ping tool came up with the same IP for legacygt.com, however, their packets were returned.

 

Run a traceroute on it and find out where the transmission error is.

 

 

 

Link to comment
Share on other sites
GateTwelve Apprentice

GateTwelve

Posted
Posted

Traceroute results:

 

1 <1 ms 1 ms 1 ms 10.0.0.2

2 7 ms * 7 ms 1.120.221.216.srtnet.com [216.221.120.1]

3 9 ms 6 ms 7 ms 27.97.221.216.srtnet.com [216.221.97.27]

4 8 ms 8 ms 8 ms 17.97.221.216.srtnet.com [216.221.97.17]

5 16 ms 15 ms 15 ms far-edge-01.inet.qwest.net [65.125.122.61]

6 48 ms 35 ms 36 ms far-core-01.inet.qwest.net [205.171.160.54]

7 22 ms 22 ms 22 ms min-core-01.inet.qwest.net [205.171.8.82]

8 37 ms 31 ms 33 ms cer-core-02.inet.qwest.net [67.14.8.14]

9 32 ms 32 ms 32 ms chp-brdr-01.inet.qwest.net [205.171.139.150]

10 40 ms 41 ms 40 ms 0.so-0-0-0.BR2.CHI13.ALTER.NET [204.255.168.17]

11 41 ms 56 ms 40 ms 0.so-6-1-0.XL4.CHI13.ALTER.NET [152.63.73.30]

12 69 ms 70 ms 69 ms 0.ge-3-0-0.XL4.SJC7.ALTER.NET [152.63.49.142]

13 70 ms 69 ms 69 ms POS5-0-0.GW4.SJC7.ALTER.NET [152.63.49.173]

14 74 ms 74 ms 74 ms internap-sjc-gw.customer.alter.net [157.130.195.90]

15 75 ms 76 ms 75 ms border4.pc1-bbnet1.sje.pnap.net [66.151.144.10]

16 74 ms 75 ms 76 ms giglinx-17.border4.sje.pnap.net [66.151.157.226]

17 75 ms 75 ms 74 ms 209.177.159.10

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

Link to comment
Share on other sites
Tide Grand Master

Tide

Posted
Posted
I've used fail2ban for several years on the site, and never had a complaint. That specifically is banning of IPs trying to hack the server via repeated logins over a short timeframe. The ban is temporary (i think an hour or two), so dictionary attacks or other DDoS attacks don't get anywhere for years. Though it's highly unlikely this is your specific issue.
Link to comment
Share on other sites
Tide Grand Master

Tide

Posted
Posted

traceroute to http://www.legacygt.com (208.111.32.138), 64 hops max, 40 byte packets

1 * * *

2 68.86.249.177 11.847 ms 9.042 ms 11.798 ms

3 68.87.192.18 10.186 ms 8.849 ms 11.703 ms

4 68.87.192.34 12.406 ms 14.139 ms 13.486 ms

5 68.86.91.225 31.946 ms 18.509 ms 13.407 ms

6 68.86.85.78 21.682 ms 16.372 ms 17.581 ms

7 154.54.11.105 16.948 ms 16.765 ms 18.756 ms

8 154.54.7.173 17.080 ms 154.54.2.165 18.804 ms 154.54.0.177 17.005 ms

9 154.54.1.26 19.724 ms 18.810 ms 154.54.2.126 19.485 ms

10 154.54.6.74 19.468 ms 154.54.6.70 26.048 ms 154.54.6.74 19.324 ms

11 38.99.214.170 203.889 ms 206.333 ms 120.371 ms

12 66.231.186.6 92.704 ms 234.192 ms 243.810 ms

13 208.111.37.54 17.536 ms 20.935 ms 23.366 ms

14 208.111.32.138 18.088 ms 19.183 ms 18.893 ms

Link to comment
Share on other sites
LuckyBob Mentor

LuckyBob

Posted
Posted
I've used fail2ban for several years on the site, and never had a complaint. That specifically is banning of IPs trying to hack the server via repeated logins over a short timeframe. The ban is temporary (i think an hour or two), so dictionary attacks or other DDoS attacks don't get anywhere for years. Though it's highly unlikely this is your specific issue.

 

So the last IP that GateTwelve is getting a response from is owned by VR Hosted, which also owns the IP block that LegacyGT is hosted on. Tide, give your upstream provider a call and see if they're having any routing or packetloss issues. BTW - I like the name of the LLC you've got going ;).

Link to comment
Share on other sites
GateTwelve Apprentice

GateTwelve

Posted
Posted

Not to mention fail2ban wouldn't catch my elite script kiddie grepping abilitiez! </sarcasm>

 

But yeah...this issue seems to be beyond my control...so I'll play the waiting game unless you'd like me to provide any additional information.

Link to comment
Share on other sites
LuckyBob Mentor

LuckyBob

Posted
Posted
traceroute to http://www.legacygt.com (208.111.32.138), 64 hops max, 40 byte packets

1 * * *

2 68.86.249.177 11.847 ms 9.042 ms 11.798 ms

3 68.87.192.18 10.186 ms 8.849 ms 11.703 ms

4 68.87.192.34 12.406 ms 14.139 ms 13.486 ms

5 68.86.91.225 31.946 ms 18.509 ms 13.407 ms

6 68.86.85.78 21.682 ms 16.372 ms 17.581 ms

7 154.54.11.105 16.948 ms 16.765 ms 18.756 ms

8 154.54.7.173 17.080 ms 154.54.2.165 18.804 ms 154.54.0.177 17.005 ms

9 154.54.1.26 19.724 ms 18.810 ms 154.54.2.126 19.485 ms

10 154.54.6.74 19.468 ms 154.54.6.70 26.048 ms 154.54.6.74 19.324 ms

11 38.99.214.170 203.889 ms 206.333 ms 120.371 ms

12 66.231.186.6 92.704 ms 234.192 ms 243.810 ms

13 208.111.37.54 17.536 ms 20.935 ms 23.366 ms

14 208.111.32.138 18.088 ms 19.183 ms 18.893 ms

 

So every system I've tried it from has avoided the 209.X.X.X subnet. Betcha it's an upstream routing issue.

 

root@backuppc:~/net-snmp-5.4.2.1# tracepath -n legacygt.com

1: 72.51.0.212 0.289ms pmtu 1500

1: 216.187.64.193 0.914ms

1: 216.187.64.193 0.879ms

2: 216.187.64.94 2.180ms

3: 216.187.64.93 0.960ms asymm 4

4: 216.187.89.190 1.070ms asymm 3

5: 216.187.88.202 19.446ms asymm 3

6: 69.90.215.210 20.107ms asymm 8

7: 66.231.186.6 30.668ms

8: 208.111.37.54 31.957ms

9: 208.111.32.138 32.112ms reached

Resume: pmtu 1500 hops 9 back 56

 

 

Tracing route to legacygt.com [208.111.32.138]

over a maximum of 30 hops:

 

1 1 ms 1 ms 1 ms 192.168.1.1

2 8 ms 7 ms 7 ms 73.98.14.1

3 20 ms 25 ms 17 ms 68.87.206.181

4 12 ms 19 ms 12 ms 68.86.96.173

5 16 ms 14 ms 15 ms 68.86.90.221

6 36 ms 31 ms 33 ms 68.86.85.162

7 30 ms 31 ms 30 ms 68.86.85.181

8 32 ms 31 ms 31 ms 154.54.11.105

9 31 ms 31 ms 32 ms 154.54.7.173

10 128 ms 202 ms 49 ms 154.54.2.138

11 51 ms 33 ms 45 ms 154.54.6.70

12 32 ms 31 ms 31 ms 38.99.214.170

13 35 ms 32 ms 32 ms 66.231.186.6

14 31 ms 33 ms 31 ms 208.111.37.54

15 33 ms 32 ms 33 ms 208.111.32.138

 

Trace complete.

 

Tracing route to legacygt.com [208.111.32.138]

over a maximum of 30 hops:

 

1 1 ms <1 ms <1 ms 64.81.10.33

2 11 ms 15 ms 15 ms 64.81.9.65

3 13 ms 9 ms 9 ms 69.17.83.233

4 12 ms 10 ms 10 ms 198.32.180.40

5 27 ms 30 ms 29 ms 72.52.92.49

6 52 ms 39 ms 29 ms 72.52.92.117

7 29 ms 30 ms 30 ms 66.160.146.134

8 29 ms 29 ms 30 ms 66.231.186.6

9 32 ms 29 ms 30 ms 208.111.37.54

10 26 ms 30 ms 30 ms 208.111.32.138

 

Trace complete.

Link to comment
Share on other sites
LuckyBob Mentor

LuckyBob

Posted
Posted

In case you don't have it. The contact info is the same for the last successful hop that GateTwelve reached.

 

OrgName: VR HOSTED

OrgID: VRHOS

Address: 28 N 1st St

Address: Suite #810

City: San Jose

StateProv: CA

PostalCode: 95113

Country: US

 

NetRange: 208.111.32.0 - 208.111.47.255

CIDR: 208.111.32.0/20

NetName: VRHOS-ARIN-19-0002

NetHandle: NET-208-111-32-0-1

Parent: NET-208-0-0-0-0

NetType: Direct Allocation

NameServer: NS1.VRDNS.COM

NameServer: NS2.VRDNS.NET

NameServer: NS3.VRDNS.INFO

Comment:

RegDate: 2007-04-09

Updated: 2008-09-12

 

OrgAbuseHandle: ABUSE1018-ARIN

OrgAbuseName: Abuse Department

OrgAbusePhone: +1-408-833-7040

OrgAbuseEmail: abuse@vr.org

 

OrgNOCHandle: NOC1935-ARIN

OrgNOCName: Network Operations Center

OrgNOCPhone: +1-800-274-7019

OrgNOCEmail: noc@vr.org

 

OrgTechHandle: IPADM257-ARIN

OrgTechName: IP Admin

OrgTechPhone: +1-800-274-7019

OrgTechEmail: staff@vr.org

 

# ARIN WHOIS database, last updated 2009-03-23 19:10

Link to comment
Share on other sites
enthusiast Mentor

enthusiast

Posted
Posted
Traceroute results:

 

1 <1 ms 1 ms 1 ms 10.0.0.2

2 7 ms * 7 ms 1.120.221.216.srtnet.com [216.221.120.1]

3 9 ms 6 ms 7 ms 27.97.221.216.srtnet.com [216.221.97.27]

4 8 ms 8 ms 8 ms 17.97.221.216.srtnet.com [216.221.97.17]

5 16 ms 15 ms 15 ms far-edge-01.inet.qwest.net [65.125.122.61]

6 48 ms 35 ms 36 ms far-core-01.inet.qwest.net [205.171.160.54]

7 22 ms 22 ms 22 ms min-core-01.inet.qwest.net [205.171.8.82]

8 37 ms 31 ms 33 ms cer-core-02.inet.qwest.net [67.14.8.14]

9 32 ms 32 ms 32 ms chp-brdr-01.inet.qwest.net [205.171.139.150]

10 40 ms 41 ms 40 ms 0.so-0-0-0.BR2.CHI13.ALTER.NET [204.255.168.17]

11 41 ms 56 ms 40 ms 0.so-6-1-0.XL4.CHI13.ALTER.NET [152.63.73.30]

12 69 ms 70 ms 69 ms 0.ge-3-0-0.XL4.SJC7.ALTER.NET [152.63.49.142]

13 70 ms 69 ms 69 ms POS5-0-0.GW4.SJC7.ALTER.NET [152.63.49.173]

14 74 ms 74 ms 74 ms internap-sjc-gw.customer.alter.net [157.130.195.90]

15 75 ms 76 ms 75 ms border4.pc1-bbnet1.sje.pnap.net [66.151.144.10]

16 74 ms 75 ms 76 ms giglinx-17.border4.sje.pnap.net [66.151.157.226]

17 75 ms 75 ms 74 ms 209.177.159.10

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

 

 

The highlighted address is the same place mine stops resolving.

My mod list
Link to comment
Share on other sites
GateTwelve Apprentice

GateTwelve

Posted
Posted

Well, either Tide is super quick at fixing things, or I had much adu about nothing... after three days, I can now get to the site without a proxy.

 

1 1 ms 1 ms <1 ms 10.0.0.2

2 7 ms * 7 ms 216.221.120.1

3 9 ms 7 ms 8 ms 216.221.97.27

4 16 ms 8 ms 10 ms 216.221.97.17

5 41 ms 35 ms 36 ms 65.125.122.61

6 17 ms 15 ms 16 ms 205.171.160.54

7 23 ms 22 ms 22 ms 205.171.8.82

8 33 ms 32 ms 32 ms 67.14.8.14

9 33 ms 33 ms 32 ms 205.171.139.150

10 39 ms 38 ms 38 ms 204.255.168.17

11 39 ms 40 ms 45 ms 152.63.73.30

12 76 ms 69 ms 72 ms 152.63.49.142

13 70 ms 70 ms 68 ms 152.63.49.173

14 112 ms 219 ms 160 ms 157.130.195.90

15 74 ms 74 ms 74 ms 66.151.144.10

16 76 ms 75 ms 75 ms 66.151.157.226

17 75 ms 74 ms 75 ms 208.111.37.50

18 74 ms 75 ms 76 ms 208.111.32.138

Link to comment
Share on other sites
LuckyBob Mentor

LuckyBob

Posted
Posted
Well, either Tide is super quick at fixing things, or I had much adu about nothing... after three days, I can now get to the site without a proxy.

 

1 1 ms 1 ms <1 ms 10.0.0.2

2 7 ms * 7 ms 216.221.120.1

3 9 ms 7 ms 8 ms 216.221.97.27

4 16 ms 8 ms 10 ms 216.221.97.17

5 41 ms 35 ms 36 ms 65.125.122.61

6 17 ms 15 ms 16 ms 205.171.160.54

7 23 ms 22 ms 22 ms 205.171.8.82

8 33 ms 32 ms 32 ms 67.14.8.14

9 33 ms 33 ms 32 ms 205.171.139.150

10 39 ms 38 ms 38 ms 204.255.168.17

11 39 ms 40 ms 45 ms 152.63.73.30

12 76 ms 69 ms 72 ms 152.63.49.142

13 70 ms 70 ms 68 ms 152.63.49.173

14 112 ms 219 ms 160 ms 157.130.195.90

15 74 ms 74 ms 74 ms 66.151.144.10

16 76 ms 75 ms 75 ms 66.151.157.226

17 75 ms 74 ms 75 ms 208.111.37.50

18 74 ms 75 ms 76 ms 208.111.32.138

 

Yeah, but notice that you're avoiding the 209.177.159.10 device this time. Sounds like somebody changed their routes to get around either that or the next device.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Go to topic listing


×
×
  • Create New...

Important Information

Terms of Use

  I accept