No, it's not 100% fixed, but the major part of the problem (99%), which was at the server was fixed. The remaining part of the problem (1%) that's within RPA isn't fixed but shouldn't cause an issue for the greater majority of users.
A few possible reasons for not being able to connect with RPA these days, in order of probability, are
- The firewall or antivirus on the PC is blocking RPA's access to the internet
- The RPA server was down at the time
- Some other program or service on the PC is using port 4608 locally
- You have a weird wireless network problem that is causing NAT table corruption
- You don't have IPv4 connectivity to the internet
It appears from your other threads that you have successfully connected before so has anything changed with the PC since then, new software?, windows update? anything?
As for my UDP Test tool in the thread you referenced, I removed it as the issue is "fixed" for the greater majority of users and there are better tools available now for diagnosing problems than that tool I wrote years ago.
- Tim