OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Networking => Topic started by: ChrisGWarp on January 31, 2026, 06:34:37 am

Title: DDNSAPC.CMD: Communication could not be established with the server.
Post by: ChrisGWarp on January 31, 2026, 06:34:37 am
Hi everyone,

Has anyone else had the issue when running the DDNS Server Administrator (DDNSAPC.CMD) - or the DHCP Server Administrator for that matter?

I get a momentary pop of a dialog but then it says "Communication could not be established with the server."

Named is most certainly running and functional.

Cheers!

-Chris
Title: Re: DDNSAPC.CMD: Communication could not be established with the server.
Post by: ChrisGWarp on February 01, 2026, 07:02:49 am
I've attached a screen shot of the error, if that helps.

If I have too, I'll disassemble the jars back to java and take it from there (done that more than once...).

-Chris

Title: Re: DDNSAPC.CMD: Communication could not be established with the server.
Post by: Steven Levine on February 01, 2026, 07:22:52 am
Has DDNSAPC.CMD ever worked for you in the past?

Looking at the script, I wonder if an argument is required.  Typically IBM would create a Desktop object to run the script and provide the site specific argument in the object parameters.
Title: Re: DDNSAPC.CMD: Communication could not be established with the server.
Post by: ChrisGWarp on February 02, 2026, 10:47:28 pm
Nah. I was being a complete brain dead idiot. Too tired.

As it turns out, the error message was exactly correct. It could not connect to the server. Which server. DDNSAPS.CMD... Normally started from tcpstart.cmd Doh! This was done to implement remote config, but it's also used locally.

Funny how it whinges that it can't connect to a server when it's not running.

Hence the brain dead me bit...

Please return to your normal programming, whilst I reboot myself. :)

-Chris