Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

SMTP not working after WinXP XP2 Upgrade

Sep 09 04 5:27 am

Hello,

I noticed that after upgrading WinXP to SP2, the SMTP of wingate is not working/routing emails anymore. I changed the firewall settings of WinXP to allow port 25 (TCP & UDP) but still thesame problem.

jiandc

Sep 09 04 10:48 am

What if you try adding the WinGate exe to the allow list rather than just the port?

Regards

Neil

Sep 09 04 4:17 pm

Also, there is an incompatibility between WinGate's Gateway features (pre-routing) as configured on the gateways tab for a service, and XP's firewall, since XP's firewall translates source port numbers for outbound connections regardless of whether it needs to or not (i.e. it doesn't need to but it does anyway), this means the mechanism we use for pre-creating hash entries for routing and interface/gateway selection breaks.

So we recommend if you need a firewall on the WinGate machine, use WinGate's firewall.

Adrien

Sep 09 04 6:07 pm

I already allowed Wingate in XP Firewall prior to the Port.

Should I DISABLE XPs Firewall, we are behind a PIX firewall anyway.

Sep 09 04 6:15 pm

Easy to test - try turning XP's firewall off. If SMTP begins working, then it's something related to XP's firewall and should be fairly easy to figure out then. If not, then something else in your config has changed to affect this and we'd need to look at other things.

If you're behind a PIX firewall and you have WinGate's firewall on, the odds of anything happening is slim.

Sep 09 04 7:01 pm

Disbaled XP Firewall and still thesame problem.
Below is a part of the SMTP Log file.


09/09/04 08:42:24 digitalsender 0000000023 Requested: SMTP In: mail from jiandc@hotmail.com to 3 recipients (47kb)
09/09/04 08:42:24 digitalsender 0000000023 Traffic 434 48033 0 0 2s
09/09/04 08:44:24 digitalsender 0000000032 Traffic 130 33 0 0 0s
09/09/04 08:46:24 digitalsender 0000000047 Traffic 130 33 0 0 0s



09/09/04 08:48:06 127.0.0.2 <system> 0000000056 Error: Connection (MX Record) to jcs3.faxsav.com. for domain faxmail.com failed
09/09/04 08:48:06 127.0.0.2 <system> 0000000056 Error: Connection (MX Record) to jcs4.faxsav.com. for domain faxmail.com failed
09/09/04 08:48:06 127.0.0.2 <system> 0000000056 Error: Connection (MX Record) to njs2.faxsav.com. for domain faxmail.com failed

Sep 10 04 2:52 pm

Which version of WinGate are you using? Just searched through all your posts, but could not find anything to tell me that.

Also, Adrien just suggested that you try to connect to the host specified using telnet on port 25. If you can reach it, we know that the connection out works to that host.

Sep 12 04 10:38 pm

Hi,

we have WG5.2.3 bulid 901.
i tried to telnet<host>:25 but could not connect.

Sep 13 04 10:34 am

Alright, now, from a command prompt run nslookup. Then, type a set type=all in the window that opens. Then type the name of the host (faxmail.com)

You should see something like:

Non-authoritative answer:
faxmail.com nameserver = jcs1a.faxsav.com
faxmail.com nameserver = dcs2.netmoves.com
faxmail.com nameserver = njs1.faxsav.com
faxmail.com nameserver = nys2.netmoves.com

faxmail.com nameserver = dcs2.netmoves.com
faxmail.com nameserver = njs1.faxsav.com
faxmail.com nameserver = nys2.netmoves.com
faxmail.com nameserver = jcs1a.faxsav.com
dcs2.netmoves.com internet address = 204.124.244.65
njs1.faxsav.com internet address = 165.251.8.64
nys2.netmoves.com internet address = 165.251.28.71
jcs1a.faxsav.com internet address = 209.67.18.65

This tells us that DNS is working from the client. (If you get the same type of response). Can you check that it happens?

As a side thought, you can upgrade to 6.0.2 - your 5.2.3 key will work with it.

Sep 14 04 1:26 am

Hello,

I tried the command and got thesame response.

I also tried to upgrade our Wingate but during the activiation, I get the message "ERROR: The activiation file is invalid".

jian

Sep 14 04 2:32 am

Hi,

I downloaded 6.0.2 build 1001 and tried to activiate. Only the VPN got activated but still had thesame error message with Wingate License.

With the previous 6.0.1, both license cannot be activated.


jiandc

Sep 14 04 8:49 am

Can you get a trial license activated?

If you check your WinGate folder, there will be a two files ending in .lic. What is the size of each of those files, please?

Sep 15 04 1:18 am

I activtaed the license but still got thesame error. Pls see below.

09/14/04 13:30:17 digitalsender 0000000183 Requested: SMTP In: mail from jiandc@hotmail.com to <faxnumber>@faxmail.com (59 KB)
09/14/04 13:30:17 digitalsender 0000000183 Traffic 360 60477 0 0 2s
09/14/04 13:30:22 127.0.0.2 <system> 0000000189 Error: ==== Connection to jcs2.faxsav.com failed
09/14/04 13:30:22 127.0.0.2 <system> 0000000189 Error: ==== Connection to jcs3.faxsav.com failed
09/14/04 13:30:22 127.0.0.2 <system> 0000000189 Error: ==== Connection to jcs4.faxsav.com failed
09/14/04 13:30:22 127.0.0.2 <system> 0000000189 Error: ==== Connection to pss1.faxsav.com failed
09/14/04 13:30:22 127.0.0.2 <system> 0000000189 Error: ==== Connection to pss2.faxsav.com failed
09/14/04 13:30:22 127.0.0.2 <system> 0000000189 Error: ==== Connection to pss3.faxsav.com failed
09/14/04 13:30:22 127.0.0.2 <system> 0000000189 Error: ==== Connection to infinity.faxsav.com failed

Sep 16 04 7:37 pm

I am still having problems sending emails via Wingate SMTP. Hope someome can share his/her idea on how to solve this.

Thanks

Sep 16 04 9:55 pm

Hi

The fact that WinGate cannot connect to these servers, and you also cannot connect from the WinGate machine using telnet on port 25 to these servers means something is stopping you connecting.

Can you deliver mail to anywhere else? Are you able to connect to any other mail servers on port 25? Is it just port 25 that is blocked (i.e. by XP's firewall), or all ports?

Is it only connections to these hosts that fail, or do other connections fail as well? If it is only these hosts, are you sure they are even there and responding to connections?

Adrien

Sep 17 04 2:51 am

Its ok now.
It was McAfee VirusScan Enterprise 8i blocking port 25 againts worms.


Thank you very much for all your responses.
Post a reply