To: ToySoldier who wrote (12033 ) 11/4/1998 2:21:00 PM From: keithsha Read Replies (3) | Respond to of 74651
Toy, Netware 5 is not a completely revamped OS. The revamp is code named Modesto and plays catch up with NT's modular microkernal architecture that has been in service since version 3.1. So who is going to experience pain? Novell plans to rip and replace the database engine for NDS, rearchitect the platform's kernal, replace the API's with a VMachine architecture, and create a whole slew of development tools. Whew, a lot of effort and looks like an architecture completely different than Netware today. Although I'm sure they intend to do the right thing and provide a compatibility mode. But the last revamp of the application architecture from VAPs to NLMs did not. The track record and impending architecture change have effectively stalled developer effort in NDS integration. NT went through this process years ago and Windows 2000 replaces the directory database engine and adds services. Developers can extend their existing integration with the NT4 DS to support new objects and services or chose not to. Microsoft's implementation of TCP is pure, in fact it supports over 40 TCP RFCs. There's a list at the end of this post, how about one for Netware 5? ONE of the TCP services it supports is RFC 1001 and 1002 for Netbios. And yes, NT4 uses it to locate a login server. Beyond that, DNS can be used for name services. Windows 2000 eliminates the need for netbios based login server lookup and uses DDNS for the entire name space. As far a scalability goes NTS scales quite nicely in 10-50k user range. Active Directory extends that into millions. NDS seems to scale in that 10-50K range as well although with enormous complexity. Eric Schmidt has indicated the database will have to be replaced to scale beyond what is possible today. These are facts, not insults or half baked opinions that seem to be so common on this board. Keithsha RFCs support by Microsoft NT TCP/IP implementation 768 User Datagram Protocol (UDP) 783 Trivial File Transfer Protocol (TFTP) 791 Internet Protocol (IP) 792 Internet Control Message Protocol (ICMP) 793 Transmission Control Protocol (TCP) 816 Fault Isolation and Recovery 826 Address Resolution Protocol (ARP) 854 Telnet Protocol (TELNET) 862 Echo Protocol (ECHO) 863 Discard Protocol (DISCARD) 864 Character Generator Protocol (CHARGEN) 865 Quote of the Day Protocol (QUOTE) 867 Daytime Protocol (DAYTIME) 894 IP over Ethernet 919, 922IP Broadcast Datagrams (broadcasting with subnets) 950 Internet Standard Subnetting Procedure 959 File Transfer Protocol (FTP) 1001, 1002NetBIOS Service Protocols 1034, 1035Domain Name System (DNS) 1042 IP over Token Ring 1055 Transmission of IP over Serial Lines (IP-SLIP) 1112 Internet Group Management Protocol (IGMP) 1122, 1123Host Requirements (communications and applications) 1134 Point to Point Protocol (PPP) 1144 Compressing TCP/IP Headers for Low-Speed Serial Links 1157 Simple Network Management Protocol (SNMP) 1179 Line Printer Daemon Protocol 1188 IP over FDDI 1191 Path MTU Discovery 1201 IP over ARCNET 1231 IEEE 802.5 Token Ring MIB (MIB-II) 1332 PPP Internet Protocol Control Protocol (IPCP) 1334 PPP Authentication Protocols 1518 An Architecture for IP Address Allocation with CIDR 1519 Classless Inter-Domain Routing (CIDR 1533 DHCP Options and BOOTP Vendor Extensions 1534 Interoperation Between DHCP and BOOTP 1541 Dynamic Host Configuration Protocol (DHCP) 1542 Clarifications and Extensions for the Bootstrap Protocol 1547 Requirements for Point to Point Protocol (PPP) 1548 Point to Point Protocol (PPP) 1549 PPP in High-level Data Link Control (HDLC) Framing 1552 PPP Internetwork Packet Exchange Control Protocol (IPXCP) 1553 IPX Header Compression 1570 Link Control Protocol (LCP) Extensions