Issue with asp / downloads in Wingate 6.0.3

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Issue with asp / downloads in Wingate 6.0.3

Postby dbs » Sep 23 04 3:47 am

Dear Support,

We have a server running Windows 2003 and a network configuration with a Dlink 10/100 network card for external traffic and a Intel Pro Server 100/1000 for the internal lan.

We have noticed a problem after upgrading to 6 where files downloaded from the likes of Hewlett Packard would appear corrupted. After upgrading to 6.0.3 the problem is more evident with asp and other types of database's.

It occurs when for example logging onto a banking online system and once logged in simple tasks which would take you to other asp pages will simply time out or come up with user not logged in errors. The problem is also evident from the server completely by passing the proxy.

In troubleshooting this issue I have completely uninstalled Wingate and enabled routing and remote access to test. Both the server and clients responded 100% with Wingate removed. I then reinstalled Wingate and again the problem arrose with asp type websites.

Any ideas?
dbs
 
Posts: 5
Joined: Aug 10 04 3:07 am

Postby adrien » Sep 23 04 3:28 pm

Hi

That's pretty odd.

Normally in seemingly weird cases like this, we find there is something wrong with the routing configuration.

What does your route table look like? Do you have more than one default gateway (or one specified for more than one network adapter)?

Are you still running Routing and Remote Access with WinGate, or do you disable it when you run WinGate (R&RAS makes a mess of the results of the system IPHelper DLL which we use to get the system route table, so we recommend turning it off unless you really need it - otherwise WinGate has to try to correct the data).

Adrien
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland

Possible solution

Postby dbs » Sep 23 04 9:06 pm

Adrien,

I might of discovered the solution, first of all we had previously being using a 3com network that packed in so I replaced it with the Dlink card for the adsl connection. I used the same IP address as previously used, so I changed it from say 192.168.1.1 to 192.168.1.2 and specified to use this adapter as the default gateway in the WWW Proxy Service as oppossed to automatic.

So far so good.

Maurice
dbs
 
Posts: 5
Joined: Aug 10 04 3:07 am


Return to WinGate

Who is online

Users browsing this forum: No registered users and 8 guests