RE: Languard 7 and terminal window madness

	Forums Register Login My Profile Inbox Address Book My Subscription My Forums Member List Search FAQ Ticket List Log Out

RE: Languard 7 and terminal window madness

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Networking & Security] >> GFI LANguard >> RE: Languard 7 and terminal window madness

Page: << < prev 1 [2]

Message

<< Older Topic Newer Topic >>

RE: Languard 7 and terminal window madness - 22.Feb.2006 9:15:04 AM

EWAB

Posts: 2
Joined: 27.Jan.2006
Status: offline

Tried the "dcomcnfg" solution and it worked.
Have to say that I'm using the Domain admin account to log on
to terminal and to scan.

(in reply to Nicks)

Post #: 16

RE: Languard 7 and terminal window madness - 23.Feb.2006 4:58:42 AM

Patrizia

Posts: 8474
Joined: 18.Aug.2003
From: Malta
Status: offline

EWAB,

Thanks for the update!

_____________________________

Patrizia Caruana
GFI Software - www.gfi.com
Messaging, Content Security & Network Security Software

(in reply to EWAB)

Post #: 17

RE: Languard 7 and terminal window madness - 21.Jun.2007 3:56:07 PM

fatmosh

Posts: 4
Joined: 20.Mar.2007
Status: offline

I had a similar issue and the processes detailed above fixed the problem.

BUT...for some reason, at some point in the the DCOM config gets set back to the LNSS_MONITOR_USR instead of the "launching" user. Whenever this happens, my scheduled scans stop sending until I reset both LNSSCommunicator and RepServer components back to using the "launching" user.

Does anyone have any idea what could cause this? It's almost as if N.S.S. is reseting the DCOM component back to it's original configuration at some point in time (when an error occurs, perhaps?)...

Any ideas? I don't want to have to keep reseting this over and over again whenever it stops working.

Thanks in advance!

(in reply to Patrizia)