Shaun_Dark_Lord Posted July 21, 2017 Posted July 21, 2017 Hi All Whilst I await a response from my SIMS support provider, I thought I'd ask here. All of my teachers have left for the summer, taking their laptops with them. All of the laptops are configured to remotely connect from home via Microsoft Direct Access. This is working fine and I can happily manage the clients whilst they're off site. We haven't had a SIMS upgrade since rolling out DA, but as SIMS was working and SOLUS3 was reporting the clients as online when they were off site, I was not expecting any problems............... What was I thinking? It appears that the SOLUS 3 agent reports it's IPv4 address to the server rather that it's DNS name. As a result, the SOLUS server tries to push upgrades to the IPv4 address rather than simply use DNS. I have no clue why it's doing this. The agents are reporting as online, and I can even uninstall/reinstall the agent to a remote PC through SOLUS. Has anyone else experienced this, and was there a workaround? Regards Shaun.
LytchettNM Posted July 21, 2017 Posted July 21, 2017 (edited) We have the same issue and I have asked for support and have had no reply yet! But we only have a few member of staff with SIMS installed on there laptops so these teachers are aware and know that they would need to bring the laptop in and while on local network it will update. I have not find a workaround but have been thinking about setting up a remote app's server and allow member of staff that have / need SIMS at home to use the remote app. The app should run quicker to the end user as it's running locally on the server and we can update it automatically. Edited July 21, 2017 by Techforyou
matt40k Posted July 25, 2017 Posted July 25, 2017 Wonder if they disabled IPv6 as the records were mostly carp (as no-one sets it up internally in schools). Or if its the DA NAT64 its struggling with.
Michael Posted July 25, 2017 Posted July 25, 2017 I've observed behaviour whereby the workstation is only reporting IPv6 and not IPv4 and Solus simply cannot find it. The only solution was to release the IP and then renew, which cleared the issue.
RobFuller Posted July 26, 2018 Posted July 26, 2018 Did anyone get a confirmation from Capita about IPv6 support for Solus3? (Exactly the same issue at OP)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now