Cyrius

It is a business network. I have not made any domain changes recently. It is grabbing it from DHCP. I checked using ipconfig /all and x.x.x.x is showing up as the primary dns, not sure why dcdiag.txt is showing it reversed. Also, for some reason the machine was grabbing an IP from one of the NICs on my DC from DHCP that wasn't in the DHCP scope. Also, this NIC's IP address was showing as a forward lookup zone for my DC, I removed the entry. I disabled that NIC, I am not sure why my predecessor enabled and configured it to use this IP, but no problems have arisen from disabling it. I think my enterprise AV may be messing with the DC, so I took it off for now. I will know where I am at after a lunch-time reboot It turns out this problem is with my DC and not the host machine, I tested with another system that was known to be working, so I need to have this thread moved. I am running Server 2008.

Hi, I have been trying to join this PC to the domain, but I have been unsuccessful. This machine is attached to some quality tracking equipment, so I called the manufacturer to see if they locked down some Windows features because this is pretty common. Here is the error I am getting. I do not know why it would be trying to use a WINS name. The machine grabs an IP through DHCP just fine, and I can ping and remote to the AD Domain Controller, so communication is fine. As a side not, I can access shared drives but it will not let me map them stating that it is already mapped, when it is not. The domain name "domainname" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration. The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "domainname": The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.domainname Common causes of this error include the following: - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses: 4.2.2.2 x.x.x.x -this is correct - One or more of the following zones do not include delegation to its child zone: domainname . (the root zone)

Alright thanks!

I will do this, but where do I run this from??? I just used WDS and I cant find a command window for it. Maybe I am just being dumb here, give me hints? haha

x86 image did not work Since it looks like I will have to dig in to dism I have a quick question. In your opinion would this error would be referencing the capture boot image I created or some problem within the host I am using to create the custom image?

Hello, I am having a strange issue with Exchange/outlook 2010 where the Global Address List is sending emails to a particular user to the wrong address. Instead of going to 'uname@domain.us' it is going to 'User Name@domain.us' with the space and all! At one point I had to remake this user profile as it was corrupted in both AD and exchange, and there is a disconnected mailbox with this users name I cannot get rid of. Anyone ever seen this?

K thanks

By the way, is this the correct forum area? Should I have posted this elsewhere?

I have experience with Watchguard firewalls and I can tell you that they have a pretty decent IPSec Branch Office VPN setup that is easy enough to configure. I have heard good things about the Barracuda VPN device as well. Do you have a firewall in place now? Are you doing this to avoid server browsing in some way?

I will give it a shot. I will let you know whether or not this works. Thanks!

It was a Windows 7 Professional x64 disc. I really want to avoid having x86 on my network because we have already run into issues with printer shares coming from x64 to x86 systems. Can you create a x64 image from a x86 capture?

EDIT: Actually auto-complete is only kinda working now. It will populate from the Global Address List after a few seconds, but it is not saving outside contacts like it did OOB. Guess its on to uninstall/reinstall of Office This issue is just bizarre to me...

Will try this. thanks!

No go, I may look around for other tags though!

Hello everybody, I have a weird issue on a few clients, including my own system, where the auto-complete contacts no longer save after closing Outlook 2010. As a workaround, I have been creating an email to every contact in my list then pressing CTRL-K to save it. This does not save after closing it. Since I have seen a bunch of random fixes for this, I will tell you what I have already tried: Recreation of Email Profile Reinstall of Outlook 2010 Deletion of all Outlook 2010 info in C:\Users\csanderson\AppData\Local\Microsoft\Outlook\RoamCache Deletion of ALL Outlook 2010 AppData Trying to import all the contacts into the AutoComplete.dat file using NK2View, this refuses to work at all. Any info on this would be much appreciated. Thanks!

Hi everyone, This is my first post here so go easy, I couldn't find this exact info :-) I have set up WDS on a 32-bit Windows Server 2008 Standard box. I was following the quick start guide for using it, then attempted to use a guide to capture a client image. The original install and boot images pulled off the disc fine, and I was able to create a capture image through the MMC snapin. The capture image is Win 7 64bit. Then, I ran sysprep /oobe /generalize /reboot and this works all fine and dandy. By this I mean I have a generalized OOBE once PXE fails! Once the system reboots and I go to PXE it goes through "Loading Windows Files" then ends with the following error (Had to copy it from somewhere, mine says dism and not peimg): Windows PE cannot start because the actual SYSTEMROOT directory(X:\Windows) is different from the configured one (x:\Windows~BT\Windows). This can be configured with the peimg /targetpath command. Please consult the documentation for more details. Press the OK button or close this message to reboot. Could someone help me out here? I am not very familiar with DISM OR WDS, and none of this stuff was talked about in the guide. Since my familiarity with these deployments is minimal, please keep it so I can understand it If you need any more info from me let me know please. Thank you very much!