ocslogon.exe can't communicate with ocs server

Bug #497001 reported by zefox
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OCS Inventory: Windows Agent
Fix Released
Medium
eguillory

Bug Description

With v4.0.5.4 all is ok, but with v4.0.6.1, the ocslogon.exe (renamed with the name or the IP address of the ocs server) can't communicate with ocs server, which can be checked with a sniffer like wireshark (no packet).

Revision history for this message
Fabrice Flore-Thebault (themroc) wrote :

the ocs server doesn't receive anything and the clients complaints that it can't reach the server. with a tool like wget or a browser, ocspackage.exe is accessible.

Changed in ocsinventory-windows-agent:
importance: Undecided → Medium
Revision history for this message
eguillory (emmanuel-guillory) wrote :

Please, past the OcsLogon log file
There is absoluttelly no changes between 4054 and 4061 code exept version numbrer for OcsLogon...

Changed in ocsinventory-windows-agent:
importance: Medium → Undecided
Revision history for this message
zefox (zefox) wrote :

Hi Emmanuel,

I'm away but I remember :
- the debug switch could't create the ocslogon.log. Don't know why : can you explain me how I can generate the ocslogon log file ?
- only a version change ? but the sizes are significally different : 66 vs 77 KB

Cheers.

Revision history for this message
Fabrice Flore-Thebault (themroc) wrote :

Ocslogon.log :

Cmd Line: "\\wonderfulcompany.com\SysVol\wonderfulcompany.com\Policies\{XXXXXX}\Machine\Scripts\Startup\ocslogon.exe" /INSTALL /DEPLOY:4061 /SERVER:ocsinventory-ng.wonderfulcompany.com /DEBUG /NP
OCS server port number: 80
Deploy folder : C:\ocs-ng
OCSserver is set to: ocsinventory-ng
Internal Ocslogon version: 4.0.6.1
Ocs Inventory NG (4061) was not previously installed.
Start deploying OCS
http://ocsinventory-ng:80/ocsinventory/deploy/ocspackage.exe : U
End Deploying
Testing ocsagent.exe version:0000
ERROR downloading agent on: http://ocsinventory-ng:80/ocsinventory/deploy/ocspackage.exe
Please check this URL.

Revision history for this message
eguillory (emmanuel-guillory) wrote :

...
And in the web browser:
http://ocsinventory-ng:80/ocsinventory/deploy/ocspackage.exe
Works or not?...

Revision history for this message
Fabrice Flore-Thebault (themroc) wrote :

no, and that's the problem : everything is configured so that 'ocsinventory-ng.wonderfulcompany.com' should be the server used by ocslogon.exe, but it is not, it's still looking for 'ocsinventory-ng' ;
using the IP of the server to rename ocslogon.exe didn't work either

Revision history for this message
eguillory (emmanuel-guillory) wrote :

you didn't read correctly the documentation!
You have to rename ocslogon.exe to wonderfulcompany.com.exe...

You just have what you ask...

Revision history for this message
eguillory (emmanuel-guillory) wrote :

Please past the correct log file with "wonderfulcompany.com.exe"

Changed in ocsinventory-windows-agent:
status: New → Incomplete
Revision history for this message
zefox (zefox) wrote :

Emmanuel,

I know that and I have already renamed with IP or FQDN name but nothing with 4.0.6.1.
An idea : in my company, it's forbidden writing on the root of C: volume. Maybe that's why I can't have the ocslogon log file. Is it possible to specify another path ? Is there any change in the logic of the exe ? If it can't write, then stop ?
The true url works manually in a web browser.

Revision history for this message
eguillory (emmanuel-guillory) wrote :

Ok
I have the same bug now due to a new plugin inet plugin in the last NSIS version.
I'll try to patch asap.

Regards

Changed in ocsinventory-windows-agent:
status: Incomplete → Confirmed
importance: Undecided → Medium
assignee: nobody → eguillory (emmanuel-guillory)
Revision history for this message
Florent-36 (florent362) wrote :

