I'm new to RipBot264, and doing my best to set it up and troubleshoot it on my own, but after several days of still not getting anywhere I am now at the point where I feel asking around for help is warranted.
When I try to do distributed encoding, the encoding server will not connect. The client shows the server as being in a "connecting" state, then switches to disconnected. This happens over and over again about twice per second. Over on the server side, it shows the connection is established, and then that it has closed gracefully. Once again over and over in a loop. The TCP Communication window shows lots of:
553|CLIENT -> SERVER| CONNECT=10.7.1.170:1001
554|CLIENT <- SERVER| OK
I have read through many other posts, and have checked an awful lot of things including the following:
- Disabled other network adapters and made sure IP addresses being used are correct
- Disabled windows firewall and antivirus on both machines
- Visual C++ Redistributable is installed on both machines
- I can telnet to port 1000 on the server, and 1001 on the client without issue (receiving "200 Welcome")
- I can access the RipBot share from the remote server and write to it
- I disabled password protected sharing in Windows
For additional background:
- I'm running RipBot264 v1.24.0
- Encoding Server is v18.104.22.168
- Both computers are running Windows 10 and have plenty of resources
- Both computers are plugged into the same switch, there is no network firewall between them
At this point I don't know what else to troubleshoot and welcome any guidance. Thank you very much in advance!
+ Reply to Thread
Results 1 to 7 of 7
I appreciate the tip, but I'm not sure any of that applies to me. I never even get to a point where it starts encoding because the remote server seemingly never connects.
Can the PC's "see" each other in Windows Explorer/ network?
Can you ping each other's I.P. address?
Just thought I'd post back here that the new version, 1.25.0, works with no other changes in my environment. Not sure what was going on with 1.24.0, but something in the newer version took care of it.