How does the 7-day free trial work?
How to uninstall Cursr?
How to update or downgrade Cursr?
How compatible is Cursr with 3rd party applications?
What should be whitelisted for Cursr on secured networks?
KVM - Connection Issues Between Devices
Cursr uses 'TCP' and 'UDP' communications which can be blocked by firewall, therefore first make sure there are no Inbound Firewall rules blocking 'UDP' or 'TCP' communications for 'cursr.exe' or 'Cursr'. By default these should be allowed on Private networks unless you chose otherwise, therefore check if your network is set to Private or Public and then check corresponding firewall settings, if everything looks correct sometimes it also helps to switch between the Private and Public setting and back to reapply the firewall configuration. Alternatively to avoid unnecessary search of individual firewall rules you can also temporarily disable firewall (not recommended on Public network) to check if it will help, before tracking down individual rules causing the issue.
Afterwards, make sure UDP and TCP ports used by Cursr are not occupied or reserved (Default values for 'Coms' UDP/TCP=4440 and 'Discovery' UDP=28777 (61650 for v1.7.3-prerelease.8 and earlier) ports can be changed in settings):
macOS:
If the above did not help open up all instances of Cursr and try connecting manually by clicking red 'connect' button in bottom right corner of Cursr. You should see popup appear on all instances saying ' Scanning for all available devices' which will change as connection gets set up.
If popup does not appear on one or more instances:
Afterwards, make sure UDP and TCP ports used by Cursr are not occupied or reserved (Default values for 'Coms' UDP/TCP=4440 and 'Discovery' UDP=28777 (61650 for v1.7.3-prerelease.8 and earlier) ports can be changed in settings):
macOS:
- Check occupied TCP: sudo lsof -iTCP -sTCP:LISTEN -nP | grep :4440
- Check occupied UDP: sudo lsof -iUDP -nP | grep -E ':(4440|28777)'
- Check occupied TCP: netstat -tln | grep :4440
- Check occupied UDP: netstat -uln | grep -E ':(4440|28777)'
- Check occupied TCP: Get-Process -Id (Get-NetTCPConnection -LocalPort 4440).OwningProcess
- Check occupied UDP: Get-Process -Id $(Get-NetUDPEndpoint -LocalPort 28777, 4440 | Select-Object -ExpandProperty OwningProcess -Unique)
- Check reserved TCP: netsh interface ipv4 show excludedportrange protocol=tcp
- Check reserved UDP: netsh interface ipv4 show excludedportrange protocol=udp
If the above did not help open up all instances of Cursr and try connecting manually by clicking red 'connect' button in bottom right corner of Cursr. You should see popup appear on all instances saying ' Scanning for all available devices' which will change as connection gets set up.
If popup does not appear on one or more instances:
- Make sure that all devices are connected to same network
- Make sure that the same 'Network Range' is available and selected in 'Virtual Switch' settings across all Cursr instances. If these are not matching and matching options are not available try clicking 'Refresh Network'.
- Make sure that 'Hide from Network' is not enabled in 'Virtual Switch' settings
- Make sure that all Cursr instances have same 'Discovery Port' set in 'Virtual Switch' settings
- macOS - open Wi-Fi settings, for connected network open 'Details...', select 'TCP/IP' section on left and click 'Renew DHCP Lease'
- Windows - open Command Prompt or PowerShell and execute 'ipconfig /renew'
- Linux - open terminal and execute 'sudo dhclient -r' to release current lease and 'sudo dhclient' to obtain new lease. Note that solution might vary based on distribution
- Try running 'curl IP_OF_DEVICE_YOURE_CONNECTING_TO:4440/status' [for version older than 1.7.3-prerelease.9 - 'curl IP_...:4440'] between the devices. If it succeeds you should see 'Cursr is running!' [Or 'curl: (52) Empty reply from server' for versions older than 1.7.3-prerelease.9], if it takes too long and times out then it's likely that there is firewall blocking incoming connections on the other device. (Example: If you have macOS and Windows device, you would run 'curl WINDOWS_IP:4440' in macOS Terminal)
- macOS: Make sure that Cursr is allowed to find and communicate with devices on local network by enabling this setting in 'Privacy & Security' settings under 'Local network' permissions. Sometimes even if this permission is granted it may not work until you restart the app and macOS shows a popup again asking for permission to allow Cursr to use local network. If the popup does not show but you still see errors like 'EHOSTUNREACH' when trying to connect from macOS device, toggle the 'Use Alternative TCP Library' in General settings and restart. When you grant the permissions it should start working and for some time you may see duplicate instance of Cursr in 'Local Network' settings.
- Try changing 'Communications Port' in 'Virtual Switch' settings to any unused port
- Try restarting all instances of Cursr manually before reattempting to connect the instances
Keyboard not working in games or applications over KVM
Newly created license is invalid
Auto-disable not working
macOS - Why does Cursr need Accessibility access?
Windows - Cursr is not working if another application is open (ex: task manager)
Windows - Cursr does not open on new system?
