>NT doesn't even know it's talking to a Linux machine. Yes and no. Depends on what you're doing. Especially with logging into a domain from a linux machine where your login script requires registry editing and such. Like I said before, you can hack around it, but you will never have the seamless integration that other NT machiens have obviously.
> >> You will never have the seamless integration into the domain that >other NT/2000 systems enjoy. Not anything wrong with Linux, just a fact >of the domain implementation that MS engineered. > >As far as accessing shares and printers is concerned, a Linux machine >behaves exactly like a Windows one. Things as simple as shares and printers yes, but there is a vast world beyond those simple subjects that have, and do, cause problems within a domain. I speak from experience ;) >> >> You also should not have had to set up a static IP for your Linux >box. >> >False, again. There is no reason not to use a static IP address. >> What? That's preposterous. Of course you want to use dynamic IP's on >workstations. And besides, no one said he couldn't use static IP's. I >said there's no reason why he couldn't use dynamic IP's. Think about >it... he's gettign all his references (gateway, etc..) from DHCP.... > >This dynamic/static IP address issue was my big misunderstanding (I'm an >ESL, after all). I apologize. > No need to apologize to me... none at all. If you have specific questions about how to integrate your system with SAMBA please pass them on by all means. The SAMBA mailing list, hosted through samba.org is a wealth of information... which I also highly recommend you utilize. Luck! Anthony -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
