Hello,When I try to join a domain I get the following error : Your computer could not be joined to the domain because the following error has occurred: The parameter is incorrect.I am running as local admin and I am entering adomain admin password when asked.ThanksSteveMORE INFOI have looked at my logfile, I see odd things in the netsetup.log01/09/2009 12:11:22:361 DomainDnsPolicy:01/09/2009 12:11:22:361 Name:apretendname.pre=*)01/09/2009 12:11:22:361 DnsDomainName:apretendname.pre.local01/09/2009 12:11:22:361 DnsForestName:apretendname.pre.local01/09/2009 12:11:22:361 DomainGuid: 787e47e8-62f6-4872-8e8d-fb1930d010d401/09/2009 12:11:22:361 Sid: S-1-5-21-2102921534-791105524-564879143I have changed the SID and Domain GUID... do I really need to :)Note the =* at the end of line 2, intresting "apretendname.pre"should this not be the shortname, not the DSN.and.. its 16chars, looks like a buffer issue. Steve

Hi Steve,I just tried it here and it works fine. How many characters does you domain name has?Peter Forster, MVP Virtual Machine, Austria

domain name has 6 chars, eg ABCABC but the FQDN is longer, its 24 chars long.I have done some googleing and I am not alone with this issue, others have found the issueseen problems in the netsetup log file.I am connecting to a Windows 2000 Domain.Thanks for the input.Steve

Is the client using a domain controller for DNS and no other DNS servers? When you tried to join the domain did you specify the NETBIOS name of the domain or the FQDN? Can you ping the domain controller by NETBIOS name, FQDN, and IP?Kerry Brown MS-MVP - Windows Desktop Experience

The DNS are Domain controllers are the DCs (we have 2)The network infrastructure has not been created just for Win 7, so its pretty standard. (Just got lots of mixed versions, EG 2000 DC with some WK2 Servers and even som W2008 Servers)If I install vista on the SAME Laptop and join the domain it works fine.I have tried using the domain name and FQDN.ThanksSteve

MrSube said: Ourdomain name is 18 digits without the machine name or ".com"I cannot ping our short "NetBios" name or join with it. I can add the same laptop to the domain with Vista x64. However with Windows 7 I see the same problem. Hope someone can help...Thanks, Michael - Asst. Desktop Manager Hi MichaelYou may want to start another thread. It is very hard to troubleshoot for two people within the same thread. Even though your problem is related the solution may be very different. Kerry Brown MS-MVP - Windows Desktop Experience

Steve.Drake said: The DNS are Domain controllers are the DCs (we have 2)The network infrastructure has not been created just for Win 7, so its pretty standard. (Just got lots of mixed versions, EG 2000 DC with some WK2 Servers and even som W2008 Servers)If I install vista on the SAME Laptop and join the domain it works fine.I have tried using the domain name and FQDN. Please post the results of pinging by NETBIOS name, FQDN, and IP for both DC's. Also the results of nslookup NETBIOS nameof both DC's. e.g. "nslookup dcname"In the Network and Sharing Center what type of network is identified - Public, Home, or Work?Have you tried disabling the Windows Firewall?How many NICS are in the workstation?Wireless?What NIC is the workstation using?I'm sure you've already investigated many of these suggestions but it'd be good to know what you've tried that didn't work.Kerry Brown MS-MVP - Windows Desktop Experience

Do you see the same issue in the log file? checkout netsetup.log in %WINDIR%\DebugLook for =*Steve

Yes, I see the same issue:01/09/2009 07:30:54:901 DomainDnsPolicy:01/09/2009 07:30:54:901 Name: teleperformanceu=*)01/09/2009 07:30:54:901 DnsDomainName: teleperformanceusa.com01/09/2009 07:30:54:901 DnsForestName: teleperformanceusa.com01/09/2009 07:30:54:901 DomainGuid: 5407c8ce-584e-4fd5-8548-911f4719e43601/09/2009 07:30:54:901 Sid: S-1-5-21-3837813750-218278948-1069949287Michael - Asst. Desktop Manager

