Port 80 redirect

[breese]

I am using version 6.6.4 1338 on a Windows 2003 server.
My port 80 is being redirected back onto its self...
when anyone tried to make a connection to my webserver behind gatekeeper, I see the guest connection and then a new connection at Proxy (the name of the gatekeeper system).
Hundreds of connections are made to the point the system is almost dead.
If I stop the www Port 80 service, all other services work.

I have run, Synantec Anti-virus, Super Antivirus Pro, Trojan Hunter and Exterminate It!, all I own and nothing has been found.

I checked the system host file and there no redirect.
The system has 2 nic's, 1 external (DSL) and 1 internal. The IP address's gatways and DNS have not been changed and everything works except incomming Port 80.

Also, I have powered down my web server (the only other machine on the internal network) and retested wingate.... It still turns onto its self... instead of giving me a port error.

I do not know where to turn so I am asking for your help.
if you need or want access, tell me how and I will do it.
thanks for the time.....

[adrien]

so you're doing a reverse proxy?

Sounds like the settings got changed to get WinGate to connect to itself

That's why the connections show as coming from Proxy.

Can you please check the reverse proxy settings in the WWW proxy?

Adrien

[breese]

Action Reverse Proxy reques
Server: 10.0.0.240
Port 80
not checked.... Cache requests, Prepend resource with, Change Host tag to

[adrien]

OK, what does the connection show up as?

as a web request, or general mapping?

Did some other proxy get created looping back to itself (e.g. TCP mapping proxy).

It didn't change IP and get that 10.0.0.240 assigned to itself?

Adrien

[breese]

Address table and routing table.
The server is at 10.0.0.240




Windows IP Configuration



Host Name . . . . . . . . . . . . : proxy

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Server Adapter

Physical Address. . . . . . . . . : 00-0E-0C-72-1A-AA

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.0.0.9

Subnet Mask . . . . . . . . . . . : 255.0.0.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 68.94.156.1

151.164.8.201



PPP adapter Ameritech:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 99.142.10.220

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 99.142.10.220

DNS Servers . . . . . . . . . . . : 68.94.156.1

151.164.8.201

NetBIOS over Tcpip. . . . . . . . : Disabled



7.02 System Route Table

7.03 ---------------------------------------------

7.04 Current Route Table:

7.05 ---------------------------------------------

7.06 Network Mask Gateway Interface Metric

7.07 0.0.0.0 0.0.0.0 99.142.10.220 99.142.10.220 1

7.08 10.0.0.0 255.0.0.0 10.0.0.9 10.0.0.9 10

7.09 10.0.0.9 255.255.255.255 127.0.0.1 127.0.0.1 10

7.10 10.255.255.255 255.255.255.255 10.0.0.9 10.0.0.9 10

7.11 99.142.10.220 255.255.255.255 127.0.0.1 127.0.0.1 50

7.12 99.142.15.254 255.255.255.255 99.142.10.220 99.142.10.220 1

7.13 99.255.255.255 255.255.255.255 99.142.10.220 99.142.10.220 50

7.14 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

7.15 224.0.0.0 240.0.0.0 10.0.0.9 10.0.0.9 10

7.16 224.0.0.0 240.0.0.0 99.142.10.220 99.142.10.220 1

7.17 255.255.255.255 255.255.255.255 10.0.0.9 10.0.0.9 1

7.18 255.255.255.255 255.255.255.255 99.142.10.220 99.142.10.220 1

7.19

8.01 ---------------------------------------------

[adrien]

Hi

I don't think it will be a routing issue. Have you checked all the proxies? Routing I don't think can cause WinGate to connect to itself.

Regards

Adrien

[breese]

How do I transfer the license to another machine?
I will rebuild the proxy's

[adrien]

HI

I can probably find the problem quickly if you have some sort of remote access possible - e.g. teamviewer or remote desktop

If you want, send access details to support@wingate.com

Shouldn't need to rebuild the proxy.

Regards

Adrien

[breese]

I will send email later with access
Do you have / use MS terminal access?

[adrien]

sure - you mean windows remote desktop / terminal services client?

[mlderr]

I am not sure where this issue/post actually begins/ends. I am now in the same boat. I have been running a small Bank (70 computers) off of Wingate 6.2.2 (25 user on Win2000) for a while (years). I have the Kaspersky and Puresight plugins running with it. This past Wednesday we added a backup VPN router for the bank to it's data processor and cut out some routing commands simplifying it's command structure. Now, my Wingate server locks up solidly, randomly throughout the day. Thinking that I had a PC problem, I changed the motherboard. When it continued to lock up, I replaced the box with an XP box and it gave an error just before locking up - - disk error with paging file. The first box would just lock up .... frozen screen, frozen mouse, frozen keyboard. I think that a server 2003 box inside the bank is overloading the Wingate with DNS forward requests. I am at wits end. The Wingate box is accessed as a proxy server setting in internet explorer. It's ip address is not anybodys gateway in the building. Is there a better way to get dns info to the in-house dns server. Is that (possibly) why it is locking up? Any ideas?

[adrien]

Hi

there are known issues in 6.2.2 that we fixed which could be causing this. My first recommendation would be to update to 6.6.4, which is a free update for you if you have an existing license for 6.2.2

If you still have problems with that, I'd recommend trying WinGate 7, which has a completely new DNS infrastructure.

Regards

Adrien