We recently installed SCCM 2007 SP2 on a new server, but we have problems with the disjoint namespace and all workstations are not discovered. Everything works fine on SCCM 2007 SP1 and the workstation are discovered.Here part of the discovery log:ERROR: GetIPAddr - getaddrinfo() for '[Computername].aa.bb.cc' failed with error code 11004. $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Mon Jan 04 14:06:56.617 2010 Tokyo Standard Time><thread=3144 (0xC48)>ERROR: Machine [Computername] is offline or invalid.~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Mon Jan 04 14:06:56.617 2010 Tokyo Standard Time><thread=3144 (0xC48)>The domain name is like aa.bb.cc but the workstation suffix is 11.aa.bb.cc. The SCCM server can ping and reach the client and as said before SCCM 2007 SP1 does not have any issue. I know there was a hotfix before SP1 http://support.microsoft.com/kb/949957/en-us and that the hotfix is included in SP1.Any glues if there is any update or setting for SP2

Have you tried to add the dns suffix (for the clients) to the Advanced TCP/IP settings on the site server?Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

Yes, and also I all compared the settings to our Service Pack 1 installation and they are the same. Pinging the workstation with the short name works also well. I`m just wondering if there are any differences between service pack 1 and 2. At least the version of Adsource.dll is different.

Any updates? I am seeing the same issue. I can resolve systems by short name, but cannot resolve with hostname.domain.com. is there a way to force ConfigMgr to look for short name instead of FQDN?gfraetis

Yes I am seeing the same issue. I have just last week installed a new box with Server 2008 R2 with SCCM 2007 SP2 R2. I get the same error where computers are failing to resolve to an IP Address from their FQDN due to an incorrect suffix. However I can Ping, RDP from SCCM without a problem. We have 3 DNS suffixes added into the Advanced TCP / IP of which one correlates to the workstation i'm using to test. Any ideas?

To my knowledge, this is a confirmed bug when installing the site server on Server 2008 R2; AD discovery does not honor the dns suffix search order list when trying to resolve host names. Your best course of action is to call CSS to get them to document the issue, check on the status of a fix, and maybe get a fix started if its not in the works.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Is anyone able to confirm whether CSS has managed to resolve the fault after reporting it? Unfortunately the educational establishment I work for only receive 2 Support calls under there Agreement which means I do not want to waste their essential credits if CSS will bear no fruits. Please if someone could advise

Calling CSS on this one will not be a waste if for nothing more than to request a fix be created -- once they acknowledge that this is indeed a bug, you will not (to my knowledge) be charged. Reference this post if you need to -- note that I have received confirmation directly from the product group that this is a known issue. CSS may be able to provide you a workaround or some other support.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Hi Guys, We pursued this issue with Microsoft intensely last year. They got us to test the following KB for them before making it public: http://support.microsoft.com/kb/2345551 I know it's a bit late now but in case anyone else needs it.

We are having the exact same problem. I have tried downloading the KB article that you supplied, as this sounds exactly what I need to correct the problem, but every time I download the KB article the password they sent in the email, fails to work. Any suggestions or know a way I can get my hands on this KB article? I have tried multiple email addresses with the same problem

There seems to be a problem with those password emails since yesterday. Microsoft is already informed. You could call CSS (and it should be free).Torsten Meringer | http://www.mssccmfaq.de