DTF Printer Software Disconnected? Fix Ethernet and IP Settings

DTF printer software connects your artwork workflow to the printer, but a “disconnected” message can stop production before a job begins. If the XINFLYING A2 printer-control software cannot connect, first confirm that the printer is powered and ready. Then check software compatibility, the Ethernet cable, the computer’s static IPv4 settings, and the network port.

The A2 service FAQ also specifies a Gigabit Ethernet connection and directs users to inspect the mainboard network port if the earlier checks pass. Follow the settings for your exact printer and controller rather than copying values from another machine.

Do not copy the A2 IP address into another printer without confirmation. Static IP values, controller software, and network-adapter requirements can vary by printer model and controller configuration.

What Is DTF Printer Software?

The term DTF printer software can describe two parts of a DTF workflow:

• RIP software processes artwork, color profiles, white-ink layers, ink channels, and print output.
• Printer-control software communicates with the printer controller, applies machine settings, and sends or manages print jobs.

A “disconnected” warning usually points to the communication path between the printer-control software, computer, and printer. It does not automatically mean that the RIP software or printer mainboard must be replaced.

Why Does DTF Printer Software Show Disconnected?

Common causes include:

• the printer is off, still starting, or stopped by a controller alarm;
• the installed software or version does not match the controller;
• the Ethernet cable is loose or damaged;
• the computer and printer use incompatible or duplicate IP addresses;
• the computer is connected through an unsupported network port or adapter; or
• the printer’s mainboard Ethernet port is damaged or unstable.

Check these causes in order. Starting with power, compatibility, and the physical connection can prevent unnecessary software installation or board replacement.

Diagnose the Connection in Layers

Work from the simplest physical condition toward software and hardware isolation.

Record existing network values before changing anything. Changing the wrong adapter or assigning a duplicate IP can disconnect another device.

1. Confirm the Printer Is On and Ready

A controller cannot accept a software connection while the printer is off, still booting, or stopped by a board-level fault. Confirm that the normal startup sequence completes and that no headboard or mainboard warning appears.

If the machine shows a code, flashing board LED, or incomplete startup, diagnose that condition first. A network-setting change will not repair a controller that is not running normally.

2. Verify the Software and Controller Version

The A2 FAQ lists the software version as an early check. Confirm that the installed printer-control software is the version supplied or approved for the exact controller and firmware.

There is no single DTF printer software download that works with every machine. Before installing or updating software, verify:

• the printer model and controller board;
• the controller firmware version;
• the approved printer-control software and version;
• RIP software compatibility; and
• the supported Windows version and network requirements.

Choose software based on documented compatibility, required workflow features, and available technical support—not on a similar-looking interface or an unrelated download page.

Record:

• application name and version;
• printer or controller profile selected;
• Windows version;
• whether the connection worked before; and
• any software, firmware, or computer change made before the fault.

Do not install a random driver or controller package from an unrelated printer. A similar interface does not guarantee protocol or firmware compatibility.

3. Check the Ethernet Cable and Connection

Reseat the cable at the computer and printer with the equipment in the state specified by the manual. Inspect the plug tabs, connector shell, cable jacket, and port for damage or contamination.

If possible, test with a known-good cable of the required category and length. Avoid unverified couplers or a complex office network while isolating the fault. A direct printer-to-computer connection may be appropriate when the model’s setup guide specifies it.

4. Verify the Computer’s Static IPv4 Address

The printer and computer must be on compatible network addresses without using the same address.

A2-specific setting: the supplied FAQ lists 192.168.127.11 as the computer IP address. It states that the first three number groups must match the printer network and that the final number must not be 10, which is reserved in that setup. Before applying this value, confirm the documented printer IP address, subnet mask, and exact controller or firmware version. Treat the value as A2 service information, not a series-wide default.

Before changing the adapter:

1. Save a screenshot of the current IPv4 address, subnet mask, gateway, and DNS settings.
2. Identify the physical Ethernet adapter connected to the printer.
3. Confirm the printer’s documented IP address, subnet mask, and any gateway requirements.
4. Assign the documented computer address, or another approved unique address in the required subnet.
5. Avoid changing Wi-Fi or another business-network adapter by mistake.

If the computer is managed by an IT department, obtain approval before changing network settings.

5. Use the Required Network-Port Speed

The A2 FAQ says the computer connection should use a Gigabit Ethernet port and warns that a 100 Mbps port may fail to connect or may be unstable. Confirm the requirement for the exact model before purchasing an adapter.

When an approved USB-to-Ethernet adapter is used, verify that Windows recognizes it consistently and that power-saving behavior does not remove it during production. Keep the adapter model and driver details in the support record.

6. Inspect the Mainboard Network Port

If the printer is ready, the approved software is installed, the cable is known-good, and the IPv4 settings are correct, the mainboard Ethernet port is the next component to investigate.

With the printer powered down and isolated according to the service procedure, inspect for:

• a loose or damaged port shell;
• bent or contaminated contacts;
• a plug that does not lock;
• evidence of cable strain.

After the physical inspection, restore power only according to the approved procedure. If the model provides Ethernet link LEDs, record whether they remain off, illuminate normally, or behave intermittently during a controlled connection test.

Board-level repair or replacement should be performed only after model-specific confirmation. Network ports are part of the control system, and a board change may require configuration or firmware work. If the earlier checks pass but the connection still fails, send the evidence to XINFLYING support before replacing the board.

If the Connection Is Intermittent

An intermittent link needs evidence from the moment it fails. Note whether disconnection happens:

• when the carriage starts moving;
• after a fixed period of inactivity;
• when another network adapter connects;
• only during large print jobs; or
• after the cable or connector is moved.

This timing helps separate cable strain, adapter power behavior, IP conflict, and controller instability.

DTF Printer Software FAQ

Get Help With DTF Printer Software and Network Settings

Different XINFLYING DTF printer configurations may use different controllers and network settings. If the software still shows disconnected, send XINFLYING the printer model, software version, network-setting screenshots, and cable or port test results so the correct settings and next test can be confirmed.