FQDN problems
Just a little bit of history, I have been using SD since ver 5. We have not had the FQDN issues until we upgraded to 7. We currently have many machines still on an NT 4.0
domain. Here is the problem, which others have posted about but for different reasons:
Say my NT domain is Adventnet. And I have a computer named TEST1. SD (before the upgrade) would scan the computers, using netbios to find TEST1, use wmi to pass the domainname\administrator (i.e. Adventnet\administrator) and the password, and scan no problem.
Now, since ver 7, SD decides to append the FQDN name to the computer name (TEST1.adventnet). Now, for those that dont know NT 4 DOES NOT use dns, it uses netbios and WINS! It never finds the machine and then fails.
I called tech support and he told me to use network scans. This is for one a real PITA, because I have almost 20 subnets. But that aside, it still doesnt work, because apparently the network scan will not pass the username as "adventnet\administrator", only "administrator", and using local machine passwords is NOT an option.
I dont see any good reason to append FQDN to the machine names. On a correctly set up SD server, it would already append that info for you when looking for AD machines using its TCP/IP DNS settings. Why would you guys decide to do it for us!?
domain. Here is the problem, which others have posted about but for different reasons:Say my NT domain is Adventnet. And I have a computer named TEST1. SD (before the upgrade) would scan the computers, using netbios to find TEST1, use wmi to pass the domainname\administrator (i.e. Adventnet\administrator) and the password, and scan no problem.
Now, since ver 7, SD decides to append the FQDN name to the computer name (TEST1.adventnet). Now, for those that dont know NT 4 DOES NOT use dns, it uses netbios and WINS! It never finds the machine and then fails.
I called tech support and he told me to use network scans. This is for one a real PITA, because I have almost 20 subnets. But that aside, it still doesnt work, because apparently the network scan will not pass the username as "adventnet\administrator", only "administrator", and using local machine passwords is NOT an option.
I dont see any good reason to append FQDN to the machine names. On a correctly set up SD server, it would already append that info for you when looking for AD machines using its TCP/IP DNS settings. Why would you guys decide to do it for us!?