Just installed the FIM portal, I am able to access the portal and use it locally without issue, if I access from a remote server I can view the front page fine but if I click users then click search I get:

Unable to process your request.  
   Please contact your help desk or system administrator. 


If I access remotely, click administration, schema, bindings, all that loads fine. When I click to view page two of bindings I get the same error. Seems certain actions are causing an error but I have no idea where I begin to debug such a thing.

Portal currently only has my user account and the built-in sync, I've not set-up a FIM portal MA yet. Portal, service and sspr portals are on server 1, the sync server and sql are on server 2. 

Any suggestions would be great. Thanks.

Are you logging in as the same user in both cases? Does your user have the access, or is simply a normal user?

Same in both cases, user I am using is the one I installed with, the domain, objectSid and accountName are all present.

Thanks

When you RDP, are you using the browser on RDP server or your local machine where RDP from?  Check the browser settings. Allow Popups, ActiveX

When I RDP to the server and use the browser on the server where FIM portal is installed, I have no problems.

When I use a browser on another machine , such as my desktop, I can view some pages fine, I've even managed to view a user successfully now, but the vast majority of requests return the error described. 

I don't think my ActiveX or pop-up blocker settings have anything to do with this error unfortunately :( 

If all things are equal, the only difference is your Browser.

Hmm, can't spot any immediate differences - would you have suggestions beyond ActiveX and pop-up blocker?

Thanks

Version.  Some known issues with IE11. Delete CACHE and make sure to delete all temporary internet files. The files are here: C:\Users\UserName\AppData\Local\Microsoft\Windows\Temporary Internet Files.

Of course this is not a solution, but a worka

Couldn't pinpoint exactly what setting was causing it but it's almost certainly a browser issue. Thank you

Glad it worked!