4100 NT4 domain -> AD domain - DC IP unresolvable [fix]

[Lethe]

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

[blue68f100]

Thanks for the Info,

I may post this in the wiki section so it doesn't get lost.

[Lethe]

Originally Posted by blue68f100

Thanks for the Info,

I may post this in the wiki section so it doesn't get lost.

I think you should. People without tech support will be stuck otherwise, as there is absolutely no information about this problem anywhere.

BTW, it could be caused by the migration itself, as we still have NT4 domain running on that network segment - so maybe SnapOS finds the wrong master browser (i.e. the PDC of the NT4 domain) and gets it's knickers in a twist.

Nick

[Hallis]

Originally Posted by blue68f100

Thanks for the Info,

I may post this in the wiki section so it doesn't get lost.

That would be good info to have i think. If not then im definately bookmarking this thread in my snap fix reference section.

Shane

[Phoenix32]

Originally Posted by blue68f100

Thanks for the Info,

I may post this in the wiki section so it doesn't get lost.

Yup Yup

[Lethe]

Whoever added the wiki article, it is slightly wrong... there is no <ok> dialog after showing the 'dummy' AD network arrangement.

So, presume this arrangement:

Domain name: Mickey
DC IP Address: 123.456.789.123
DC machine name: Mouse

http://wiki.procooling.com/index.php...able_.5Bfix.5D

Nick

[blue68f100]

<ok> is to execute the debug cmd. Will make let users know. As soon as you enter debug the OK gui is there. Will add a foot note to it.

edit: removed the <ok>'s happy now.

[Lethe]

No.... you missed the point.

The 'example' domain stuff doesn't need <OK> at the end.

So exactly like this:

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>

Nick

[blue68f100]

OK, added the <ok> note happy now.

[Hallis]

I am. very happy.

[eschw95458]

That is perfect, I have been trying for forever to use OS X (10.4) server for authentication and that fixed my problem, I can now pull the lists and athenticate users against the opendirectory.

[Lethe]

I can confirm this works very well - very well indeed.

Today was the start of our migration. I moved all 5 NAS boxes over from NT domain to AD domain.

The move to new domain obviously trashes the ACL's, so all file persmissions have to be re-applied to the new AD ACL list (the 'everyone group' ACL gets retained though whatever it was (read, read & add, change etc.). Shares remain intact, though, which is good news.

I also found you can do this with one reboot - add the snap 4100 to the new AD domain (answer 'restart later' when asked), then apply the above fix in /config/debug - _then_ restart.

Nick

[kanox]

Hello I try this command on the new Guardian OS 5.O not working