Probably but the account works fine on a mac or windows machine. I'm starting to think its a bug within curl. On Sep 7, 2012 11:37 PM, "Kurt Buff" <[email protected]> wrote:
> Is there an account that's local to either the Windows OS or to the > SQL instance that you could use instead? > > On Fri, Sep 7, 2012 at 7:53 PM, Stefano Pirrello <[email protected]> > wrote: > > No luck with that suggestion either. > > > > On Fri, Sep 7, 2012 at 6:57 PM, Kurt Buff <[email protected]> wrote: > >> Perhaps try instead "[email protected]:password" - in Active Directory > >> it's a valid login form, though I don't know for sure if it would work > >> in this case. > >> > >> Kurt > >> > >> On Fri, Sep 7, 2012 at 12:29 PM, Stefano Pirrello <[email protected]> > wrote: > >>> This doesn't seem to be working. See below from the packet capture. > >>> > >>> GET /Reports/Pages/Report.aspx?ItemPath=%2fSD%2fAvailable_Talent_UAT > HTTP/1.1 > >>> Authorization: NTLM XXXXXXXXXXXXX > >>> User-Agent: User-Agent: BLAHMAN > >>> Host: HOST.HOST.COM > >>> Accept: */* > >>> > >>> HTTP/1.1 401 Unauthorized > >>> Content-Length: 0 > >>> WWW-Authenticate: NTLM XXXXXXXXXXXXXXXXX > >>> Date: Fri, 07 Sep 2012 19:10:33 GMT > >>> > >>> GET /Reports/Pages/Report.aspx?ItemPath=%2fSD%2fAvailable_Talent_UAT > HTTP/1.1 > >>> Authorization: NTLM XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX > >>> User-Agent: User-Agent: BLAHMAN > >>> Host: HOST.HOST.COM > >>> Accept: */* > >>> > >>> HTTP/1.1 401 Unauthorized > >>> Content-Length: 0 > >>> WWW-Authenticate: NTLM > >>> Date: Fri, 07 Sep 2012 19:10:33 GMT > >>> > >>> > >>> > >>> On Fri, Sep 7, 2012 at 10:14 AM, Peter Kristolaitis < > [email protected]> wrote: > >>>> Have you tried changing your extraargs to > >>>> --NTLM -u "DOMAIN\\USERNAME:PASSWORD" > >>>> (note the extra \ ...). The backslash is likely being used as an > escape > >>>> character when it gets passed to the shell and so isn't actually used > at > >>>> all. > >>>> > >>>> - Pete > >>>> > >>>> On 12-09-07 09:54 AM, Stefano Pirrello wrote: > >>>>> Hi, > >>>>> > >>>>> Is there a way to send a CURL probe with NTLM authentication so I > >>>>> don't receive a 401 response? I'm trying to probe to a MS Reporting > >>>>> Services site but I'm only getting 401s and I've setup the NTLM info > >>>>> on the probe but it doesn't seem to be working. Using 301 redirects > >>>>> won't suffice my needs, I need to know the application is up and > >>>>> serving pages. > >>>>> > >>>>> ++ Curl > >>>>> probe = Curl > >>>>> extraargs = --NTLM -u "DOMAIN\USERNAME:PASSWORD" > >>>>> urlformat = http://%host% > >>>>> #forks = 10 > >>>>> #step = 60 > >>>>> pings = 20 > >>>>> menu = HTTP Latency > >>>>> title = HTTP Latency > >>>>> > >>>>> > >>>>> +++ CBRS-VIP > >>>>> host = SITE.DOMAIN.COM > >>>>> urlformat = http://%host%/Reports/Pages/Report.aspx? > >> > >> _______________________________________________ > >> smokeping-users mailing list > >> [email protected] > >> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > > _______________________________________________ > smokeping-users mailing list > [email protected] > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users >
_______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
