- Device Redirection Solutions
- Serial Port Solutions
- Programming Tools
- Contact Us
Most devices with serial port interface are supported. However, if your specific device doesn’t get redirected and connected properly, you might want to check if the correct drivers are installed on the client side.
Yes. This is one of the most common applications of our software.
Using our Serial Port Splitter product (sold separately), you’ll be able to split the virtual COM port created by Network Serial Port Kit in two or more ports, and assign multiple pieces of software to use those split ports.
If your license was purchased more than 1 year ago, this means your update subscription has expired and you need to purchase another update subscription to receive updates for another year. For pricing please go to:
Please copy all lines of the license key, including -----BEGIN/ ----END. If it still doesn’t work, please contact us at firstname.lastname@example.org or enter our live chat.
Sometimes software designed for use with specific COM port devices are configured to work only with a particular COM port (most often COM1). If this cannot be configured, you may use our Serial Port Mapper (sold separately) to assign a particular name for the virtual COM port created by Network Serial Port Kit (including COM1).
Network Serial Port Kit allows you to work with serial devices attached to another machine as if it were connected directly to your local machine, whereas Serial Port Redirector allows you to connect standalone serial devices having their own IP addresses in the network.
Sure! Please write an email to email@example.com explaining why you need an extended trial key and we’ll send you one as soon as possible.
In order to start sending and receiving data you need to open that port with some software, for example HyperTerminal. When you open the port, the dot will turn green and data can be transmitted.
After making sure it is our software that’s causing the BSOD, please do the following:
1) Go to the System Properties ("Windows + Break" buttons on the keyboard)
2) Open "Advanced" tab
3) In the "Startup and Recovery" section press "Settings" button.
4) Here you can see "Write debugging information" section. Choose "Kernel memory dump" and remember the path to the file - MEMORY.DMP
By default it's "%SystemRoot%MEMORY.DMP"
5) Reproduce BSOD once again
6) Go to the windows root folder and find that file: "Windows/MEMORY.DMP"
7) Zip this file and send it to firstname.lastname@example.org.
8) Also please send us your sysinfo. To get it you need to do the following:
Start -> Programs -> Accessories -> System Tools -> System Information File -> Save
Most probably you’re getting a BSOD, but your PC is not configured to show it. Please follow the instructions above to send us the kernel memory dump file.
Please make a screenshot of the error and send it to email@example.com. We’ll analyze the problem and get back to you with the solution as soon as possible.
1. Please check if you can query the serial device without using NSPK on the PC where it’s plugged.
2. Share the serial device using NSPK, create virtual connection to the shared com port on the same PC (no network is involved), connect an application to the virtual connection and check if you can query the shared device.
No, NSPK can also work with virtual com ports. You can create and share the virtual com port making the local and remote serial application communicate with each other.
Yes, you can do it. NSPK has command line utility and can be easily installed and configured using it. For instructions please go to:
There is no actual limit, the speed will depend on the application that speaks to com port. But if the “limit transmission speed...” option is disabled the speed will depend on the network quality and PC performance.
Yes it can. It runs as a service.