Cmd Line: "\\test.com\SysVol\test.com\Policies\{7F67CEDA-CFDB-4F66-9A4E-ABF3DF3FF936}\Machine\Scripts\Logon\SERVEUR_OCS.exe" /S /NP /INSTALL /DEBUG /DEPLOY:4061 /SERVER:SERVEUR_OCS /NoOcs_ContactLnk
OCS server port number: 80
Deploy folder : C:\ocs-ng
OCSserver is set to: SERVEUR_OCS
Internal Ocslogon version: 4.0.6.1
Service is installed on: C:\Program Files\OCS Inventory Agent
Testing: C:\Program Files\OCS Inventory Agent\BIOSINFO.EXE
Testing: C:\Program Files\OCS Inventory Agent\OCSInventory.exe
Testing: C:\Program Files\OCS Inventory Agent\OcsWmi.dll
Testing: C:\Program Files\OCS Inventory Agent\SysInfo.dll
Testing: C:\Program Files\OCS Inventory Agent\MFC42.DLL
Testing MFC42.DLL version (6241310)
Testing OCSInventory.exe version (4054)
Ocs Inventory NG (4061) was not previously installed.
Start deploying OCS
http://SERVEUR_OCS:80/ocsinventory/deploy/ocspackage.exe : U
End Deploying
Testing ocsagent.exe version:0000
ERROR downloading agent on: http://SERVEUR_OCS:80/ocsinventory/deploy/ocspackage.exe
Please check this URL.

PS: works perfectly with ocslogon 4054 ,
PS2: http://SERVEUR_OCS:80/ocsinventory/deploy/ocspackage.exe works in the web browser

Revision history for this message
Gonéri Le Bouder (goneri) wrote :

Hi,

I rebuilt everything and got this log:

Cmd Line: nana.rulezlan.org /DEBUG /INSTALL /SERVER:nana.rulezlan.org /DEPLOY:4061
OCS server port number: 80
Deploy folder : C:\ocs-ng
OCSserver is set to: nana.rulezlan.org
Internal Ocslogon version: 4.0.6.1
Service is installed on: C:\Program Files\OCS Inventory Agent
Testing: C:\Program Files\OCS Inventory Agent\BIOSINFO.EXE
Testing: C:\Program Files\OCS Inventory Agent\OCSInventory.exe
Testing: C:\Program Files\OCS Inventory Agent\OcsWmi.dll
Testing: C:\Program Files\OCS Inventory Agent\SysInfo.dll
Testing: C:\Program Files\OCS Inventory Agent\MFC42.DLL
Testing MFC42.DLL version (6241310)
Testing OCSInventory.exe version (4054)
Ocs Inventory NG (4061) was not previously installed.
Start deploying OCS
http://nana.rulezlan.org:80/ocsinventory/deploy/ocspackage.exe : OK
End Deploying
Testing ocsagent.exe version:4061
Launching : C:\ocs-ng\ocsagent.exe /DEBUG /INSTALL /SERVER:nana.rulezlan.org /DEPLOY:4061
Testing Service...
Service start parameter (should be 2): 2
Service is installed on NT like OS.
Exiting OcsLogon.

I wonder if the there is a corrupted file in the public archive.

Revision history for this message
Gonéri Le Bouder (goneri) wrote :

It also works if I use the rebuilt ocslogon with an ocspackager.exe generated with the official archive.

Revision history for this message
Denis Konstantinov (linvinus) wrote : Re: [Bug 497001] Re: ocslogon.exe can't communicate with ocs server

Hello Gonéri!
Sorry i don't understand what you are talking about?

2010/1/18 Gonéri Le Bouder <email address hidden>

> It also works if I use the rebuilt ocslogon with an ocspackager.exe
> generated with the official archive.
>
> --
> ocslogon.exe can't communicate with ocs server
> https://bugs.launchpad.net/bugs/497001
> You received this bug notification because you are a member of OCS
> Inventory Dev Team, which is subscribed to OCS Inventory.
>

