OCS Inventory - Cliente Windows
Bruno Peres
COM SERVER => Initializing cURL library for sendRequest
COM SERVER => Using cURL with server authentication
COM SERVER => Disabling cURL proxy support
COM SERVER => Disabling cURL SSL server validation support
COM SERVER => Sending HTTP Post request to URL <http://192.168.1.100/ocsinventory>
COM SERVER => HTTP Post response received <HTTP Status Code #417>
COM SERVER => Cleaning cURL library
ERROR *** AGENT => Failed to send Inventory <HTTP Status Code #417>
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:00:08.
Bruno Peres.
Twitter: @BrunoPeresREAL
Dante_Zaupa
============================
10.4.18 417 Expectation Failed
The expectation given in an Expect request-header field (see section
14.20) could not be met by this server, or, if the server is a proxy,
the server has unambiguous evidence that the request could not be met
by the next-hop server.
-----
14.20 Expect
The Expect request-header field is used to indicate that particular
server behaviors are required by the client.
Expect = "Expect" ":" 1#expectation
expectation = "100-continue" | expectation-extension
expectation-extension = token [ "=" ( token | quoted-string )
*expect-params ]
expect-params = ";" token [ "=" ( token | quoted-string ) ]
A server that does not understand or is unable to comply with any of
the expectation values in the Expect field of a request MUST respond
with appropriate error status. The server MUST respond with a 417
(Expectation Failed) status if any of the expectations cannot be met
or, if there are other problems with the request, some other 4xx
status.
This header field is defined with extensible syntax to allow for
future extensions. If a server receives a request containing an
Expect field that includes an expectation-extension that it does not
support, it MUST respond with a 417 (Expectation Failed) status.
Comparison of expectation values is case-insensitive for unquoted
tokens (including the 100-continue token), and is case-sensitive for
quoted-string expectation-extensions.
=======================================
Se eu entendi direito (e eu meio que duvido disso, mas a tentativa é
válida), existe um campo Expect no cabeçalho que não está setado como
deveria. Pode ser um problema na configuração dos clientes Windows.
2011/11/30 Bruno Peres <brunop...@gmail.com>:
> --
> Mensagem enviada para <http://groups.google.com/group/tchelinux>.
> Regras de Conduta para o grupo: <http://tchelinux.org/regras>.
--
Dante
"IMPUNIDADE, subst.: Riqueza."
-- Ambrose Bierce, "The Devil's Dictionary"
Usuário Linux #459228 -- Linux Mint 11 ("Katya")
William Souza
Pelo texto que tu colou ai a porta esta closed.
Abraço.
--
Mensagem enviada para <http://groups.google.com/group/tchelinux>.
Regras de Conduta para o grupo: <http://tchelinux.org/regras>.
--
William Souza de Lima
Diretor de Operações
Notesul - Consultoria em Tecnologia da Informação
(51) 3323.4218 (51) 9967.6075 (51) 9508.8969
Email: wil...@notesul.com.br - williamso...@gmail.com
MSN: ws...@terra.com.br
Jabber: williamso...@jabber.org
Googletalk: williamso...@gmail.com
Skype: williamhitec
blog: http://www.williamsouzadelima.blogspot.com/
www.notesul.com.br
Renato Rudnicki
On 30 nov, 16:57, William Souza <williamsouzadel...@gmail.com> wrote:
> Cara.. a porta 80 do teu servidor ta liberada?
> Pelo texto que tu colou ai a porta esta closed.
>
> Abraço.
>
> Em 30 de novembro de 2011 14:34, Bruno Peres <brunopere...@gmail.com>escreveu:
>
>
>
>
>
>
>
>
>
> > Olá lista,
>
> > Estou com um probleminha com o cliente Windows do software OCS. Com os
> > clientes Unix está tudo ok, funcionando perfeito, mas no Windows 7 ele
> > simplesmente não comunica com o servidor, até onde eu consegui compreender.
> > Segue trecho do erro no log do cliente.
>
> > * COM SERVER => Initializing cURL library for sendRequest
> >> ** COM SERVER => Using cURL with server authentication
> >> ** COM SERVER => Disabling cURL proxy support
> >> ** COM SERVER => Disabling cURL SSL server validation support
> >> ** COM SERVER => Sending HTTP Post request to URL <
> >>http://192.168.1.100/ocsinventory>
> >> ** COM SERVER => HTTP Post response received <HTTP Status Code #417>
> >> ** COM SERVER => Cleaning cURL library
> >> **ERROR *** AGENT => Failed to send Inventory <HTTP Status Code #417>
> >> **AGENT => Unloading communication provider
> >> **AGENT => Unloading plug-in(s)
> >> **AGENT => Execution duration: 00:00:08.*
>
> > Alguém aí já passou por essa dificuldade?
>
> > Att,
>
> > --
> > Bruno Peres.
>
> > Twitter: @BrunoPeresREAL
>
> > --
> > Mensagem enviada para <http://groups.google.com/group/tchelinux>.
> > Regras de Conduta para o grupo: <http://tchelinux.org/regras>.
>
> --
>
> *William Souza de Lima*
>
> Diretor de Operações
> Notesul - Consultoria em Tecnologia da Informação
> (51) 3323.4218 (51) 9967.6075 (51) 9508.8969
> Email: will...@notesul.com.br <will...@hitec.com.br> -
> williamsouzadel...@gmail.com <will...@hitec.com.br>
> MSN: w...@terra.com.br
> Jabber: williamsouzadel...@jabber.org
> Googletalk: williamsouzadel...@gmail.com
> Skype: williamhitec
> blog:http://www.williamsouzadelima.blogspot.com/www.notesul.com.br
Bruno Peres
Twitter: @BrunoPeresREAL