Closed tksdia closed 1 year ago
any update please??
@SamDecrock Any Update on this?
Me too facing this issue at regular intervals - but there is no clear root cause at our end. Any update or if any one get through this please help..
I too have encountered this issue, based on my research below are the probable causes for the issue, nothing specific in library :
target not responding to the request due to some kind of outage like incoming Network connection bottleneck.
the source Network config isn't allowing outgoing connections to target in question
target's network might not be configured to receive any incoming connections from the source in question.
furthermore there might not be a windows NTLM auth setup in place at target at all
Due to any of the above, as a result - stage 2 in NTLM protocol will not be receiving a key from target to use for stage 3 communication with target.
if your working with NAV/Business central, In NAV or Business Central Administration, there is a field in the General tab called Use NTLM Authentication ensure that it is checked (set to true). it helped me resolve this issue
As @rp21buzz told, it's probably something server related. If my module doesn't see the correct header, there's not much I can do about it. Closing ticket.
Most times it works but some times failed with below error.
Couldn't find NTLM in the message type2 comming from the server\n at Object.parseType2Message (....\node_modules\httpntlm\ntlm.js:116:12)\n at sendType3Message (C:\node_soa\soa.referencedata.service\node_modules\httpntlm\httpntlm.js:73:23)\n at Immediate. (....\node_modules\httpntlm\httpntlm.js:101:4)\n at runCallback (timers.js:666:20)\n at tryOnImmediate (timers.js:639:5)\n at processImmediate [as _immediateCallback] (timers.js:611:5)
my code is making an http api call which is protected by windows auth.
httpntlm.get( { url, username, password, workstation, domain:"XXX" } Thanks a lot.