Digirip - Connecting to TCPIP Port: Part 3

1. This is **Part 3** of a three-part series on configuring printer port connections in DigiRIP.
2. This section covers **Reason #3** for TCP/IP printing failure: Another program is already using the same TCP/IP port.
3. This applies when: Firewall and antivirus are not blocking the connection WHAT A PORT CONFLICT IS

• The printer control software is configured correctly
• Printing to **TCP/IP 127.0.0.1: 9100** still fails

1. Only one application can listen to a TCP port at a time.
2. If another program is already using **port 9100**, the printer control software cannot receive print data. DOWNLOADING TCPVIEW

1. TCPView is a Windows utility that displays all active: TCP connections
2. Open a web browser.
3. Search for **TCPView Microsoft**.
4. Download **TCPView** from the Microsoft website.
5. Unzip the downloaded file. RUNNING TCPVIEW

• UDP endpoints

1. Run **TCPView64.exe**.
2. TCPView will display all active TCP and UDP processes on your system. IDENTIFYING PORT 9100 CONFLICTS

1. In the TCPView search field, type: `127.0.0.1`
2. Look for entries using: **Local Address:** 127.0.0.1

• **Local Port:** 9100

1. If a program other than the printer control software is using port **9100**: DigiRIP will not be able to send print data
2. The listed process name shows which application is occupying the port. RESOLVING THE CONFLICT

1. Identify the program using port **9100**.
2. Run a web search for the program name to determine its function.
3. Resolve the conflict by: Closing the application
4. Once the program releases port **9100**, the printer control software will be able to receive data. END OF GUIDE

• Disabling the application
• Uninstalling the application if not needed

This completes Part 3 of the DigiRIP printer port configuration series. Please review Parts 1 and 2 if additional troubleshooting is needed.