Ok, so many of us have wrestled with DisableStrictNameChecking in the past and once you understand what and why you need it, for the most part, you're good to go. So I have 2003, 2003R2, 2008 & 2008R2 servers all working great (some hardware, some VM) except for '1'! A hardware based print server that will not accpet a alias FQDN to connect. I can only assume as it's settings and registry (even checked spelling of the registry setting) are identical to others that this must be related to the fact it is MH'd? NE1 else have this issue, can I at least assume this is a confirmed bug / short coming, is there a work around? I suspect there is some limitations as we're dealing with FQDN & MH, perhaps this issue is like a cluster enviroment with NIC swapping? As a FYI, we need 3 seperate IP as it is also a backup server and we target specific NICs for specific jobs for performance reasons and time of day. Until later .... Brett

Hi, I would like to confirm what is the main issue, “DisableStrictNameChecking” cannot enable the capability to connect to a print server with alias or others? If so, please refer to the following Microsoft KB article for how to fix this issue: How to consolidate print servers by using DNS alias (CNAME) records in Windows Server 2003 and in Windows 2000 Server http://support.microsoft.com/kb/870911 In addition, multihomed network is not recommended. For more information, please refer to the following Microsoft KB articles: Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294 Name resolution and connectivity issues occur on Windows 2000 domain controllers that have the Routing and Remote Access service and DNS installed http://support.microsoft.com/kb/830063 Delay in NetBIOS connections from a multi-homed computer http://support.microsoft.com/kb/166159 Regards, Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Yes, other than the DNS/DC article which isn't the issue here, it is done that way or doesn't apply. As I stated, we have it working both NETBIOS and FQDN in many other instances, only this is failing in FQDN. This is a 2008R2 member server (hardware) in 2008 R2 / 2003 R2 mixed mode domain / forest. I can only assume this feature has a shortcoming when used via FQDN and MH. Now with iSCSI, MH / Multi NIC systems is simply a issue that must be dealt with, I would suggest Microsoft will have to come up with something better to resolve this then suggest to refrain from MH / Multi NIC. Again in 2008 R2 with additional features compared to a default install of a 2000/2003 I've run into issues making registry setting changes based on a previous OS version so I am more inclined to ensure there will be the desired effect when the change is made. Until later .... Brett

Hi, If you still want to use the multihomed server, you may refer to the following Microsoft TechNet articles: Default Gateway Configuration for Multihomed Computers http://support.microsoft.com/kb/157025 Configuring Multihomed Servers http://technet.microsoft.com/en-us/library/cc772564.aspx Multihomed DHCP Servers http://technet.microsoft.com/en-us/library/cc958910.aspx Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I don't want to sound rude but you really don't understand this issue do you? Have you used DisableStrictNameChecking in a production enviroment? The server is not doing DC,DNS or DHCP, it is a member server and if you look at my priginal post, it all works as it should with the exception of 1 FQDN alias, on that very same server the NETBIOS alias works fine, it is either by design in R2 or a bug that is not allowing this FQDN alias access, works in 2008 / 2003. Until later .... Brett