Alternate Domain Credential Problem Authenticating

[derek_rose]

I am trying to setup credentials to use to scan another domain, and it is not able to verify the ID. I enter the NETBIOS name, fill out the username line correctly, type in the password and hit OK. I get an error that says "cannot verify logon, wrong username or password"

My concern is that it happens to quick, barely a second. I'm guessing it's not able to reach the other DC in the other domain, although I can ping from that machine.

Any tips on how I can debug what's going on? I did go ahead and reset the password on the other domain to verify that isn't the issue.

[derek_rose]

I didn't have a chance to try adsiedit, but for whatever reason it started working. My error log still shows the same message, but I do have entries from the other domain.

Will have to keep an eye on it.

[Hemoco]

Try to connect with adsiedit.msc to the domaincontroller from the lansweeperserver and specify the same credentials

[derek_rose]

Any recommendations on how I can resolve this from a lansweeper perspective?

[Hemoco]

What's failing is not the actual scanning but reading the computer logon information from the domain controller.

[derek_rose]

I figured I would give the connection tester a try, and that connected with no problems

Remote WMI test
-----------------------------------------------
Found: Microsoft(R) Windows(R) Server 2003, Standard Edition Service Pack 2
\root\cimv2 Remote WMI access test OK

Remote Registry test using WMI
-----------------------------------------------
Found: Microsoft Windows Server 2003 Service Pack 2
\root\default Remote WMI access test OK

That worked for both using pdc-01.domain.com and as well as pdc-01. I obviously did this using alternate credentials.

From within the configuration, I did verify my login is set as netbiosdomainname\username, which was the same syntax I used within the connection tester

[Hemoco]

Could be "wrong username/password" or there is an actual problem with the DC (not likely)

Your login should be netbiosdomainname\username

[derek_rose]

I was able to do both without problems from the lansweeper server

[Hemoco]

are you able to do this from the lansweeper server:

"telnet PDC1-01 389"
or
"telnet PDC1.domain.local 389"

If you can't do the first it's a naming resolution problem

[derek_rose]

It's interesting though -

On the Domain scanning tab, the errorlog.txt seems to be referencing the Domain DNS Name. I have the Domain DNS name and the Domain Netbiosname set correctly. When I go to the Domain credentials tab, I enter in the netbios name.

The errorlog.txt shows domain.com, which is the Domain DNS name.

Don't know if that helps or matters.