4100 NT4 domain -> AD domain - DC IP unresolvable [fix]
Hi all,
After a two stressed out days, and after many hours googling etc. today I finally resolved a serious problem I was getting at work with the help of Snap tech support (finally I got a guy who knew what he was talking about).
We have five 4100 NAS boxes serving 300GB+ data to 200 clients. We are migrating from a NT4 domain to Win2003 Active Directory domain.
Over Xmas (Xmas eve and Xmas day in fact) I flashed up the boxes to the latest SnapOS 4.0.860 (UK) ready for AD.
On the test box, I changed to the AC domain and set the user up. Rebooted.
Then I kept getting this in the logs:
SMB: Can't resolve master browser IP address for domain <DOMAIN>
And of course couldn't do much else as no DC was found so no ACL list etc. A box on it's own.
I tried everything, including reading almost all the threads here for enlightenment.
The fix is really to do with the way Snap 4100 hasn't really got a DNS configuration page, so the tech guy said we will have to hack the hosts file.
So, presume this arrangement:
Domain name: Mickey
DC IP Address: 123.456.789.123
DC machine name: Mouse
Then in http://<server IP>/config/debug enter these two lines consecutively:
hosts Mickey ip 123.456.789.123 <OK>
hosts Mickey machine Mouse <OK>
Reboot.
You will now find DC controller is found, and immediately ACL is pulled in from the AD DC.
Hope that helps somebody.
Nick
|