Revision history for this message
Gonéri Le Bouder (goneri) wrote :

2010/1/19 Denis Konstantinov <email address hidden>:
> Hello Gonéri!
Hi Denis,

> Sorry i don't understand what you are talking about?
I rebuilt all the OCS binaries and I can't reproduce the bug. So I
tried to create an ocspackager.exe with the binaries from the 1.3
distribution from the website to check if the bug was related.

Do you also have the bug with OCS 1.3?

Regards

--
     Gonéri Le Bouder

Revision history for this message
Gonéri Le Bouder (goneri) wrote :

The ocslogon we provide has been built with inetc UTF8 (26kb) whereas UTF8 is disabled. If I use the classic inetc (20kb), everything is ok.

Revision history for this message
Gonéri Le Bouder (goneri) wrote :

I published the new OCSNG_WINDOWS_AGENT_4061.1.zip archive to fix the issue.

Revision history for this message
Gonéri Le Bouder (goneri) wrote :

Fixed in OCSNG_WINDOWS_AGENT_4061.1.zip

Changed in ocsinventory-windows-agent:
status: Confirmed → Fix Released
Revision history for this message
TiNTiN (esdebian) wrote :

With OCSNG_WINDOWS_AGENT_4061.1.zip

Cmd Line: 192.168.8.13 /S /NP /INSTALL /DEBUG /SERVER:192.168.8.13 /NoOcs_ContactLnk
OCS server port number: 80
Deploy folder : C:\ocs-ng
OCSserver is set to: 192.168.8.13
Internal Ocslogon version: 4.0.6.1
Ocs Inventory NG (0) was not previously installed.
Start deploying OCS
http://192.168.8.13:80/ocsinventory/deploy/ocspackage.exe : U
End Deploying
Testing ocsagent.exe version:0000
ERROR downloading agent on: http://192.168.8.13:80/ocsinventory/deploy/ocspackage.exe
Please check this URL.

And in the web browser:
http://192.168.8.13:80/ocsinventory/deploy/ocspackage.exe
Works...

Revision history for this message
Yann Caron (ycaron) wrote :

Same problem here with ocslogon.exe in OCSNG_WINDOWS_AGENT_4061.1.zip
Cmd Line: OcsLogon.exe /install /url:http://ocs-server/ocsinventory/deploy/ /DEBUG /np
OCS server port number: 80
URL used : http://ocs-server/ocsinventory/deploy/
Deploy folder : C:\ocs-ng
OCSserver is set to: ocsinventory-ng
Internal Ocslogon version: 4.0.6.1
Ocs Inventory NG (0) was not previously installed.
Start deploying OCS
http://ocs-server/ocsinventory/deploy/ocspackage.exe : U
End Deploying
Testing ocsagent.exe version:0000
ERROR downloading agent on: http://ocs-server/ocsinventory/deploy/ocspackage.exe
Please check this URL.

http://ocs-server/ocsinventory/deploy/ocspackage.exe works fine in a browser.

I tried with the servname in the filename, with the FQDN and and the IP : same error.
I checked with a packet tracer and a tcpview while runnin ocslogon.exe : the process does not send a single packet to the ocs server or to anything else.

Revision history for this message
eguillory (emmanuel-guillory) wrote :

+++++++++ This bug is fixed +++++++++
Please download the 4061.1 version here
http://code.launchpad.net/ocsinventory-windows-agent/trunk/win32-agent-release-4061/+download/OCSNG_WINDOWS_AGENT_4061.1.zip
================================

Revision history for this message
eguillory (emmanuel-guillory) wrote :

Use Ocslogon.exe at the top of OCSNG_WINDOWS_AGENT_4061.1.zip
Th Osslogon packed in Ocsagent.exe is not patched.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.