Unable to create local file on Revit Server 2013

Starting yesterday one of our Revit Server Accelerators started malfunctioning. First we noticed that links were being unloaded. Then we were unable to sycronize open files. Then when opening a new file the create new local was greyed out but detach from central was ok. We were able to open the files if we detach from central but if we saved the files back to the Revit Server the files would remain constantly in use as the files that were open and could not be synronzied. While this was going on at one of our sites the other sites could work on the same files without any problems.

Both the internet speed (30 mbit) and the latentcy (27 m/s) were not the issue. We have restarted the effected accelerator, cleared the cache from the acclerator and cleared the cashe from the workstations. All of this did not work. We accesed the host server directly. This worked fine but the performance was very slow. We built a new acclerator. This worked for about an hour but then we had the same problem.

Has anyone experienced this problem?

This is a tough one. Here is how I would troubleshoot this:

1) verify the RSN.ini file is the same, as every other device in your Revit Server Network.

2) Is this box running other services or operations?
a. Revit Server operates on port 808. Verfity there are no other processes operating on this port.

3) what do you get, when you go to RSA from this accelerator: e.g. http://YourAccelerator/revitserveradmin2013/?
a. Based on your RSN.ini on the accelerator, it should communicate directly to RSA on the server(s) via port 80.
b. I always check RSA first, whenever there are Revit Server issues. It's the first indication of hardware/network issues.

4) verify the prerequisites. This is tedious, but could be the deal breaker.
a. http://wikihelp.autodesk.com/Revit/e..._Prerequisites

5) Do you have a WAN accelerator between the accelerator and host? Verify the configuration is consistent with the rest of the network. I am not a sysadmin, so I can't advise anything specific.

I would be curious to know the resolution. Thanks.

>>We built a new acclerator. This worked for about an hour but then we had the same problem.<<

Did you rebuild using another hardware?
If not, maybe it's your present hardware the culprit.
HTH

We found the issue to be a conflict between two fire walls which caused the packet size to be too small for our revit models. We have a field office where the contractor's IT department changes some of their hardware without consulting us. In house we use all the same fire walls in all of our office but in this case we do not have control over the fire wall that the contractor uses. So fare it has been working without any more problems.