Wingate 6 client on small business server 2003

[SeanLeR]

hi
i have a wingate 6 server running on a windows 2000 pc

we run microsoft exchange through a windows small business server 2003

i can not get the wingate internet client to work on the smb server and this is stopping our emails from working
i can get the internet to work via proxy on the smb server but not the email/exchange server.

Please Help
Thank You In Advance

[SeanLeR]

i have also tried scenario 2 out of the "mail server scenarios and configurations pdf file" and it does not work

[SeanLeR]

just to veryfy i used the second option (let it pass through the wingate server to the exchange server)

and this does not work

[SeanLeR]

SMTP mail cannot be sent or cannot be received in Exchange Server
View products that this article applies to.
Article ID : 895857
Last Review : April 2, 2005
Revision : 1.0
Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.


If you are running Wingate Proxy/Firewall
To work around this issue, you must replace the Wingate Proxy/Firewall. For information about alternative firewall programs that may replace Wingate Proxy/Firewall, contact C&C Software Solutions. For information about how to contact C&C Software Solutions, visit the following C&C Software Solutions Web site:
http://www.ccsoftware.ca/wingate/ (http://www.ccsoftware.ca/wingate/)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

is this true? is there no workaround???
i like wingate but if it will not work i will need to get something else (damm that would be a waste of money!)

[adrien]

Hi

That support response from MS looks like garbage, and recommending uninstallation of a competing product for no good reason is probably something they could be sued for.

However, I don't recommend using the WinGate Client for Exchange server to send mail. You should simply be able to either

a) direct exchange server to deliver to WinGate's SMTP server, or
b) set the default gateway on the exchange server to WinGate's IP, so that it can connect out for mail delivery through WinGate using NAT/ENS.

Adrien

[SeanLeR]

Hi Ardian

thank you for the help

just for interest sake here is the link to the article

http://support.microsoft.com/default.as ... -us;895857

enjoy the day

[SeanLeR]

Please excuse my bad spelling!! (i hate it when people spell my name wrong and here i am doing it to others)

[kgoodknecht]

Please excuse my bad spelling!! (i hate it when people spell my name wrong and here i am doing it to others)

As Adrien stated, WG Client should not be used on a server, it causes port conflicts because the client listens on the server ports.

Configure Wingate to send and receive mail for Exchange's mail domain as a Smart Host, (Wingate does an excellent job of reducing spam) Have Wingate deliver incoming mail for the domain to Exchange.

Configure Exchange SMTP virtual server to send all mail to the Wingate Smart host.

Install and SMTP connector in Exchange System Manager. Administrative Groups>First Administrative Group>Routing groups>First Routing group>Connectors. Add new SMTP connector, name the connector (I use SMTP) on the General tab, select "Forward all mail through this connector to the following smart host" If you use an IP the IP must be in brackets (e.g. [192.168.1.2]) Under Local bridgeheads, click Add and select your Exchange SMTP virtual server. Select the Address space tab, click add, under Address type choose SMTP then OK. In the E-mail domain use the default *, then click OK. and close System manager.