spc-rocket Posted April 29, 2015 Posted April 29, 2015 Hello all, we have office 365 solution and are trying to use the onedrive for business location and sharepoint sites when using office application. We're got an issue at the moment where the signing in to office (using word say for example) is failing and giving the following error: "we are unable to connect right now. please check your network and try again". The username and password is correct. The single sign on to office 365 through browser is fine and we can access the onedrive and sharepoint sites document library in the browser. Just wondering if anyone has had this problem. office 2013 sp1 + all updates on windows 7 64bit station (office 2013 is a 32bit version). Ash.
CharlieH Posted April 30, 2015 Posted April 30, 2015 I've had issues along these lines with Sharepoint in the past when I have changed passwords. I have resolved this on more than one occasion by deleting everything from Credential Manager (as advised by Microsoft). Good luck!
spc-rocket Posted April 30, 2015 Author Posted April 30, 2015 Hiya, I tried this but it doesn't work, in fact it doesn't work for anyone in the school - we're trialing this at the moment so not a major impact but i would like to get a resolution to this pretty soon. Ash.
harriuk Posted April 30, 2015 Posted April 30, 2015 How are you publishing your adfs server? If it's through TMG you need two rules, one for the browser and one for the client "Rich" experience.
spc-rocket Posted May 1, 2015 Author Posted May 1, 2015 Hiya, Yes the adfs server(s) are published through TMG 2010, at the moment, I have 1 reverse publishing rule i.e. 443 from external to the ADFS servers and for ADFS server to go out we have anonymous access to internet for Microsoft domains. Could you share your rules if possible. Many thanks, Ash.
harriuk Posted May 1, 2015 Posted May 1, 2015 OK. You just need to copy your original rule and change the authentication delegation to "No authentication but client may authenticate directly" and the paths need to be (without quotation marks) "/adfs/trust/mex/*" and "/adfs/trust/2005/*" . This rule needs to go above your original rule. Also ensure there is no link translation on any of your adfs rules. Let me know how you get on!
spc-rocket Posted May 1, 2015 Author Posted May 1, 2015 Hiya, I've created a server publishing rule to allow 443 traffic to ADFS server from external with an external IP. I think you may have configure web publishing rule for this. This is what was recommended to me. action: allow traffic: HTTPS server From: external To: networks: External - External IP address of ADFS server Thanks, Ash. Ash.
harriuk Posted May 1, 2015 Posted May 1, 2015 Yes that is correct so copy that rule, place it above your original rule and make the changes detailed above. By having the new rule above it allows the office clients to connect to the adfs directly as it needs to using the paths it needs as stated above. All other Web traffic to your adfs server will be unaffected as they will still use the original rule. Does that make sense?
spc-rocket Posted May 1, 2015 Author Posted May 1, 2015 Hiya, Thanks for your help thus far, I really do appreciate it. Since the rule is a server publishing rule and not a web publishing rule I don't see the place to put "paths". I think this is only available if you use a web publishing rule to publish the web server /adfs server Ash.
harriuk Posted May 1, 2015 Posted May 1, 2015 Ahhh yes Adfs should be published as a Web server AFAIK.
spc-rocket Posted May 7, 2015 Author Posted May 7, 2015 Hi, Solved this, it was something to do with our ADFS servers. All working fine. Ash,
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