How-to

Licensing validation — for network administrators

What the client contacts, five candidate causes with a test for each, and four remedies ranked by how little they ask of you.

What the client does

Graphite, and the Cobalt, Xenon, Argon and Lithium line, validate their registration by contacting our licensing server. This page is so you do not have to discover any of it by packet capture.

Hostnames tried verify.ashlarvellum.biz, verify.ashlarvellum.com.ua
Also tried directly 69.13.42.172
All of the above resolve to 69.13.42.172 (United States)
Protocol HTTP, plain text, TCP port 80 — not HTTPS
Licensing network (allowlist / VPN) 69.13.42.128/25

Two things in that table are ours to own, and we would rather name them than let you find them. The validation exchange runs over plain HTTP to an older server generation — there is no TLS in it, which matters for cause 4 below. And the client still carries a retired fallback address that no longer answers; on any path that reaches it, that costs roughly a 21-second black-hole timeout, which presents to the user as a hang rather than as an error. A replacement licensing system that moves validation to HTTPS is in development and retires this whole failure class. That does not help you this week, which is why the remedies below exist.

Five candidate causes, with a test for each

In the cases we have seen, the registration validated normally for months and then stopped, and the traffic still arrives — it is the completion that fails. Any of the following would produce that. We are not going to assert one; the tests are quick.

  1. DNS or TLD reputation filtering. Many EU security stacks (Olfeo, Stormshield, Fortinet web filtering and others) filter .ua and .biz names by category. This acts on the name, before resolution — a different mechanism from IP-level geoblocking, so the addresses being in the United States does not rule it out. Test:
    nslookup verify.ashlarvellum.biz
    nslookup verify.ashlarvellum.com.ua
    curl -v http://69.13.42.172/
    If the bare IP succeeds and the names fail, it is at the DNS layer.
  2. Path MTU black hole. PPPoE access in much of Europe runs an MTU of 1492 rather than 1500. Our response can exceed the path MTU, and if ICMP fragmentation-needed messages are dropped it is discarded silently. Test — reduce the size until it passes; that is your real path MTU:
    ping -f -l 1464 69.13.42.172      (Windows)
    ping -D -s 1464 69.13.42.172      (macOS)
  3. Transparent HTTP proxy on port 80. A proxy intercepts the request and fails its own leg to our older server. The client's traffic reaches us; the exchange does not complete. Test: compare the affected machine against a connection outside the firm — a mobile hotspot is sufficient.
  4. “Block unencrypted HTTP” policy, or TLS inspection. Increasingly common as a default. Our port-80 exchange has no TLS to inspect, so a policy requiring HTTPS will simply drop it. Test: check the gateway policy for plain HTTP to external hosts.
  5. IPS / DPI discarding the response payload. Test: gateway logs for 69.13.42.172 over port 80.

A blocked outbound port 80 is not among the candidates. If outbound 80 were closed nothing would reach us at all, and in the cases we have seen the traffic arrives.

Four remedies, in order of how little they ask of you

  1. A temporary code from support — nothing to configure. Write to us with the serial number; a temporary registration code gets the user working while the network question is settled.
  2. Activate manually for 1 day — fully out of band. The Secure window carries a button labelled Activate manually for 1 day (on Cobalt, Xenon, Argon and Lithium: Activate manually for a day). Pressing it reveals a Personal ID and the Serial number. Take those to https://www.ashlar.com/registration/Graphite from any device with working internet — a phone, a machine on another network — and it returns an activation code to type into the Activation code field. Nothing on the CAD workstation needs to work for this, and nothing needs to be installed. About two minutes; lasts one day. The dialog itself prints that URL as http://; use the https:// form. Note that the button itself opens a page on our licensing host — if that host is what your filter blocks, the page will not load on the workstation either, which is why the ID and serial go to the address above from another device.
  3. Split-tunnel VPN. Routes only our licensing network through an IKEv2 tunnel; everything else stays on your connection. Details and the prerequisite in the next section.
  4. Permit the licensing network. If you would rather allow it than tunnel it: 69.13.42.128/25, TCP port 80, plus the two hostnames above if name filtering is in play.

Split-tunnel VPN

Prerequisite — check before installing: UDP 500 and UDP 4500 outbound must be permitted. Many corporate firewalls do not permit them by default. If they are closed, this remedy is unavailable and remedies 1 and 2 are the answer.

We operate an IKEv2 service that routes only traffic destined for 69.13.42.128/25 — our licensing network — through the tunnel. All other traffic on the machine stays on your own connection. There is a signed Windows installer; it is not a configuration exercise. It can be left connected, or brought up for two minutes every thirty days to validate and then disconnected.

Guide: verify-vpn-tunnel-guide.ashlar.com

The registration-persistence check

This is independent of everything above, takes ten minutes, and is worth doing even if the network is at fault.

The program stores its registration in a protected location, so a registration must be entered while logged in as an administrator to persist. That is not the same as invoking “Run as administrator” from a standard user account. Three requirements, all of which must hold:

  1. The code is entered while logged in as an administrator.
  2. That administrator can write to the location where the registration is stored.
  3. The end user's own account can read it — otherwise the registration holds for you and not for them.

The test: enter the code, log off completely, log back on as the user, start Graphite.

Registration survives the logoutWhat it means
Yes Network path only. The remedies above are sufficient.
No Network and persistence. Persistence must be corrected as well, and no licensing remedy will substitute for it.

Worth knowing: each upgrade is a complete new installation. If the registration was entered under different rights before the upgrade than after it, that alone can account for a registration that used to hold and now does not.

One thing to tell your user

When validation cannot complete, the program shows a notice with a Later button that dismisses it so work continues. Users frequently report that the software “keeps asking to register” when what it is doing is warning them, and they re-enter codes they never needed to re-enter because they did not notice the button. If a DEMO button is offered instead, it should not be pressed — demonstration mode removes saving and printing. The user-facing version of all this is /software/licensing.

Contact

support@ashlar.com · 800 877-2745

If you would rather work this on a screen share than by email, say so and we will send a link. We would rather spend our time than yours.

Revision r1 · published 2026-09-04 · current.
Initial publication — what the client contacts, five candidate causes each with a test, four remedies in order of how little they ask, the split-tunnel VPN and its UDP prerequisite, and the registration-persistence check.

Permanent link to this revision: /software/licensing-network/r1