ICTCity

Can you please DELETE all the entries for IPv6? I see there's a zone for IPv6 and a A record. Also the two A records have the same "weight", when the DC try to use the IPv6 it doesn't work. We must delete everything related to IPv6!

I think you're right. Please confirm.

Start > run > gpedit.msc > User Configuration\AdministrativeTemplates\Start Menu & Taskbar Cheers

I'm still waiting for somebody who can explain me the advantages from a core installation. I just saw you can't manage everything (for example IIS), you have to use another server to open snap-in and log on remotely... THE HELL!!! What's the point? Really, I use Windows and I like it, but WHY develop a core install if you can't actually manage your server?!?!?! I'm really disappointed!

Do you have another server? If yes, open domain and trusts from there and connect to the dc by typing the ip. Let me know. Somebody explain me WHY you can't manage a server with core install -.- now I want to open a new topic in this forum!

Grrrrrrrr f****ng ipv6!!! First try this procedure which surely disable IPv6: http://www.windowsreference.com/networking/disable-ipv6-in-windows-server-20008-full-core-installation/ Then Export and post the DNS configuration again. The first error is interesting: The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. It looks like it's trying to access another server via the wrong interface! I'm still trying to find a way to manage domain and trust from command line...

Ciao Andrea, Puoi pf postare il tuo problema in italiano? Almeno capisco qualcosa di pi, perch sinceramente non ho capito molto eheheh. Traduco io il tuo posto :) Hi Andrea, can you please post in italian (I see you're from Rome), so I can understand a bit better your problem? I will translate for you.

Hi, What does "win7 machine filters it out" mean? Check that the new policy is the "primary" in that OU, pay attention to LINKED GPO. Let me know.

To do this, check this tutorial, it may help you: http://serverforum.org/tuts/t-37-use-process-monitor-to-set-up-permissions-properly/

try the same step in SAFE MODE WITH NETWORK.

yes :)

Mhhhh that's a good question. I think you should copy the original file, modify it as I suggested before, stop dns service (open DNS snap-in > right click > stop), rename the new file properly, flush DNS cache, restart DNS and export again everything just to be sure everything has gone in the properly way. EDIT ***Uh... DELETE ALSO the entry for ipv6!*** After that, try to open sites and services and tell me if you have the same error again. DO NOT RENAME YOUR SERVER! We are going to fix this problem in another way. Check event log for a while. If you can open sites and services with no errors... we can be a bit more happy :) If not... well... I still have time before the clean install :P

Comment out (put the ";" at the beginning) all the lines with BIG-RIG2 and substitute them with big rig. For example: ; _ldap._tcp.wtbhome._sites.gc._msdcs 600 SRV 0 100 3268 big-rig2.wtbhome.net. _ldap._tcp.wtbhome._sites.gc._msdcs 600 SRV 0 100 3268 big-rig.wtbhome.net. Flush cache and retry. (Give it some time...)

Mhhh can you try this please? net stop wuauserv Rename c:\Windows\SoftwareDistribution SoftwareDistribution_OLD net start wuauserv Download and install this: (I think you still tried this step but please repeat it because now you renamed the updates's folder) http://www.microsoft.com/downloads/en/details.aspx?FamilyID=914fbc5b-1fba-4bae-a7c3-d2c47c6fcffc&displaylang=en The operation can take up to 1 hour. Let me know.

Can you remember when I told you to disable the ipv6 before migration? eheheh Problems are two: error in name (big-rig / big-rig2) and IPv6. big-rig2 and big-rig2.wtbhome.net are the same thing, big-rig sounds like an Alias. To export dns entries use the command prompt and type: dnscmd I know we can find a solution :)

Windows updates aren't the guilty. The error IP ALREADY IN USE means that somebody has taken this IP. Does your lacie has a STATIC or DYNAMIC (DHCP) IP? Do you have a DHCP server on your network? The problem is easy, when somebody log in remotely, he takes the same IP of LACIE. Now I need to understand your network config, so please answere to my questions. Cheers

To allow users to be able to install programs, you must understand the "Software Restriction Policy": http://technet.microsoft.com/en-us/library/bb457006.aspx I know it could be annoying, but assign the wrong permission to software installation, can be harmful for your system (not only for malwares). To deny users to shutdown the server: Local Policy > Users rights assignment > SHUT DOWN THE SYSTEM Select only the user / group you want to able to shutdown your server. Remember that GPO must be refreshed to take effect: start > run > gpupdate /force Or you can restart the server...

