Home > Internet > Managing Samba: Windows Network Identity BasicsManaging Samba: Windows Network Identity Basics Submitted by Emilia Yeh 2005-11-02 Internet 7 CommentsSamba Team co-founder John H. Terpstra kicks off a six-part, two-month series that can help Linux administrators master Samba-3 management. This first installment introduces the Samba series and covers a tutorial on Windows network ID basics.About The Author Thom HolwerdaFollow me on Twitter @thomholwerda 7 Comments 2005-11-02 7:57 pm odin749Samba is a great product. With my company I am currently in the early stages of using it for all our linux and unix boxes to impliment a single sign on system. I had alot of trouble getting AD2k3 and Samba to play together nicely and must of the stuff on the web was just about how to get it setup not how to troubleshoot the many stange problems that can occur. I look forward to ready the rest of this set of articles because it sounds like it will of information directly related to my current projects. 2005-11-02 9:06 pm The article renders horribly on my 1024×768 laptop display using firefox. As a workaround use your favorite text www browser (lynx, w3m, links, etc.). 2005-11-02 9:39 pm BnonnYah, the page wrapping is broken on Firefox 1.5 RC and 1.0.7, at least on Windows. Doesn’t seem to matter what your resolution is. 2005-11-03 1:42 am Well, even on IE 6 it’s a disaster… (surprised anyone?) 2005-11-02 10:31 pm http://allinthehead.com/retro/218/accessing-a-windows-2003-share-fr…http://www.google.com/search?hl=en&lr=&newwindow=1&safe=off&c2coff=…http://groups.google.com/group/microsoft.public.windows.server.acti…)&rnum=3&hl=en%23cc897ccb0d976354(Digitally sign SMB communications (always)) is the default in W2K3 Server despite the fact that it only works with W2K/XP clients. There’s a Solaris box I can’t SMB into from home because its SMB is managed by a W2K3 box in front of it. 2005-11-03 7:25 am Just disable the policy on the server or hack the registry. 2005-11-03 1:40 pm Its kind of dissapointing seeing this kind of thing. The open source communities love to kick MS for security breaches. Then when it comes to wanting something you throw away the SMB signing. Convenience over security is often used to lash MS.If its my organisation, the SMB signing stays. Clients in the windows world can sign on using the updated client. Non-windows clients – well, thats more tricky. The choice of end client should have been decided before switching to a 2k3 backroom.In addition, its patently false to claim signing only works on 2k/xp – you just need the client for downlevel OS versions.The alternative is not to use 2k3 at all, and switch to SMB on Linux/Unix servers and run with NT/2000 level security.Lets try and stick to factual information when we are discussing. Making flagrantly inaccurate statements, does not inspire any idea that people know what they are discussing.