TL;DR: In this article, a DCE RPC mechanism was proposed to enable client machines to make remote procedure calls to server machines in a distributed computing environment using NETBIOS protocol support. But this protocol support was not provided by using application names similar to TCP/IP conventions.
Abstract: A DCE RPC mechanism normally uses a TCP/IP-based transport service to enable client machines to make remote procedure calls to server machines in a distributed computing environment. NETBIOS protocol support for the RPC mechanism is provided by using NETBIOS application names similar to TCP/IP conventions and through use of connection-oriented or connection-less NETBIOS protocol sequences. In particular, NETBIOS names are used as though they include a fixed portion representing a machine, and a dynamic portion representing an application on that machine. New functions are provided to use NETBIOS names in place of TCP/IP addresses and these NETBIOS names are then used via the sockets API, leaving RPC's use of the sockets API unchanged.
TL;DR: This chapter discusses NetBIOS Programming in Windows NT, an Overview of Novell NetWare, and Guidelines for 16-bit Windows Sockets Applications.
Abstract: 1. Introduction. Historical Perspective. Impact of Windows NT Design on Users. Impact of Windows NT Design on Developers. Client/Server Computing with Windows and Windows NT. Summary. 2. Understanding Windows NT Architecture. Salient Windows NT Architecture Features. Networking in Windows NT. Salient Win32 Programming Features. Creating an Echo Server. Summary. 3. Understanding Windows Architecture. Operating Modes of Windows. Networks in Windows for Workgroups. Summary. 4. Remote Procedure Call (RPC) in Windows NT. Historical Perspective. Microsoft RPC Concepts. Writing a Simple RPC-based Client and Server. Designing Efficient RPC Client and Server. Designing Communication Infrastructure. Using Callback Routines. RPC Management. RPC Error and Exception Handling. Secure RPC. Echo Server--RPC-based Win32 Server. RPC Programming in Windows. Summary. 5. Windows Sockets in Windows NT. Introduction to Sockets Programming. Windows Sockets Extensions. Interoperability with IPX/SPX based Applications. Name Service Provider APIs. A Windows Socket Based Win32 Service. Guidelines for 16-bit Windows Sockets Applications. Summary. 6. Pipes in Windows NT. Named Pipes in Windows NT. Anonymous Pipes. Win32 Service Using Named Pipes. Named Pipes in Windows. Comparison with UNIX Pipes. Summary. 7. Using Mailslot in Windows NT. Architecture of Mailslots. Programming Mailslots. A Win32 Service Using Mailslot. Mailslots in Windows for Workgroups. Summary. 8. NetBIOS Programming in Windows NT. Overview of NetBIOS Programming. NetBIOS Support in Windows NT. NetBIOS Programming in Windows NT. A NetBIOS-based Win32 Service. NetBIOS Programming in Windows. Summary. 9. SPX/IPX Programming in Windows NT. An Overview of Novell NetWare. NetWare Services. IPX Programming. SPX Programming. Summary. Bibliography. Appendix A: Determining NetBIOS System Characteristics. Appendix B: Window Socket. 0201590565T04062001
TL;DR: A test laboratory for the performance analysis of the Transmission Control Protocol (TCP) and the teaching of its basic concepts is proposed, and students perform traffic measurements on a real network.
Abstract: A test laboratory for the performance analysis of the Transmission Control Protocol (TCP) and the teaching of its basic concepts is proposed. The laboratory environment is a small Ethernet local area network (LAN) with PCs running different versions of the Windows operating system (95/98/NT/2000). To support the Internet Protocol Version 6 (IPv6) for Windows and to improve flexibility, the Netperf TCP software tool has been modified. Based on the modified Netperf and a protocol analyzer, students perform traffic measurements on a real network. Various aspects of the Microsoft TCP implementation for Windows are discovered and clearly explained. The IPv6 for Windows 2000 is also examined, and comparisons with IPv4 are made.
TL;DR: Experimental results showed that Windows XP provides better results for UDP Throughput than Windows7 & Windows7 can provide betterResults indicated that IPv4 have superior results in terms of TCP throughput and UDP throughput as compared to IPv6.
Abstract: In this Research Paper, We have evaluated the performance of IPv4 and IPv6 using Windows XP and Windows 7. In this study TCP (Transmission Control Protocol) Throughput and UDP (User Datagram Protocol) Throughput have been compared for protocol IPv4 and IPv6. Experimental results showed that Windows XP provides better results for UDP Throughput than Windows7 & Windows7 can provide better results for TCP Throughput than Windows XP. Results indicated that IPv4 have superior results in terms of TCP throughput and UDP throughput as compared to IPv6.