Languard 7 and terminal window madness (Full Version)

All Forums >> [Networking & Security] >> GFI LANguard



Message

Maxtor -> Languard 7 and terminal window madness (27.Dec.2005 5:41:42 PM)

Hello all,

After I recently updated to languard v7 I noticed that I couldn't perform such functions such as running the application scanning and the remote registry scans, (error was "Could not connect to remote registry").  After playing around with it for hours, I decided to bypass the ms terminal server connection and go directly to the monitor of my 2000 server and try it there.  To my disbelief, everything worked fine from the monitor.  The problem only seemed to happen when I was using the windows terminal services remote connection.  So I decided to reinstall ms terminal services, check the permissions and nothing seemed to work...  Everything worked fine without the terminal services, but now I think that there is something wrong with languard...

I ran a missing patches scan using the terminal services and it worked.  So I decided to add the application scan to the missing patches scan and now the application scan works.  For some reason the default scan does not work, (at least with application scans and processes) using ms terminal servies.  It's almost like there is some setting in there that is not working properly, but I can't put my hand on it. 

By the way this is a fresh install of Languard.  I completely uninstalled the old version and blew out the old directories.  Anyone else using terminal services out there or a remote connection to their languard server?

Max



Maxtor -> RE: Languard 7 and terminal window madness (28.Dec.2005 1:55:59 PM)

Now I'm thinking it may have to do with 2000 server since the terminal services are working on another computer that I have Languard installed on. 

Max



Nicks -> RE: Languard 7 and terminal window madness (2.Jan.2006 4:17:37 AM)

Hi Max,

That is strange. LANguard NSS should not be effected when it is run from a Terminal service connection. You can try to connect to the remote registry of the scanned machine using regedit - this will confirm if the problem is from LNSS or from the Terminal service connection.



EWAB -> RE: Languard 7 and terminal window madness (27.Jan.2006 7:24:32 AM)

I can confirm that.
I updated to Languard 7 Build 20060118 lately after using 6 and 5 for already some time.
I used all the time a Terminal session to remote control the Server where LanGuard is installed.

Today I scanned a computer I just setup with W2K and SP4.
With remote desktop I got 'could not connect to remote registry'

After searching for this problem I finally found your post and tried to scan from the server console.

From there Languard could connect to remote registry and found of course all the missing patches.

Michael



Nicks -> RE: Languard 7 and terminal window madness (30.Jan.2006 3:31:19 AM)

Hi,

Just to let you know that we have managed to reproduce the problem on servers that allow more than one terminal services sessions, like Windows 2000 SP4 server or Windows 2003 server. The problem was not reproduced on Windows XP.

We are currently researching further the problem.

Thank you.



rex -> RE: Languard 7 and terminal window madness (30.Jan.2006 7:44:04 PM)

quote:

Nicks


Hello,

Yes I can connect using the remote registry without languard.  It does appear to be something with langard.

Rex



Nicks -> RE: Languard 7 and terminal window madness (6.Feb.2006 10:40:15 AM)

We researched the issue and it seems that when you connect on windows servers (either Windows 2000 or Windows 2003) via Terminal Services they need a privilege enabled for the user used to connect if you want to run a LANguard NSS scan from the terminal session.

On workstations it works ok, but on servers the privilege is required even for local administrators.

To resolve the problem, you need to elevate the rights of the account used to connect via Terminal Services with "Replace a process level token" right. To do so, on the computer where LANguard NSS is installed, open the Control Panel / Administrative Tools / Local Security Policy and add the user account to the "Replace a process level token" right. (You may have to logout or even reboot to have this change take effect.)



rex -> RE: Languard 7 and terminal window madness (6.Feb.2006 11:53:44 AM)

Hi Nicks,

I'm sorry but that didn't work.  I carefully went through your steps exactly and rebooted to make sure and got nothing.  The only way I found to get around it is to add the "applications" scan to the "missing patches" scan, then it works. 

I've been a langard user for many years on this 2000 server.  There was nothing wrong with the previous versions, it was only when I got to v7 that the problems occurred.  Perhaps there is a setting somewhere in langard that needs to be fixed.  I think you are almost there...

Thanks,
Rex



Nicks -> RE: Languard 7 and terminal window madness (7.Feb.2006 10:06:18 AM)

Hi Rex,

Can you also try the following:

1. Go to Start -> Run, and type "dcomcnfg" and press Enter
2. Change to Component Services -> Computers -> My Computer -> DCOM Config (note the path may be different depending on OS)
3. Right click on LNSSCommunicator, and select properties.
4. Change to the Identity tab.
5. Select "The interactive user" option.
6. Click ok to save the changes.



wurtter -> RE: Languard 7 and terminal window madness (7.Feb.2006 1:56:03 PM)

 
I can confirm that this is also happening on my GFI NSS 7.0 installed on my Windows 2003 server accessed via a terminal server session.

None of the above posted solutions work.

/*Raj*/



rex -> RE: Languard 7 and terminal window madness (7.Feb.2006 4:22:11 PM)

This did correct some of the problems I was facing, but then again, it also caused some more problems.  When I run the default scan or any other scan now (besides the apps scan), it works fine.  However, when I run the "Applications" scan alone it still give me no results.  If I add the "Applications" scan to the "Missing Patches" scan then everything works fine. 

But now from all this I have a different problem, (after I did the correction below)... Now when I run a scheduled (or automated scan) nothing appears.  I checked the Reports folder and nothing has been populated in there.  I'm not sure what to do next.

Rex



Nicks -> RE: Languard 7 and terminal window madness (8.Feb.2006 5:19:51 AM)

Raj,

Kindly try the solutions provided above.


Rex,

Regarding the Applications scan, we will have to check further.

Regarding the scheduled scans, this seems to be a problem with the GFI LANguard NSS 7.0 Attendant Service. This service will initiate the scheduled scans. Can you ensure that this service is running. Check also that the logon account for the service is allowed to start the scheduled scans.



wurtter -> RE: Languard 7 and terminal window madness (8.Feb.2006 2:09:56 PM)

 
Nicholas,

I did try the above "solutions" but they do not work.

Thanks,
/*Raj*/



rex -> RE: Languard 7 and terminal window madness (9.Feb.2006 6:49:45 PM)

Hi Nicks, yes the service is running and I've played with the login accounts (permissions) many times.. I've tried two differnet accounts so far.  The whole thing was working before I tried the steps above.  Now it doesn't want to work anymore.  I've sent you guys my trouble shooting files just a few days ago, maybe that will show you what's going on.


Thanks,
Rex



Nicks -> RE: Languard 7 and terminal window madness (16.Feb.2006 12:42:10 PM)

Hi,

Upon further investigations, we noticed that the identity should be that of the launching user.

Can you please try the following:

1. Go to Start -> Run, and type "dcomcnfg" and press Enter
2. Change to Component Services -> Computers -> My Computer -> DCOM Config (note the path may be different depending on OS)
3. Right click on LNSSCommunicator, and select properties.
4. Change to the Identity tab.
5. Select "The launching user" option.
6. Click ok to save the changes.



Page: [1] 2   next >   >>