Hi Knut,
What exactly are you debugging?
Just a normal Uniface runtime? Do you use (e.g.) /deb from the command line of the client or the debug statement? In that case Uniface will create a Debug Thread that the Debugger will hook into. This is just inter-process communication, no port is used here. Maybe some "security" software is running on the host that prevents this?
When you debug a UServer or Web App Server then that is of course a different story. In that case the communication is done over TCP and that port needs to be open in the firewall. The port should be defined in the UST of the server in question.
It might be an idea to use
Process Monitor from Sysinternals and trace the Uniface client and Debugger. In case something is blocked or not accessible then Process Monitor probably can tell you.
I hope this helps.
Regards,
Daniel
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
Original Message:
Sent: 04-06-2022 10:29
From: Knut Dybendahl
Subject: UF Debugger Question
Ya'll,
The debugger works fine when activating inside our own network.
Everything works fine.
Some of the offices access our network via a firewall - and UF itself
works fine. However, when we try to activate the debugger from the
other side of the firewall, we crash.
How come / why? Do we need to open another port? How does UF
communicate with the debugger? All the resources needed for the
debugger is underneath the directory structure started using the /dir
switch...
So what am I missing??
Regards,
Knut
------------------------------
Knut Dybendahl
------------------------------