Outage

**admin** · 18-07-13, 07:28 PM

All should be good now. It wasnt a problem with the server, just with an older VBulletin addon. Although we got rid of it long ago, it decided to haunt us.

It wrecked my site uptime, but not the server uptime as the server didnt go offline, though the server load did go through the roof.

Very happy again that we have a managed server, I couldnt access anything and they responded to my original support ticket in 2 minutes.

**NASA** · 18-07-13, 09:34 PM

Not sure what's happened but I can no longer access the site from my home connection. I only have access thru my iPhone now.

**Rick** · 18-07-13, 10:35 PM

Originally Posted by NASA

Not sure what's happened but I can no longer access the site from my home connection. I only have access thru my iPhone now.

clear your cache/cookies for Austech and try again

**admin** · 19-07-13, 09:54 AM

Originally Posted by Rick

clear your cache/cookies for Austech and try again

Yep, as Rick said it is probably your best first option. If you still have problems after doing that post back here or sent us a support ticket via the "contact us" link at the bottom of the page right hand side.

**NASA** · 27-07-13, 09:37 AM

Cleared all cache/cookies. Still no luck.

**mickstv** · 27-07-13, 04:21 PM

Originally Posted by NASA

Cleared all cache/cookies. Still no luck.

Clear Windows DNS Cache ....

Command to reset, flush or clear your DNS cache.

Vista, Windows 7, and WIndows 8

These same directions work in versions of Windows after XP; however, you’ll need to gain admin privileges first:
Vista, Windows 7, and Windows 8 directions for flushing the dns cache.
XP

XP remembers negative (DNS unable to resolve) entries for a few minutes. Often this can be a pain when moving and debugging sites. As long as that negative entry sits in your DNS cache, your box will continue to give you a cannot find server error. By cleaning out your DNS cache, you can fix this problem.

Rebooting will flush your cache… but there is an easier way.

Drop to a command box and type:

ipconfig /flushdns

If you wish to stop XP from placing negative entries into cache, you can make this change in your registry.

1. Goto HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\ Dnscache\Parameters
2. Build a new DWORD value called NegativeCacheTime and give it a value of 0

I believe the default time is 5 minutes. I always use zero for my default time, but I think the value above is in seconds. So if you only want to save them for 1 minute, then I am assuming you would change that value to 60.

The Restart

Taken from the link below

**admin** · 27-07-13, 05:07 PM

Originally Posted by NASA

Cleared all cache/cookies. Still no luck.

Yikes, you definately arent having any luck. Please try what Mick suggested, the problem is definately on your end.

This isnt going to help you, but can you access the site through our IP address ?

If so, Mick's suggestion should do the trick.

**Rick** · 27-07-13, 07:42 PM

also next option is to reboot your modem, what browser are you using?

**NASA** · 30-07-13, 05:43 PM

Tried all above suggestions ... still no luck on home network.

I can only access the site via tethering on iPhone.

Using Windows 7 with Explorer & Chrome.

**mickstv** · 30-07-13, 06:00 PM

open command prompt CMD, then type ping and post what happens.

EDIT What firewall are you using Windows internal firewall or some other internet security pack.

**NASA** · 30-07-13, 08:12 PM

First ping - tethered iPhone connection

Second ping - home wifi network connection

**mickstv** · 30-07-13, 08:26 PM

What firewall are you using Windows internal firewall or some other internet security pack

**NASA** · 30-07-13, 08:51 PM

Free AVG.

**ssrattus** · 31-07-13, 04:19 PM

g'day NASA
It almost appears that either your router or ISP has blocked austech, a trace route should show where the ping fails. Can you provide a trace route? Please be aware it will show details of your IP system and rough location, you may want to PM me the results.

Open command prompt CMD, then type tracert and post what happens.

**NASA** · 02-08-13, 01:17 AM

**ssrattus** · 02-08-13, 12:46 PM

Hmmm, now I didn't expect that. It appears that austech's host may blocking your IP, you could ask dodo what is going on, but I have heard that their customer support is bad. What you could try is to disconnect/connect your WAN side in your router and get a new IP, and see if it works. Problem is the whole subnet is probably blocked. But sometimes you will be issued a new IP in a different subnet.

Also Andrew be able to see if what I am saying is true.

Andrew, does austech's vbul have IP blocking? Maybe NASA's IP subnet was used by a spammer once and it was blocked?

**admin** · 02-08-13, 01:02 PM

I dont think we have any ip's blocked, I cant check at the moment but will post back in an our or 2 as I am on mobile atm

Sent from my GT-I9300 using Tapatalk 4 Beta

**Rick** · 02-08-13, 01:08 PM

try turning your modem off for a couple minutes then power back up

**NASA** · 02-08-13, 01:18 PM

Originally Posted by Rick

try turning your modem off for a couple minutes then power back up

Tried already. I even reset the modem to factory defaults & reinstalled. Still no luck.

I lost access to the site around the time of this outage as advised in this thread.

**admin** · 02-08-13, 03:01 PM

Originally Posted by ssrattus

Hmmm, now I didn't expect that. It appears that austech's host may blocking your IP, you could ask dodo what is going on, but I have heard that their customer support is bad. What you could try is to disconnect/connect your WAN side in your router and get a new IP, and see if it works. Problem is the whole subnet is probably blocked. But sometimes you will be issued a new IP in a different subnet.

Also Andrew be able to see if what I am saying is true.

Andrew, does austech's vbul have IP blocking? Maybe NASA's IP subnet was used by a spammer once and it was blocked?

We only had 2 banned IP addresses and neither related to this issue.

I will put in a support ticket with our host, they should be able to at least tell us what the issue is.