The most common causes for the forcefully rejected error are:
1. The IP on the Automation System is not the IP of the CSRDS computer or the IP in CSRDS is not the IP of the Automation System computer.
2. If they are on different networks and one network cannot be accessed from the other. Not likely but you can verify by pinging the Automation System computer from the CSRDS computer. I suspect it will ping just fine.
3. If you can Ping the automation computer the issue is with the port which may be very restricted. Here are some things to check:
a. The port is the same on both computers
b. The port is not locked by another application. If you were running another
application it may still be running as a service and has the port locked even if you
exited the application.
c. The port may be blocked and needs to be opened (PC, Router, Switch)
d. It could also be blocked by a firewall, rule (open for UDP by not TCP/IP), may
even require a MAC address to allow access. This may be on the CSRDS
computer, the automation computer or on the network switch/router.
e. CSRDS itself may be blocked. The program performs a lot of processes
associated with viruses (IP, FTP, HTTP, LAN connections) and some
antivirus/firewall applications will allow the program to run but will block some
access. May need to exclude CSRDS from any firewalls or anti-virus applications.
4. It’s not common but some automation systems will only run as a “client”. A TCP/IP connection needs one computer to be the “server” and the others to be the “client” Normally CSRDS is the client and will request the connection to the automation system, but some like NextGen want to be the Client so CSRDS needs to be the client. If that’s the case, select the “Input Source is The Client” in the Other Tab