Hi and welcome to the community. Enjoy your stay!

I just need the last attempt... pleeeeeease :) Open this file: C:\Windows\system32\drivers\etc\hosts you should see only the localhost, add these lines: 192.168.0.2 big-rig wtbhome.net Then retry with rename. After this we could look at the clean install, anyway we have to pay attention by importing DNS, I think the best way is to create a new DNS service (I don't think you have thousand of names...), regarding AD it's quite easy, look at these document: http://technet.microsoft.com/en-us/library/cc771290(WS.10).aspx I really suggest you to WAIT before doing a clean install, now the situation is working in some way and I think we could come to a solution... . Anyway, if you want to do it, try first a simpler way before: Install a new server (let big-rig / 2 up and running). Choose a name and NEVER change it :P (don't call it big-rig or big-rig2!!!) Add that server in domain and, when asked, choose that it will be part of an existing domain, then make it as a global catalogue. Once you are finished, wait until replication has been completed, you will have all your objects in the new DC. Now you can demote the big-rig / 2 and turn it off. Let me know... we still have time until saturday :)

I really cannot tell you what can happens by renaming the DC... I think that you could try seizing roles... and just after that... try the rename... Actually I don't know what can happen...

It's easy: From the command line type: repadmin /showrepl Server_Name.YourDomain.Whatever and then: dcdiag /test:replications Let me know. Cheers

That's ok :) So... now I've found the problem... but actually I'm not sure about the solution. The problem is the renaming of your DC made before the migration. As you can see, both BIG-RIG and BIG-RIG2 are responding from the same IP. I *THINK* that the problem is when a DC operation is performed, the DNS resolve both big-rig & big-rig2 correctly, but the operation cannot be completed due to the same IP. I tought about 2 solutions, but I AM REALLY NOT SURE ABOUT CONSEQUENCES you may have. 1) rename your DC from big-rig to big-rig2 2) Follow this procedure: Transfer FSMO roles To transfer the FSMO roles by using the Ntdsutil utility, follow these steps: Log on to a Windows 2000 Server-based or Windows Server 2003-based member computer or domain controller that is located in the forest where FSMO roles are being transferred. We recommend that you log on to the domain controller that you are assigning FSMO roles to. The logged-on user should be a member of the Enterprise Administrators group to transfer Schema master or Domain naming master roles, or a member of the Domain Administrators group of the domain where the PDC emulator, RID master and the Infrastructure master roles are being transferred. Click Start, click Run, type ntdsutil in the Open box, and then click OK. Type roles, and then press ENTER. Note To see a list of available commands at any one of the prompts in the Ntdsutil utility, type ?, and then press ENTER. Type connections, and then press ENTER. Type connect to server servername, and then press ENTER, where servername is the name of the domain controller you want to assign the FSMO role to. At the server connections prompt, type q, and then press ENTER. Type transfer role, where role is the role that you want to transfer. For a list of roles that you can transfer, type ? at the fsmo maintenance prompt, and then press ENTER, or see the list of roles at the start of this article. For example, to transfer the RID master role, type transfer rid master. The one exception is for the PDC emulator role, whose syntax is transfer pdc, not transfer pdc emulator. At the fsmo maintenance prompt, type q, and then press ENTER to gain access to the ntdsutil prompt. Type q, and then press ENTER to quit the Ntdsutil utility. Taken from http://support.microsoft.com/kb/255504/en-us Sorry, but I can't test this scenario... but if you wanna try, start with the second option (transfer FSMO roles) first, which should be the safest one.

Hi there :)

Mhhhhh can you please run these commands? (from a workstation) ipconfig /flushdns ping big-rig ping big-rig2 ipconfig /displaydns Post results.

Ok, that means I think I've found your problem but I have to think about a solution. If you look at the output of DCDIAG, you can see that many test have been made to BIG-RIG2, which actually doesn't exist... but in some way it just passed tests. Now I'm going to read your output once again trying to understand where is the problem. Of course we need to be able to access Domain and Trusts snap-in, I don't know if there's a way to do the same thing from command line. I'll wait for your restart, then I hope I can find a solution...