MM&M UG UK

Hi To All, im happy that i could now perform DRP of AD and Exchange 2003:)

But after i closed my previous post regarding AD+exchange DRP with the help of one Expert, Fishdar (thank you friend!), i noticed that even i restored AD and was able login to client OS with the client user account, when i checked the ip address of the client machine i got 169.x.x.x ip address! (but i was able to login)-  Why the user account can log in even the machine has 169.x.x.x ip adrs?

Secondly, i noticed that the DHCP is not restored (probably this answered the question why the client machine got 169.x.x.x ip, but user account can login with this ip:(... ) so thats why restored the DHCP Db on my server and login to client machine locally with local admin account then release/renew the IP address, ok. i got 192.168.100.20 (first ip on my dhcp scope range), with this, i was able to launched nslookup with positive result! it can resolved my DNS server. After i got the new IP addrs, i logoff with the local admin account and login with domain user account- result- Failed! error message "domain controller is not available"

Note: Domain admin account cannot able to login on my first statement with 169.x.x.x and also on my second statement with valid ip address on my dhcp range.

why? why? why? please i need your ideas on this.

Thank you.
-charles

Sounds most likely that you need to set a static IP on your DC and then ensure that all the DNS records are updated.

A reboot would be the simplest way.

 

Cheers

Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk