Probably depended heavily on what kind of options you needed. WinNT network config covers a lot more than people are aware even if you keep just to TCP/IP - ho

Probably depended heavily on what kind of options you needed. WinNT network config covers a lot more than people are aware even if you keep just to TCP/IP - how many people are aware that all WinNT >=5.0 systems are OSFPv2 routers? There's also of course optional RIP listener, or the part where WinNT >=6.0 is IPv6-first. When the claim was made, you could end up working with few major network protocol families, and while vendors failure was leading to ending GOSIP it was still unclear if TCP/IP would be winner (I think TUBA - aka IPv9 - was still in the running when the prolog part of network configuration was done), you had huge installed base of IPX/SPX (that didn't really go away till early 2000s), you had NetBEUI support for dealing with LanManager variants, there was Banyan VINES you might have to cooperate with (especially if you tried to sell to USMC, iirc), there was X.25, FrameRelay and other WAN specific protocols you might need to support, there was AppleTalk, there was ATM (not just IP over ATM), there was support for dealing with IBM Mainframe networks... All of the above also had presence in the Unix market, and given 1993 release date, all of that was present in some ways - and Microsoft could capitalize on "we can easily support all of that".