Please Help!!!

[fmassena]

I have the wingate 6.2.1 installed on my server (Win2003 SBS, 2 nics - one internal and one external), I am not using SMTP, DHCP, DNS, IMAP nor POP3 services.
I can receive e-mails but can't send... well I send them but they sit on the Queue (exchange) for a long time.
Anyone has clue? I have been looking at that server for a while now and can't figure it out.
Please help!
thanks in advance

[jamesc]

Well presuming the Exchange server is a computer behind WinGate, the first thing you will want to do is make sure you can resolve DNS addresses and have NAT connectivity

(Windows) Start menu --> run --> cmd --> ping www.wingate.com
(Windows) Start menu --> run --> cmd --> ping 210.55.214.36

If you do not have NAT connectivity then please review this guide.
http://support.qbik.com/index.php?_a=kn ... ils&_i=147


The next thing you want to do is confirm that the SMTP server in WinGate is disabled; and I know you have said you are not using them, but there is a difference between not using them and disabling / stopping them.

[Nev]

I have the wingate 6.2.1 installed on my server (Win2003 SBS, 2 nics - one internal and one external), I am not using SMTP, DHCP, DNS, IMAP nor POP3 services.
I can receive e-mails but can't send... well I send them but they sit on the Queue (exchange) for a long time.
Anyone has clue? I have been looking at that server for a while now and can't figure it out.
Please help!
thanks in advance

G'day,

Now I have exactly the same fault on Win 2k3 R2, it went down around 08:00Z on the 15th of February last.

I can send [SMTP] directly from the server if I uninstall [(^_*) unheard of] Wingate and use Windows firewall.

BTW: OP just to confirm it isn't a MTU fault over a PPP circuit by any chance? --> as here here and here

My personal suspicion is one of the following WSUS'ed patches applied just prior:

KB924667
KB931836
KB918118
KB928843
KB926436
KB925720
KB928255

Anybody had this one?

[adrien]

another thing to check is your ISP. more and more of them have started blocking connections to anything on port 25.

but that doesn't tie in with it still working through the windows firewall.

The KB articles for those service packs don't look like they affect your network stack, but you never know.

So even connecting directly from the WinGate machine with WinGate installed, it breaks?

Adrien

[Nev]

another thing to check is your ISP. more and more of them have started blocking connections to anything on port 25.

but that doesn't tie in with it still working through the windows firewall.

The KB articles for those service packs don't look like they affect your network stack, but you never know.

So even connecting directly from the WinGate machine with WinGate installed, it breaks?

Adrien

Hi Adrien,

The ISP has a link open for the remote gateway, it does connect, authenticate and time out with no data exchanged on Port 25.

A basic pc dropped onto the connection instead of the Win2k3 Server works normally.

I can send if I disable Wingate's firewall and stop the service.

Odd one indeed.

[Nev]

Hi all,

Well there has been movement.

To access the remote domain SMTP gateway I have had to relax the firewall by opening 1024~4096 ports.

Prior to this development I always used the 'High' setting!

Haven't tried uninstalling the service packs, but the peculiar thing is that I have a notebook also with Win2k3 and Wingate 6.2.1 which sends perfectly via this same ISP and remote domain gateway with a 'High' setting in the Firewall.

So I am at a loss.

[Nev]

Hi all,

Co-incidentally I think the fault was KAV.

As below KAV suddenly became invalid without provocation ;-(

03/12/07 17:42:47 Kaspersky AntiVirus for WinGate Data file update for 'Kaspersky AntiVirus for WinGate' completed successfully

03/12/07 22:13:25 Licence Manager The license for Kaspersky AntiVirus for WinGate has expired or is invalid. Kaspersky AntiVirus for WinGate functionality will not be available

The only solution to this was deactivate the licence and remove / re install the product then reactivate the key. Repair of the product did not 'repair' the licensing fault.

At this point I noticed the SMTP server functioned normally with a 'High' firewall setting.