I've configured sstp vpn on a tmg cluster several months ago and it worked fine. I followed mainly isaserver.org way to setup all.

Recently it stopped working and remote clients just say Error 0x800703e3 The I/O operation has been aborted because of either a thread exit or an application request.

L2tp works fine.

The listener is bound to the default cluster ip and other listeners are bound to different ip addresses.

The certificates are private, but valid (so it seems to me). Clients have their own certificates from the same CA and crls are published externally, delta crl too.

Tmg system is a cluster of 2 3 leg servers, joined to a domain and integrated with Exchange Edge and Forefront Protection for Exchange.

I cannot find documents on this error relating to tmg vpns.

Can You suggest me how to diagnose the problem on the server side? How to search?

Thanks,

Stefano

• Edited by orocchi Saturday, July 07, 2012 2:09 PM
• Changed type Nick Gu - MSFTMicrosoft contingent staff, Moderator Monday, July 16, 2012 2:47 PM

Hi,

Thank you for the post.

Does this issue occur to all the sstp vpn clients? According to the error code 0x800703e3, it looks like a network issue/firewall is blocking all the packets. do you receive any error in the live logging?

Regards,

sorry for long time and thanks for your answer.

Yes, it seems that no user can access via sstp anymore. I'm planning to rebuild the listener on another ip and look what happens.

I tryed without other firewalls over me, but the result is the same. The problem seems to be on tmg.

This behavior started after a Microsoft assistance over edgesync, but I don't know if the facts are linked (it's an integrated solution tmg+edge)

My problem is that i'm not so used to monitor the problems on tmg, so i'd like some suggestion on how to use the console and tools to monitor the behaviours during vpn attempts.

Thanks

Have you ever found the reason why? We have tmg+edge as well and the same error (0x800703e3).... Really would appreciate help. Thanks, Oliver