Google 'not working'

[ekkas2]

Strange problem...

Suddenly the past few days, when opening Google.com (which automatically redirects to google.co.za here is South Africa), I get a 'test page for Apache installation' & google doesn't show. When I do [Ctrl+F5], Google.co.za comes up, but on next open, it shows the test page again.

On the WG server it always works correctly, but on all clients, I get Apache test page. If I use google.co.uk or some other sites, it all is fine, just google.com (which changes itself to google.co.za) or google.co.za.

It's been like this for a few days & using other people's connections it all works fine, just our WG clients show this strange behaviour. I have a linux email server with Apache installed, but WG 'doesn't know about it' in any configs...


nslookup www.google.co.za
*** Can't find server name for address 10.1.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 10.1.1.1

Non-authoritative answer:
Name: www.l.google.com
Addresses: 66.102.7.147, 66.102.7.104, 66.102.7.99, 66.102.7.147
66.102.7.104, 66.102.7.99
Aliases: www.google.co.za, www.google.com, www.google.com





tracert www.google.co.za

Tracing route to www.l.google.com [66.102.7.147]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 10.1.2.254
3 3 ms 2 ms 2 ms 10.254.254.37
4 4 ms 3 ms 3 ms 10.254.254.26
5 4 ms 4 ms 5 ms 10.254.254.30
6 5 ms 4 ms 4 ms 10.1.1.1
7 5 ms 4 ms 4 ms 192.68.254.254
8 14 ms 10 ms 6 ms 196.36.9.145
9 72 ms 69 ms 67 ms 196.37.241.29
10 132 ms 93 ms 74 ms 196.36.80.209
11 69 ms 68 ms 66 ms cdsl2-rba.isdsl.net [196.36.80.162]
12 83 ms 205 ms 65 ms 196.36.80.165
13 632 ms 628 ms 644 ms 168.209.0.242
14 723 ms 723 ms 728 ms 168.209.100.17
15 912 ms 773 ms 798 ms 168.209.246.8
16 810 ms 774 ms 791 ms 195.66.226.125
17 788 ms 721 ms 723 ms 66.249.95.130
18 745 ms 735 ms 756 ms 66.249.95.146
19 824 ms 923 ms 870 ms 216.239.46.48
20 962 ms 927 ms 860 ms 66.249.95.215
21 867 ms 795 ms 877 ms 72.14.236.11
22 890 ms 783 ms 805 ms 72.14.233.131
23 874 ms 867 ms 792 ms 216.239.49.66
24 813 ms 894 ms 839 ms mc-in-f147.google.com [66.102.7.147]

Trace complete.

[logan]

Hi,

From the traceroute, you can be certain that the server exists and requests should be getting there. Because of this, my first instinct is that the apache test page may be coming from WinGate's cache.

Try deleting or disabling the cache in WinGate and see if that helps your problem.

C:\Program Files\WinGate\cache

Logan