Problems receiving e-mail with wingate

[marcojoel]

Hello there
Today I changed my internet connection to another provider. I Installed the Router and the internet is working fine. I have wingate configured and I have no problems in the internet.
But I have a problem in my e-mail accounts. I have 2 machines that do not go thru Wingate and they send and receive e-mails with no problems. But the machines that go through Wingate...they receive...but cant send e-mails.
(P.S.: I do not use the e-mail service of wingate)

What can be the problem? I don't Know whow to fix this...:(

Can anyone help me please?

Thanks

[adrien]

Hi

Can any of your machines send mail?

It is now common for ISPs to block connections out on port 25 (the one used to send mail). At a guess, I'd assume that your new ISP does that, and you'll need to either

a) get them to not block port 25 for you (some of them will do this); or
b) configure your mail clients to send to your ISP mail server.

Adrien

[marcojoel]

Every machine send/receive mail when I configured outside wingate. When i configure wingate they receive mail with no problem and they cannot receive mail. And in some sites (like homebanking) they just cant acces to them.

I believe that is some configuration on the wingate server but i just cant understand what.

Thanks

[Nev]

Hi, what you could do it to check the adaptor usage in Wingate like this:



Also, but unlikely, it could be that the MTU to the ISP is wrong, to test this you can ping a webserver for example:

ping -l 1472 bigpond.com -f

Here it is 1,500 allowing for a 28 byte header:

Drive_C:\> ping -l 1472 bigpond.com -f

Pinging bigpond.com [144.135.18.32] with 1472 bytes of data:

Reply from 144.135.18.32: bytes=1472 time=654ms TTL=243
Reply from 144.135.18.32: bytes=1472 time=545ms TTL=243
Reply from 144.135.18.32: bytes=1472 time=531ms TTL=243
Reply from 144.135.18.32: bytes=1472 time=523ms TTL=243

Ping statistics for 144.135.18.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 523ms, Maximum = 654ms, Average = 563ms

Drive_C:\> ping -l 1473 bigpond.com -f

Pinging bigpond.com [144.135.18.32] with 1473 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 144.135.18.32:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

There is a back end feature in Wingate for the external connection to allow MTU over ride if it is relevant, which may also be part of the problem for SSL // banking you mentioned.

Otherwise check that Port 443 [or other as required] is allowed in the WWW Proxy perhaps.