-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Same RPC issue as #19 despite latest build #23
Comments
Is it possible that the 2nd error might actually be related to Unicode characters? EDIT: Now it's just behaving pretty weird... wtf? I keep retrying it and it goes through the motions of: Completely successful rule list Might be something on the client's infrastructure end that is messing with it... |
Hey! That is pretty interesting. I've got a few ideas what might be causing this.
I'll try figure out a better way of doing the channel synchronisation, which should eliminate this issue. Unfortunately there are a ton of different Exchange configurations :( |
If you are able to build, I've pushed a few changes to the dev branch which could hopefully help with this. There is an extra flag when using the dev branch, this is probably very useful: #21 |
Hey! Was wondering if you got this working? Have you tried the latest builds? A funny thing I've seen is moving networks helps at times, might be a latency thing - which means my code is rubbish. |
Hey,
I'm currently having the exact same issue that is described in #19
Upon trying to bind it's trying to do:
"mapi: a transport layer error occurred. An error occurred setting up RPC. Time-out reading from RPC"
/ruler-linux64 --domain domain --username "username" --hash hash_here --email "username@domain.com" --verbose --url https://domain.com/autodiscover/autodiscover.xml --insecure --rpc --nocache display
I've tried plenty of different variations while debugging it, due to certain characters in the password despite escaping them it would keep giving me 401, so I had to use a hash instead. Which does successfully obtain Autodiscover.xml, and in turn it tries to connect to:
https://company.com/rpc/rpcproxy.dll?company.com:6001
Manually going to the RPCProxy URL asks you for credentials, upon success it shows a blank page, which according to a couple of forums is the correct response, although I don't know for sure.
Also another thing to note, upon removing the domain parameter I get this error:
tl;dr - Same problem as Issue #19 despite having the latest builds as of today.
The text was updated successfully, but these errors were encountered: