Re: Service entry points over VPN

Hi Michael,

I'm using RDi SEP debugging over FortiNet VPN too - and I don't have to many problems ... most of the time.

Sometimes, I have to start the debugger with STRDBGSVR on the target machine first, because otherwise my RDi will freeze, when I try to set the SEP.

And sometimes the debugger-connection is dropped because a IP packet gets lost - and the debug-session is ended "prematurely".

Which version of RDi is your colleague using? Are the PTFs current? There are some debugger PTFs that should be applied.

HTH
Daniel

Am 22.10.2025 um 17:50 schrieb David Gibbs via WDSCI-L <wdsci-l@xxxxxxxxxxxxxxxxxx>:
On Wed, Oct 22, 2025 at 10:05 AM Michael Quigley <MichaelQuigley@xxxxxxxxxx>
wrote:

I have a co-worker who works remotely. They're using our corporate
standard Fortinet VPN client. Most things work fine for her, but she can't
get Service Entry Points (SEP) to work. None of the ports are blocked on
the firewall. If she selects to set an SEP, the dialog goes away and
nothing shows in the IBM i Service Entry Points view.

I've never had a problem using SEP debug over a VPN.

AFAIK, SEP debug uses the standard ports to communicate.

Any chance you can try a different VPN?

david

--
IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding in the American Diabetes Association's Tour de Cure to raise
money for diabetes research, education, advocacy, and awareness. You can
make a tax-deductible donation to my ride by visiting
https://mideml.diabetessucks.net.

I may have diabetes, but diabetes doesn't have me!
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.