Search results

  1. S

    New 2008R2 Server To 2003 Domain

    It's not the octal to decimal that is giving me a problem. It's the meaning of the entire octet string. There are lots of bytes in there but I've only figured out what the last 4 are in a regular DNS entry. I may need to change things other than just the IP address. (Currently it has a...
  2. S

    New 2008R2 Server To 2003 Domain

    The part that seemed to give me hopw was the line: The host 63fa3998-2396-4450-b046-a8ceb3bf85dc._msdcs.wtbhome.net could not be resolved to an IP address. Check the DNS server, DHCP, server I see that entry in ADSIEdit, but the problem is that the entry for the dnsRecord is an octet string...
  3. S

    New 2008R2 Server To 2003 Domain

    Tried a bunch of things without any good luck, but think I may have some progress that we can work with. I edited the two netlogon files and no luck. I found out that those are written out when the netlogon service starts. (Or in my case attempts to start.) So, I went down the path of getting...
  4. S

    New 2008R2 Server To 2003 Domain

    OK, I did a full search of the boot HD on the server for the string big-rig2 and here are the files where the string was found. I'm thinking of trying a "cleansing" of those references. What do you think? Sound crazy? C:\Users\Administrator\AppData\Roaming\Microsoft\MMC\dnsmgmt (no extension...
  5. S

    New 2008R2 Server To 2003 Domain

    using the .net suffix did not work. Same error from nltest The dcdiag /fix failed because it's looking for big-rig2. Here's the output: Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = big-rig * Identified AD Forest. Done gathering initial...
  6. S

    New 2008R2 Server To 2003 Domain

    I tried that and still had an error opeing the domains & trusts. I then tried to run a just plain dcdiag and it failed with an ldap error. Once I removed the entry from the hosts file I was able to run dcdiag again. Should I try the dcdiag /fix without the IPv6 address in the hosts file...
  7. S

    New 2008R2 Server To 2003 Domain

    Tried the GUI and command line and both failed with the "refused" error.
  8. S

    New 2008R2 Server To 2003 Domain

    Finally got a moment to try this and when I open group policy management there is nothing listed. So I went to "Add forrest" and entered my domain name in the dialog. When I clicked OK it gave me the error "The specified domain either does not exist or could not be contacted." I did some...
  9. S

    New 2008R2 Server To 2003 Domain

    So, I tried the workaround listed in the KB article and no joy. When I double click on the "Manage auditing and security log" entry under "User Rights Assignment" the ass and remove buttoms are both disabled. Also, I tried the "add the record twice" and I keep getting the same error. Won't be...
  10. S

    New 2008R2 Server To 2003 Domain

    OK, tried that and I get an error! Dialog reads: The host record big-rig2.wtbhome.net cannot be created. Refused Nothing in the event log.
  11. S

    New 2008R2 Server To 2003 Domain

    Unfortunately, when I go in to add the new A record it will not let me create the A record with IP_big-rig in the IP address field. It is insisting that I put in an IP address. Should I create the records with 192.168.0.2? (and whatever the IPv6 address is) Or should I just try adding the CNAME?
  12. S

    New 2008R2 Server To 2003 Domain

    Quite sadly, the same error after "cleasning" the registry. Event viewer event ID = 5602 description = An internal error occurred while accessing the computer's local or network security database Next? ;-) On the plus side, dcdiag is looking a bit more like we're erasing traces of big-rig2...
  13. S

    New 2008R2 Server To 2003 Domain

    So I removed ALL IPv6 entries in the DNS server. I then restarted the DNS server service and attempted to open the AD Sites & Services with the same error. :-( After the AD Sites & Services app came up I tried to manually connect to big-rig and it also failed with the interface unknown error...
  14. S

    New 2008R2 Server To 2003 Domain

    Here's the output after doing the registry edit & rebooting. ; ; Database file (null) for wtbhome.net zone. ; Zone version: 5632 ; @ IN SOA big-rig.wtbhome.net. admin.wtbhome.net. ( 5632 ; serial number 900 ; refresh 600 ; retry 86400...
  15. S

    New 2008R2 Server To 2003 Domain

    Other information.... I grabbed the event log from a reboot after I changed the DNS entries. The file is attached.
  16. S

    New 2008R2 Server To 2003 Domain

    OK, got the DNS reconfigured and I still get the "interface is unknown" problem when opening the AD Dimain Services. :wallbash: Output from dcdiag.exe still shows references to big-rig2 (I can post if you want to see.) Shuld I go through and try seizing roles again now that the DNS stuff is...
  17. S

    New 2008R2 Server To 2003 Domain

    Still not sure on the "rename properly" part of the above. Can I just go into the DNS snapin and change the enrties?
  18. S

    New 2008R2 Server To 2003 Domain

    So not 100% sure how to do this. (I got the file edited properly.) But not sure if the file needs to be imported or what. (I created the file using "dnscmd localhost /zoneexport wtbhome.net dns.txt") I did move the file out of c:\WIndows\system32\dns
  19. S

    New 2008R2 Server To 2003 Domain

    Yeah, Oops on the IPv6! Here is the export of my DNS configuration: ; ; Database file (null) for wtbhome.net zone. ; Zone version: 5608 ; @ IN SOA big-rig.wtbhome.net. admin.wtbhome.net. ( 5608 ; serial number 900 ; refresh 600 ; retry...
  20. S

    New 2008R2 Server To 2003 Domain

    Still no joy, the rename fails with the same error. the line that I added to the hosts file was as follows: 192.168.0.2 big-rig.wtbhome.net I also finally disabled IPv6! (Clearing the check mark next to IPv6 was just too obvious for me and it took this long to figure it out!) Possible...
Back
Top