Hi,Yes, this is a known issue within Build 7000 for both Windows 7 client and Windows Server 2008 R2. You will have this issue if the *leading* name portion of your FQDN is more than 15 characters.Examples: northwindtraders.com <-- will give parameter is incorrect.contoso.fabrikam.treyresearch.net <-- will work fine.There will be a hotfix released in the near future (it's been ready, just needed 7000 to hit the street). If you are part of any of the private beta programs, you already have access to this through https://connect.microsoft.com.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Thanks, it would be nice to have the fix..We were on the Vista Ascend program (and the office TAP).I am going to send an email or two to see if I can get on the Windows 7 private beta program.CheersSteve

So if there is a fix for it, why is it not available? I would love to test this out (especially since one of the computers in the house is having serious issues, needing a reinstall) and i've got a replacement system for him, all happily loaded up with win7, just not on the domain.

Same Issue Here. Our FQDN is 20 Characters Long. At least i now know that i'm not the only one and that I'm not crazy.Look forward to the fix as well. The sooner the better. hard to Fully test Windows 7 in a business environment if you can't bind it to the domain :-P

Hi Everyone,The hotfix is now available to download for allcustomers having this issue. The KB article will be following soon, butwe thought you want this ASAP:Download QFE KB961402 "- http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961402&kbln=en-us There are three versions of the file, for x86, X64, and IA64. It is language neutral It is for Windows 7 and Windows Server 2008 R2 (OS agnostic) When you follow this link, it will email you a location to a download of the file(s). This hotfix should only be applied if you are experiencing the following: SYMPTOMS Under the following circumstances, you may receive an error The attempt to join this computer to the contoso.com domain failed. The parameter is incorrect: You attempt to join a Windows 7 or Windows Server 2008 R2 computer to an existing domain using the System Properties UI or with NETDOM JOIN. You attempt to DCPROMO a Windows Server 2008 R2 computer to an existing domain. The NETSETUP log on the computer being joined (located in %systemroot\debug) will also show: 12/23/2008 16:06:19:419 NetpSetLsaPrimaryDomain: for 'northwindtraders' status: 0xc000000d 12/23/2008 16:06:19:419 NetpJoinDomainLocal: status of setting LSA pri. domain: 0x57 12/23/2008 16:06:19:419 NetpJoinDomainLocal: initiating a rollback due to earlier errors 12/23/2008 16:06:19:419 NetpLsaOpenSecret: status: 0x0 12/23/2008 16:06:19:419 NetpJoinDomainLocal: rollback: status of deleting secret: 0x0 12/23/2008 16:06:19:419 NetpClearFullJoinState: Removing cached state from the registry... 12/23/2008 16:06:19:419 NetpClearFullJoinState: Status of deleting join state key 0x0 12/23/2008 16:06:19:419 NetpMarkLastFullJoinAttempt: No offline domain join information found, FinishJoin key not found. 12/23/2008 16:06:19:419 NetpCompleteOfflineDomainJoin: An error occured while completing the offline join action, the action can be tried again. The error code was: 0x57. 12/23/2008 16:06:19:419 NetpCompleteOfflineDomainJoin: status: 0x57 12/23/2008 16:06:19:419 NetpDoDomainJoin: status: 0x57 Note: 0x57 translates to ERROR_INVALID_PARAMETER. The domain does not need to be named NORTHWINDTRADERS.COM for this issue to occur.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Beautiful, Ned. Worked a charm! Only thing I should note, my server is SBS2003 but applied hotfix to my win7 test machine and it is now happily churning away on the domain. now for some real testing.

Thanks!!! its great living in the UK, I sleep and you guys over the pond find fixes toissues for me :)CheersSteve

Putting this to bed: You cannot join a Windows 7 Beta-based or a Windows Server 2008 R2 Beta-based computer to an existing domain, and you receive an error message: "The parameter is incorrect" - http://support.microsoft.com/kb/961402Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

TheQFE worked in my situation as well. Our domain name was exactly 15 characters but still had the problem. The fix solved it. Jm Wooleyhttp://www.LinqInAction.net - "LINQ In Action", The book is now available. Don't wait for the movie

Hi fellow members, long time reader, first post. i managed t get through the hoops as it seemed for our vaio laptop with Windows 7 Pro on it to get onto the domain. that done we now have an issue where we can only randomly ping the DC and vice versa. by this i mean we can ping 1 good packet then 3 time out. then a few second later we get a good 4 consistent packet returns. the dc side too exhibits this as well. all firewalls are off, our gpo also turns them off login scripts and drives map perfectly. we can ping all pcs and servers even in another state but we cn ping our dc consistently. also vnc will run fro the laptop to vnc to another pc but if we try and vnc to the laptop it will not connect. quite the conundrum, tmorrow we are going to uninstall some of the sony "apps" to ensure nothing else underlying is messing wth the icmp to and from. any tips would be appreciated. Tom.