changing the Groupshare 2017 ip adress

We tried to change the Groupeshare 2017 server IP address and when doing the change and restarting the site was not accessible.Is there a configuration that must be made in GroupeShare 2017 console or in RabbitMQ or somewhere else? Is there an IP adress specific to Groupshare? For exemple, we changed the local IP, all services were working on the groupshare console, but we were not able to access the Groupshare with the server address. 

  • Hi Valérie,

    Changing the IP address of any server a task that should be very carefully planned. Are you using DNS? If so did you change the entry for the server's IP there after you changed the IP address? Or are you maybe using a hosts file? If so then each client's hosts file would have to be amended.

    This is assuming that you are using hostnames to connect from the clients to the server (which most people do). The clients need to have some way of knowing that the IP has changed and that the hostname they now connect to needs to resolve to the new IP address.

    Regarding the configuration of GroupShare itself, assuming the external server address is correct in the GroupShare Console under Settings -> Project Server Settings and Execution Server Settings then everything should be okay. You should check the IIS bindings too though.

    Hope this helps.

    Kind regards,
    Nick

  • Hi Nick, thank you for the answer. 

    I had a look on the server in the Group Share Console, and could not find any setting that was related to IP addressing for the server, nor could I find anything in the IIS bindings that would be tying the server to a specific IP.

    I also had a look in the hosts file on the server, and there are no entries there that would be tying the server to the local IP. Is there a RabbitMQ implication in all this?

  • Hi Valérie,

    Unfortunately it's impossible to say exactly what is wrong as there are far too many factors involved. I highly doubt it has anything to do with RabbitMQ though.

    If you can't ping / contact the server from the client PCs at all then you most likely need to update your local DNS server with the new IP address. I suggest that you speak to your local IT team who will be able to investigate this from a network perspective.

    If you would like SDL to investigate this issue for you then please contact your SDL sales representative who will be happy to arrange for an SDL Professional Services consultation.

    Kind regards,
    Nick