Two external adpaters and traffic routing

[Marcin]

Hi,

We are using Wingate 6.6.4.

Recently we acquired secondary ADSL line to improve the data transfer between our LAN based database server and external users. We would like to split the communication basically into two categories: 1 - one machine wita a static IP (we do not use DHCP) utilizes one external adapter; 2 - all other machines use second adapter. We went thorugh many posts on this forum and did not find similar problem. We are not "experts" in routing and Wingate configuration details, threfore going through "help" in Wingate, did not assist us either. Can anybody tell us, what is the simplest configuration model for our needs and how we should do it?

Many thanks in advance,
Marcin

[Nev]

Hello,

Yes Wingate is brilliant at this feature which I have utilised on occasion.

To access the different ISP's [connections] you can use the gateway feature in Wingate, am out of the office just now but that is one way to re-direct traffic.

Logan will chime in anytime and give you the full background on it, or maybe even a search of the forum?

[logan]

Logan will chime in anytime and give you the full background on it

The faith is strong in this one :).

Yup, WinGate can handle multiple internet connections, but in most cases, customers just want WinGate to round robin connections around multiple gateways to help improve internet speed and load capability. This is easy, but your scenario (having one client connect through WinGate through one internet connection, and then have all the others connect through WinGate and then through another internet connection) sounds a bit more out of the ordinary.

What will the one machine be doing on the internet. Will it be browsing websites, checking emails, or making any other other forms of outgoing request, or is it just there to listen for incoming database conenctions from the outside world?

It sounds like it's just there to listen for incoming DB connections. That being the case, you can simply do the following

- Make sure the Metric of the DSL connection for DB access has a higher metric than the DSL connection for general internet access. This will ensure that WinGate sees and uses the general DSL connection first and foremost.

- Have WinGate forward incoming DB conenctions to the DB server

- Give clients on the internet the IP of the DB DSL connection. When the clients connect to the DB through this IP, WinGate creates a hash table entry when it forwards the connection to the DB server. The hash entry remembers that the connections came through the DB DSL connection so when the DB server replies to the client, the connections from the DB server are made back through the DB DSL connection.

You will effectively have a DSL connection that services DB transactions alone and nothing else.

[Marcin]

Hi Logan,

Thanks for the reply - I did not notice it earlier, as I did not receive an email notification from the forum, eventhough it is set up to let me know about replies :-(

As I mentioned in my post, we are not too experienced in Wingate features, as well as my IT English is limited (I am writing from Poland), so I think that I understand the scenario, but please bear with us if I come up with further clarification questions.

Just to clarify our need here is more detailed description of the network ideal setup:

1. DB computer is part of the LAN (we use the database for ca. 20 LAN users) but also has to have high speed access for external users (approx. 3-5 users at a time); we tested with the provider the speed of connection/transfer rate and at the DSL rate of min. 3M/3M allows for "comfortable" access to read/write data; but the DB DSL line has to be free from other communication, as it seriously decreases the data transfer rate for external users; this DSL is a radio transmission transfer;
2. the second DSL line (cable) has 4M/512k rates and the upload cannot be increased due to the provider's technical limitations; we used this line for last couple of years and it is perfctly fine for 20 users LAN regular usage of WWW/email; that's why we want to keep this line for all other users usage only and sperate all the office communication from the other DSL line.

I hope that this helps to figur out what we are trying to achieve.

I will confrim if we were successful with set up based on your instructions.

Marcin