Prioritizing Gateways (ENS) and Bandwidth Control

[Bob Tucker]

Dear Sirs,

I have two questions: First, how does one prioritize gateways in ENS without interecepting traffic in various services and prioritizing gateways in those services? We have two gateways. One has much greater bandwidth than the other, and I would like to use the higher bandwdith gateway for web browsing and most Internet access We have problems with some sites when Wingate is configured to intercept ENS in the WWW proxy. Unfortuantely, access to these sites is routinely required for work. The failure appears to occur in a script process on both sites. I enabled drip-feed in the WWW proxy when the intercept was enabled, but the WWW proxy still did not work where ENS does. Thererfore, I use ENS without intercepts. However, by not using the WWW proxy, I cannot seem to find how to prioritize traffic using ENS. Is there a way to do this? Or is there a way to prioritze all traffice in Wingate?

Second question: I would like to use bandwidth control. However, I am reluctant to do so without some additonal information as Wingate is on a production machine, and I do not want to make configuration errors which would cause problems. Do you have any idocument that speaks to this?

Thank you very muc for your assistance.

Kindest Regards,

Bob Tucker

[genie]

Hi,

Unfortunately there is currently no simple way of prioritizing multiple gateways for ENS - this feature is planned for later releases.

As of your second question, bandwidth throttling, there is a chapter in Wingate doc file, dedicated to throttling setup. Let me know if you have any difficulties - I can give you a hand then.

[Bob Tucker]

Dear Gene,

Thank you very much for your reply. I read the help file as well as posts in this forum related to Bandwidth Control. I am sorry I was not more explicit. I was trying to get a much better understanding of what might be possible before I made a request. The Internet connection here provides access for inbound Terminal Services Web sessions as well as Wingate. I am trying to see if it is possible to reserve a certain amount of bandwidth for Terminal Services Web so that TSWeb sessions do not freeze when other Internet usage is too great. I looked at this briefly with Sniffer and tried to correlate the intermittant problems in TSWeb with specific Internet activity. I am surprised to see that it may be SMTP (but that is not really clear). If it is possible to reserve bandwidth for TSWeb, that would be most useful. Else, I will try to control SMTP bandwidth. Any observatinos or assistance you might have in in terms of TSWeb would be greatly appreciated.

I am sorry to hear that there in no means to prioritze gateways for ENS per se. I will need to revisit proxy usage. Two questions related to that: I notice that if I intercept ENS, I have problems with some aspects of web browsing - e.g. HTPPS. If, however, I configure clients to use proxies directly, I do not have these problems. Is that observation correct? Speed sometnines seems to be a problem when proxies are used. Some sites time-out. That seems to be the problem with scripts at some sites that users need to access when accessed via proxies. Is that observations correct?

With Kindest Regards,

Bob Tucker

[genie]

Yes, you are quite right about TRs - if you intercept a connection, then the proxy should know how to handle it.

As of the bandwidth, you can reserve (or, in case of Wingate BT, allocate) the certain traffic for TSWeb, so that it will also be guaranteed to receive the certain share (like 100Kbit/sec or 50% of all available bandwidth).

[Bob Tucker]

Dear Gene,

In throttling vis a vis TSWeb, what protocol would I select for TSWeb? How would I set up the rule? I apologize for the questions. I do not want to shoot myself in the foot as this machine is in production.

Kindest Regards,

Bob Tucker

[genie]

Hi, Bob

Don't be so apologetic - what else we are here for?
Well, I am not really familiar with TSWeb protocol. But from what I know it is http-based and therefore will be operating through port 80. SO you have to create a restriction first, saying that the restriction will gurantee X kbit/sec. Then you create a rule which has a destination IP address of your TSWeb server and port number 80 (tick bi-directional checkbox, too) and set the restriction for this rule to be the one you've just created.

[Bob Tucker]

Dear Gene,

I think that bandwidth throttling related to TSWeb may be a problem in that TSWeb sessions are negotiated in HTTP but are are RDP protocol. In effect, TSWeb sessions are just Terminal Services sessions, and I do not know much about RDP. RDP uses port 3389 by default, but that can be changed. I do not know how to approach using Wingate to control RDP bandwidth. This is the reason that I looked at what else might be causing congestion when TSWeb sessions slow. Please point me in the right direction here. If it is possible to control RDP bandwidth, I will try that. Else, I will try to control other protocols and test until I get to a better configuration.

With Kindest Regards,

Bob Tucker

[genie]

Yeap. Then you also need to use the same restriction for a rule where port 3389 is used as a filtering criteria.