I went to Miataturbo.net today and found that it wouldn't resolve. Pings didn't work, etc. Ok, so maybe dns problem or site is down. Check on my phone using 3g and it works.

Ok, so lets check dns... I get 174.120.46.56 on a ping with my phone and try that on computer. Request timed out. Ok, so maybe this workstation sucks. I move on to another one and check. Same issue. Ok, secondary and tertiary browser check. Same issue.

Is MT blocking certain ip ranges now or is there a network problem affecting some geographic regions/systems? I guess it will probably just be an intermittent issue and work fine tomorrow but the secondary network check made it seem odd.

 

Is this still an issue?

 

same problem as of 3/4/12. Responding to this on my phone. MT resolves to 174.120.46.56 on phone network and verizon fios network. No dropped packes on phone while all local stations report request timeout.

 

Sounds like your workstation is the issue. Do they block certain websites? Is your traffic routed weird?

 

My first post describes a specific check for the single workstation / browser issue. Dns resolves properly directly on router. Direct ping fail from router to MT. Same behavior as workstations. I control network traffic, no odd routing. Tracert shows death after 13 external hops, so it isn't local.

 

Maybe it's SOPA.

 

Still down. Still works via phone which has an alternate connection. Posting right now with a proxy browsing session so we know it isn't the fios network itself.

 

Still an issue. Can come in using same connection & computers using proxy or pass-through systems. Pings don't return, traceroute dies on mt side when coming directly from my ip. Can get to mt from all other sources I have tested. I believe this to be a simple ip block at this point. Annoying.

 

Fire over the Ip you are failing with and I will take a look again.

 

This problem just hit me hard.

Company link: Connects to MT.net fine
Both VPN'd and local PCs to my home network: Cannot connect to MT.net over multiple PCs in numerous configurations
Lame proxy service (Hidemyass.com): Connects just fine from the same PCs that cannot connect above.

The server is rejecting my connections to mt.net when using the IP to connect, although I can send TCP/IP data to the server that way.

I can connect fine via numerous VPNs I have AROUND ZE WOOORLLLDddddd...

 

http://i39.tinypic.com/5we0yc.png

Copy of the tracert's associated with this. The MT.net server or a connection before it is actively dropping TCP/IP data I send.

 

Set up an alternative way to access the site, on fine now, but I would imagine if this hit someone else, they'd have a few difficulties.

 

Yeah I'm having the same issue.

 

same here

 

Also, what the hell is up with this?

I get this in Chrome, Firefox, & IE on 3 seperate machines on 2 different ISPs.

Sad panda :(

 

@aaronc7
he noticed some weird ---- today too

 

Maybe IB is switching to new servers? Graphics missing for some users and not for others may be the new DNS propagating slowly?

 

I don't think so, Reverant.

If that is the case, the new servers are refusing TCP/IP connections from certain places, and not others. That doesn't make a lot of sense.

 

I was also unable to get to the forum a few hours back as well.

Still seeing random red x's though.

 

Refusing certain connections, as in you typed the IP address of the servers and got a connection refused? Connection timed out? No route to host? What?