Checks for Running PypeServer Remotely

Checks for Running PypeServer Remotely

Checks for Running PypeServer Remotely

Basic Checking for Running PypeServer Across the LAN

On Kiosk

  1. Make Sure the remote seat firewall is not blocking the connection between the two computers.? Check if the firewall is on. It must either be off, or ports must be opened (IT department will know if ports are open).

  2. Check CodeMeterWebAdmin, Ensure CodeMeter is on as a LAN server.

  1. Get the IP address of the PypeServer computer.?Open a CMD window and type in IPCONFIG to get the IP address of the PypeServer computer.? Note this somewhere. It will be needed when you get to the remote side.

Remote Side

  1. Make Sure the remote seat firewall is not blocking the connection between the two computers.?Check firewalls on remote side and follow the same procedure as the kiosk.

  2. Check that the remote seat can communicate at a network level with the PypeServer kiosk.? Open a CMD window and type in "ping pypeserver",?or whatever the name of the computer is.

  1. You want the ping to not time out.? If it times out, IT needs to figure out why the two computers cannot see each other.?

  2. If it pings, these values should be < 10ms.? Typically they are <1ms.? If they go over 20ms, then remote performance is going to be slow and painful. IT will need to be advised to fix this.

  1. If there is no ping using computer name, then try the same with the IP address, e.g. Ping 192.168.1.19 (or whatever the IP address was of the kiosk that you noted). Make sure the remote seat codemeter license service is looking to the PypeServer kiosk for the license.

  1. Open CodeMeter-->WebAdmin. If the ping <kiosk computer name> worked, then set the server search list to the kiosk computer name.? If the ping for the IP Address worked, then set the server search list to the IP address.? Showing both options below:

  1. Check Registry Settings directing the app where to connect.??

Open Regedit and check the two locations for the correct settings:

  1. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\PypeServer

  2. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PypeServer

Make sure the first "PYPESERVER" is the kiosk computer name

If?remote seat connectivity varies in performance, or is intermittent, then from the Remote Seat:

  1. Check Ping again.?See if the ping has gone bad.? Do step Remote.2 again.??

  2. See if the LAN throughput is bad.? Navigate to \\PypeServer Staging and copy the big .exe file from there to the remote computer.? If this takes longer than, say 15-20 seconds, they have a throughput issue and IT needs to solve it.

    • Related Articles

    • LoneStar Machines Running Mach3

      LoneStar Machines Running Mach3 PypeServer for Lone Star Machines Using Mach3 Controllers Table of Contents 1 General overview of network layout 2 2 PypeServer Settings Overview 3 2.1 Basic Machine Settings 3 2.2 Machine Properties 8 2.3 Torch ...
    • Getting Started with PypeServer

      Getting Started with PypeServer (and Frequently Asked Questions) This document covers what to do in preparation for using the PypeServer software, and maintaining the PypeServer system. Contents 1 User Information 3 1.1 Overview 3 1.2 General Layout ...
    • Getting Started with PypeServer

      1 User Information 1.1 Overview · The PypeServer Kiosk is an industrially enclosed computer system that sits next to the pipe cutting machine. · PypeServer is currently (as of 2020) running Windows 10 Professional. It can also be run on Window 7 ...
    • Importing Into PypeServer

      Importing Into PypeServer How Importing Works This document describes the process of importing data that describes pipe parts. PypeServer creates these importers, though customers may contact PypeServer if they are interested in developing their own ...
    • Pypeserver with EdgeConnect Machines

      Pypeserver with EdgeConnect Machines PypeServer with EdgeConnect machines Machine configuration When configuring your machine, some preparatory steps are required in order to get meaningful test results. Getting axial directions correct This is done ...