I figured this out, sort of. Now I changed sched task URL to use the public
IP address of the server, I got status 200.
So not localhost, not 127.0.0.1 but the public IP address. I guess this is
due to the server got multiple NICs so that localhost cannot be resolved
somehow?
On Wed, Nov 18, 2015
PM
To: cfaussie@googlegroups.com
Subject: Re: Re[2]: [cfaussie] CF11 Scheduled Task Not Running - 401
Unauthorized
I figured this out, sort of. Now I changed sched task URL to use the public IP
address of the server, I got status 200.
So not localhost, not 127.0.0.1 but the public IP
have windows auth on
> in one site, and not the other. And you may have been going to different
> ones all along.
>
> /charlie
>
>
>
> *From:* cfaussie@googlegroups.com [mailto:cfaussie@googlegroups.com] *On
> Behalf Of *Xiaofeng Liu
> *Sent:* Tuesday, November 17, 2015
@googlegroups.com
Subject: Re: Re[2]: [cfaussie] CF11 Scheduled Task Not Running - 401
Unauthorized
Hi Charlie,
I originally was using a URL like "http://localhost:1981/cron/schedTask.cfm"; to
run the scheduled task. So that was the URL I specified in CF Admin. That threw
401 to me.
gt;
> *From:* cfau...@googlegroups.com [mailto:
> cfau...@googlegroups.com ] *On Behalf Of *Xiaofeng Liu
> *Sent:* Wednesday, November 18, 2015 5:07 PM
> *To:* cfau...@googlegroups.com
> *Subject:* Re: Re[2]: [cfaussie] CF11 Scheduled Task Not Running - 401
> Unauthorized
>
>
&
Sent: Friday, December 8, 2017 09:11 AM
To: cfaussie
Subject: Re: Re[2]: [cfaussie] CF11 Scheduled Task Not Running - 401
Unauthorized
Did anyone ever get to the bottom of this?
Having exactly the same problem here.
Local IP address url calls to another server (Windows 2012 R2) from the
f
> *Sent:* Friday, December 8, 2017 09:11 AM
> *To:* cfaussie
>
> *Subject:* Re: Re[2]: [cfaussie] CF11 Scheduled Task Not Running - 401
> Unauthorized
>
>
>
> Did anyone ever get to the bottom of this?
>
>
>
> Having exactly the same problem here.
>
>
>> On Thursday, November 19, 2015 at 4:53:35 AM UTC+1, charlie arehart wrote:
>>
>> Sure, that is curious. If you may ever get to the bottom of things, it
>> would be interesting to hear. Thanks for the update.
>>
>> /charlie
>>
>> *From:* cfau...@g
