Windows 95 Default TCP/IP Stack Configuration

When Microsoft released the original retail version of Windows 95 in August 1995, it featured a native 32-bit TCP/IP stack, but the protocol was not installed or enabled by default. Instead, the operating system favored local area network protocols of the era, primarily NetBEUI and IPX/SPX. When users manually installed the TCP/IP stack to access the Internet or local intranets, the protocol defaulted to automatic dynamic addressing via Dynamic Host Configuration Protocol (DHCP), enabled NetBIOS resolution, and left manual name resolution systems such as DNS turned off.

Default Installation Status in the RTM Release

In the original release of Windows 95 (Build 950), setup routines evaluated existing network hardware and predominantly installed:

  • Client for Microsoft Networks or Client for NetWare Networks
  • NetBEUI and IPX/SPX-compatible Protocol (NWLINK)

Because dial-up bulletin board systems (BBS), direct local area connections, and Novell NetWare environments were standard in 1995, Microsoft did not bind TCP/IP during a typical install unless the user manually selected it through the Network Control Panel or configured a connection using the newly integrated Dial-Up Networking feature.

Default Protocol Properties When Installed

Once a user added the TCP/IP protocol to a network adapter, Windows 95 applied a specific baseline configuration across several property tabs:

  • IP Address: The stack defaulted to "Obtain an IP address automatically." Windows 95 queried a local DHCP server for an IP address and subnet mask upon boot. If no DHCP server responded, the connection failed to configure an IP address (the automatic private IP addressing scheme, APIPA, was not introduced until Windows 98).
  • Gateway: The default gateway list was blank. Routing was expected to be assigned dynamically through DHCP option 3 or manually input by a network administrator.
  • DNS Configuration: Set to "Disable DNS." Windows 95 assumed host resolution would occur locally through the LMHOSTS or HOSTS file, via NetBIOS broadcasts, or through DHCP-assigned DNS parameters.
  • WINS Configuration: Set to "Use DHCP for WINS Resolution." If the network provided a Windows Internet Name Service server through DHCP scope options, Windows 95 used it; otherwise, WINS remained inactive.
  • NetBIOS over TCP/IP: Enabled by default. Windows 95 depended on NetBIOS over TCP/IP (NBT) to facilitate Network Neighborhood browsing, file sharing, and printer sharing across subnets.
  • Bindings: Automatically bound to all installed network clients (such as Client for Microsoft Networks) and services (such as File and printer sharing).

Dial-Up Networking Behavior

For users connecting to the Internet through a dial-up modem, the TCP/IP stack operated under Point-to-Point Protocol (PPP). By default, Dial-Up Networking negotiated IP settings directly with the Internet Service Provider's (ISP) network access server. It requested a dynamically assigned IP address, server-assigned DNS addresses, and enabled IP header compression (VJ compression) while leaving default routing redirected through the remote connection.