Windows Internet Connection Sharing Dave Eitelbach…….ppt

Windows Internet Connection SharingDave Eitelbach Program ManagerNetworking And CommunicationsMicrosoft Corporation Goals Enable multiple users in the home to connect to the Internet Handle roaming laptops transparently Simplify or eliminate configuration Enable telecommuting using the Internet as a WAN (VPNs) Issues For Deployment Of Home Networks Installation should be easy There are no Net admins at home . Automatic Network Configuration has to be automatic There are no Net admins at home .. Network health and recovery should take care of itself There are no Net admins at home ... Requirements Transparent network configuration for end user No client software (from both IHVs and OEMs) Support for legacy and non-Windows clients Demand dial support Support for remote client UI for demand dial control and progress indication Dial control and client “usage” APIs Comprehensive protocol support Built in support for basic protocols (e.g., FTP, etc.) Built-in support for Internet games (no config UI) Built-in support for VPNs (e.g., PPTP) Connecting To The Internet Share the Internet connection transparently for both Dial-Up media Always-available media Resolve Internet names to addresses Use Internet protocols (DNS and DHCP) to solve the problem Clients on the home network should just work Addresses And The Internet Home network clients need to share the public IP address of the gateway system when sending and receiving traffic on the Internet Internet addresses must be unique and routable Private home addresses won’t work Consumer Internet access (via an ISP) is typically a single IP address Connection Sharing Architecture “Connection Sharing components: NAT transparently shares single public IP address for clients on the local network DHCP Allocator assigns address, gateway and name server on the local-network DNS Proxy resolves names on behalf of local-network clients Auto-dial makes connections automatically Alternative Gateways Basic options for Int