I administer contibute for my organization. We only have about a dozen users - most of them are working fine. Everything is done on our local LAN - there is no FTP involved. I have one user who was connected and things were working fine until her connection suddenly stopped working. I tried sending a connection key (which had always worked before) and she got a message saying Contribute was unable to connect to the server.
I tried uninstalling and re-installing contribute, and resending a connection key. I got the same response of unable to connect to the server. In the meantime, I re-installed contribute on a different user's machine and sent a connection key - no problem with her.
The problem user's desktop machine had become notoriously slow and unstable, so the operating system was reloaded. I again loaded the client Contribute CS3 on the reformatted machine and sent a connection key. Again I got the same response of unable to connect to the server.
I deleted the user's group on contribute and created a new one for her and sent a new connection key. Again I got the same response of unable to connect to the server. One last time I used remove programs to remove Contribute so I could try another re-install (since a lot of software (including outlook) had been installed between the time I installed Contribute on the rebuilt machine and when I sent the connection key.
Even though the Contribute program removal went to a normal completion and I restarted the machine, when I tried to re-install Contribute for the umpteenth time, it didn't ask me for a serial number. There appears to be some memory of contribute remaining in the machine. Can anyone give me a suggestion on where to look for this problem or what to try next (short of dynamiting this machine)?
Thanks for any suggestions you can give.