Skip to main content

Greetings All, 

I am running into an issue when using Accuterm.

I just switched my internet provider to Startlink.  Startlink for home use does not have a dedicated IP address so I am using a GL.Inet GL-SFT1200 router that I have a  wireguard tunnel running on the router.

I also I can log in direct from my PC using Surfshark with a -dedicated IP with no issues when connecting.

When using wireguard I am able to connect but get an error message - "WED requires AccuTerm 2000 or later to run!  " 

I am also trying to print to port 9100 to the wireguard but have not gotten far on this. 

Am I missing something in the set up? 

Thank you in advance. 

Greetings All, 

I am running into an issue when using Accuterm.

I just switched my internet provider to Startlink.  Startlink for home use does not have a dedicated IP address so I am using a GL.Inet GL-SFT1200 router that I have a  wireguard tunnel running on the router.

I also I can log in direct from my PC using Surfshark with a -dedicated IP with no issues when connecting.

When using wireguard I am able to connect but get an error message - "WED requires AccuTerm 2000 or later to run!  " 

I am also trying to print to port 9100 to the wireguard but have not gotten far on this. 

Am I missing something in the set up? 

Thank you in advance. 

Hi David - 

I'm not sure what is happening in your environment. I'm not able to reproduce your setup, but I did try running AccuTerm on a laptop, connecting to a QM server over tailscale network. Tailscale is based on wireguard, so should be similar to what you are doing. The error you are seeing happens when one of the AccuTerm host programs starts and is unable to detect that AccuTerm is running on that terminal session. From the host, its basically doing PRINT CHAR(27):CHAR(2):'I', then looking for a response from the terminal. If the session is running AccuTerm, AccuTerm sends back its information. If the response takes too long (several seconds), or is blocked or corrupted, you would get the error message you see.

Thanks, Pete

Terms & ConditionsAccessibility statement