For those of you, finding yourself on this page:
Situation
Note first up, this is NOT a ForumUp site page. Nor is it related to ForumUp in any manner.
There is
not a problem at ForumUp, neither on your Forum, or on our Servers. We know this, because your Forum can
still be seen, and accessed, normally from other locations around the globe.
It is
not the result of anything that may be on your computer.
Background
It is a DNS problem somewhere in the UK region, between you, and our Server. The DNS, are 'nodes' that direct your data around the globe, to and from yourself, and our server.
The DNS are little databases containing 'directories', or 'road-maps' of the Internet. One of these has been compromised, and is re-routing you to an alternate location, and server.
Solution
One of our generous Users has provided these instructions to get you around this problem:
| Slaney wrote: |
Go to this folder: C:\WINDOWS\system32\drivers\etc
Open the HOSTS file using Notepad,
Add the IP address 67.15.127.26 directly under "127.0.0.1"
Then tab across under "localhost" and put in your_forum_name.forumup.co.uk
Close out of Notepad, and when asked if you want to save changes click on Yes.
It should look like this when done,
| Code: | # Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
67.15.127.26 your_forum_name.forumup.co.uk
|
Remember to replace your_forum_name.forumup.co.uk with the URL of your Forum. |
My thanks to Dodge1982, and Slaney, for their valuable contributions toward rectifying this problem - Kana3.