http://www.windowsitpro.com/authors/author/author/5777391/rsscomment/5777391en-USSun, 27 May 2012 07:23:02 GMTSun, 27 May 2012 07:23:02 GMThttp://www.windowsitpro.com/article/training-and-certification2/a-study-guide-for-microsoft-s-tcp-ip-on-windows-nt-4-0-exam#commentsAnchorTue, 21 Mar 2006 22:10:32 GMT
it is more useful]]>krishnaTue, 21 Mar 2006 22:10:32 GMThttp://www.windowsitpro.com/article/training-and-certification2/a-study-guide-for-microsoft-s-tcp-ip-on-windows-nt-4-0-exam#commentsAnchorhttp://www.windowsitpro.com/article/auditing/group-policy-for-mobile-users#commentsAnchorSun, 07 Jul 2002 09:33:20 GMT
yes, but how do you restrict certain users priviledges thro’ administrative templates when Not connected to lan! without effecting every user including administrator!]]>Nigel Sun, 07 Jul 2002 09:33:20 GMThttp://www.windowsitpro.com/article/auditing/group-policy-for-mobile-users#commentsAnchorhttp://www.windowsitpro.com/article/auditing/group-policy-for-mobile-users#commentsAnchorThu, 07 Mar 2002 08:02:13 GMT
Maybe I’m just dense or an idiot but there seems to be one big piece of information missing and I can’t seem to find anything on it anywhere. If I have a win2k workstation never connected to the network and I want to enforce policy based on users or groups... How do I assign a policy to a particular user or group. The article says you can do it but doesn’t demonstrate how to do it.]]>hmark Thu, 07 Mar 2002 08:02:13 GMThttp://www.windowsitpro.com/article/auditing/group-policy-for-mobile-users#commentsAnchorhttp://www.windowsitpro.com/article/training-and-certification2/a-study-guide-for-microsoft-s-tcp-ip-on-windows-nt-4-0-exam#commentsAnchorWed, 11 Aug 1999 09:51:19 GMT
I’m an accidental reader of Windows NT Magazine. A few days ago, I browsed through the March issue and read some of the articles. The one that attracted my attention most was Emmett Dulaney’s article (“A Study Guide for Microsoft’s TCP/IP on Windows NT 4.0 Exam”) about testing your understanding of TCP/IP networking in NT. The article included a sample situation that surprised me a lot: “Evan is running a predominantly UNIX shop. However, because of differences in hardware costs, he wants to use an NT server as a router. …” I know NT has advantages in many situations, but routing is not one of them (except maybe in special cases). The motivation suggested in the sample question is completely wrong. Typically, UNIX does not use special, expensive hardware, nor does it need more memory than NT to run. On the contrary, a well-known disadvantage of NT (compared with UNIX) is high memory consumption. I don’t know the typical hardware demand to run NT as a router, but for example, for a Linux installation, a 486 processor (or better) with 200MB of hard disk space and 8MB to 16MB of RAM will suffice (40MB of hard disk space and 4MB of RAM is enough if you don’t care about graphic network configuration tools). If you are more concerned about the hardware cost (and ready to work a little), you can use a 386 processor or with 4MB of RAM and a 3.5" drive. A keyboard and monitor are not necessary (except for installing the system) because you can do all the maintenance over the network. The cost of the operating system (OS) is much lower, too—complete UNIX with all the network services costs $50 to $500. I hope you do not blindly believe that the OS you prefer is a panacea that can be used as an optimal tool in any situation. I don’t believe any such tools exist.
--Rafal Maszkowski

Thank you for your note. The sample question represented a test question you are likely to see when you take Microsoft’s TCP/IP on Windows NT 4.0 certification exam. The sample was not an editorial on whether you should use NT or UNIX as a router. Although UNIX might be a more appropriate OS to use, the exam tests only NT. Sorry the example got you off track with the purpose of the article.
--Emmett Dulaney]]>Rafal Maszkowski Wed, 11 Aug 1999 09:51:19 GMThttp://www.windowsitpro.com/article/training-and-certification2/a-study-guide-for-microsoft-s-tcp-ip-on-windows-nt-4-0-exam#commentsAnchor