We’re currently experiencing a high volume of support requests, which may result in longer response times — Thank you for your patience and understanding.
Community FAQ
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
76012
Engaged Sweeper II
I am successfully using 3.1 with an NT4 domain. Is there any reason my setup should not continue working if I upgrade to 3.2?
8 REPLIES 8
Hemoco
Lansweeper Alumni
76012 wrote:
I am successfully using 3.1 with an NT4 domain. Is there any reason my setup should not continue working if I upgrade to 3.2?

There is an extra item scanned : the active directory computer configuration.
This part of the scan will fail every time and will produce much errors in the logs.
76012
Engaged Sweeper II
Lansweeper wrote:
76012 wrote:
I am successfully using 3.1 with an NT4 domain. Is there any reason my setup should not continue working if I upgrade to 3.2?

There is an extra item scanned : the active directory computer configuration.
This part of the scan will fail every time and will produce much errors in the logs.


Yes, we do get a lot of errors for this.
76012
Engaged Sweeper II
I was referring to the application working in an NT4 domain rather than an Active Directory environment.

Our only NT4 computers are the PDC and BDCs. We cannot scan the NT4 computers. They give an error "The Procedure * could not be located in the DLL secur32.dll" when attempting to execute lsclient.exe

Sorry for the confusion...
Hemoco
Lansweeper Alumni
76012 wrote:
I was referring to the application working in an NT4 domain rather than an Active Directory environment.

Our only NT4 computers are the PDC and BDCs. We cannot scan the NT4 computers. They give an error "The Procedure * could not be located in the DLL secur32.dll" when attempting to execute lsclient.exe

Sorry for the confusion...


Haven't tried it because NT4 is not supported, but have you tried active scanning in an active directory forest with NT4 clients?
ccdesktop
Champion Sweeper
Lansweeper wrote:
Haven't tried it because NT4 is not supported, but have you tried active scanning in an active directory forest with NT4 clients?


Since using Active Scanning Lansweeper is now showing a handful of NT4 machines.

I know NT4 is not supported - but do you have any way of helping me to understand why some NT4 machines are picked up by Lansweeper and others are not.

I have checked two machines that seem identical in most areas - Lansweeper detects both but only shows NT4 against one of them. The other it just shows up Red without any s/w or o/s information.

We are desperately trying to locate all our NT4 machines as we want to get rid of them so being able to pick out NT4 machines would be really helpful.

Any ideas...anyone...?
76012
Engaged Sweeper II
ccdesktop wrote:
Lansweeper wrote:
Haven't tried it because NT4 is not supported, but have you tried active scanning in an active directory forest with NT4 clients?


Since using Active Scanning Lansweeper is now showing a handful of NT4 machines.

I know NT4 is not supported - but do you have any way of helping me to understand why some NT4 machines are picked up by Lansweeper and others are not.

I have checked two machines that seem identical in most areas - Lansweeper detects both but only shows NT4 against one of them. The other it just shows up Red without any s/w or o/s information.

We are desperately trying to locate all our NT4 machines as we want to get rid of them so being able to pick out NT4 machines would be really helpful.

Any ideas...anyone...?


http://www.systemtools.com/free.htm

Download NetView and use the /T switch

Returns this for me:
Windows NT PDC 4.0
Windows NT BDC 4.0
Windows NT BDC 4.0
76012
Engaged Sweeper II
Lansweeper wrote:
76012 wrote:
I was referring to the application working in an NT4 domain rather than an Active Directory environment.

Our only NT4 computers are the PDC and BDCs. We cannot scan the NT4 computers. They give an error "The Procedure * could not be located in the DLL secur32.dll" when attempting to execute lsclient.exe

Sorry for the confusion...


Haven't tried it because NT4 is not supported, but have you tried active scanning in an active directory forest with NT4 clients?


No. We don't have any NT4 computers in AD.

Scanning the NT4 computers is not an issue for me since we only have a few. I'm just happy the NT4 domain works!
ccdesktop
Champion Sweeper
76012 wrote:
I am successfully using 3.1 with an NT4 domain. Is there any reason my setup should not continue working if I upgrade to 3.2?


76012 - How are you getting LS to work with NT4? I have been trying for ages to pick up our NT4 machines without much success.

Have you any special tricks up your sleeve? Whenever you do lsclient servername from an NT4 workstation we get an error message.

Hope you can help.

Archive

This board contains archived posts from the retired Lansweeper Forum and Insiders Community.

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now