hhn,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://support.novell.com/forums/

hhn -

Just looking at a small snippet of the log doesn't say much. The winsock error is usually included in the log and this would give me a better idea.
Possible causes:
* firewall on client blocking incoming packets (most common problem)
* the client is online for a very short period and not allowing sufficient time for an unload to occur and transmittal of files to the client

FYI...when initiating a scan from the Manager, the request is actually placed on a high priority queue and gets processed very quickly. I think your problem might be more related to the duration of connectivity than that of a network connectivity problem. Can you indicate if clients are online most of the time; or do they connect briefly?

Dennis


>>> hhn<hhn@no-mx.forums.novell.com> 3/23/2010 11:16 AM >>>


Hi all,

A customer of mine, is facing some strange issues with receiving
scanning results on server.

They are running a ZAM 7.5 IR20 (standalone) installation with
approcimately 250 workstations.

The system is setup to scan once every week, with 4days of trying if
not online at scanning day.

For some reason, only about 25 workstations have reported their
scanning results in the last 23 days. They are scattered around on
different networks, and it seems that when manually initiating a scan
from Amanager, they report in just fine.

But - in collection server error log, we find a fairly large amount of
these errors:
<EVENT AT="22-03-2010 07:41:49" SEVERITY="Warning">
Application Object Warning at 22-03-2010 07:41:49 on SRV by SRV
Network Communication Error
[2.4.501] A network error was encountered while communicating with a
remote application.
ID: {9207F493-2FC2-4AB3-8EC0-40CCBA109C41}
Name: 0.0.0.0
Port: 0
</EVENT>

<EVENT AT="22-03-2010 07:41:49" SEVERITY="Warning">
Application Object Warning at 22-03-2010 07:41:49 on SRV by SRV
Network Communication Error
[2.4.501] A network error was encountered while communicating with a
remote application.
ID: {9207F493-2FC2-4AB3-8EC0-40CCBA109C41}
Name: 0.0.0.0
Port: 0
</EVENT>

Can anybody sheed some light on the possible reasons for these? All
network communication works fine on the network - at least nobody has
registered any issues or complaining about dropouts etc.

Cheers,
hhn


--
hhn
------------------------------------------------------------------------
hhn's Profile: http://forums.novell.com/member.php?userid=16357
View this thread: http://forums.novell.com/showthread.php?t=405527