GroupSat- solar products

Microsoft Windows includes extensive support for VPNs, including a VPN client and a VPN server. The VPN client running Windows 2000, Windows XP, and Windows Server 2003 supports the use of the Point-to-Point Tunneling Protocol (PPTP) and Layer Two Tunneling Protocol with Internet Protocol security (L2TP/IPsec) for remote access VPN connections. The VPN server in Windows 2000 Server and Windows Server 2003 supports PPTP and L2TP/IPsec for both remote access and site-to-site (also known as router-to-router or LAN-to-LAN) VPN connections. For fast answers to common questions, see Virtual Private Networking: Frequently Asked Questions. For detailed information about VPN support in Windows Server 2003, see the Virtual Private Networks for Windows Server 2003 page. For detailed information about VPN support in Windows 2000, see the Virtual Private Networks for Windows 2000 page.

2Q. What support does Windows provide for IPsec?

Windows 2000, Windows XP, and Windows Server 2003 includes extensive support of Internet Protocol security (IPsec) including Authentication Header (AH), Encapsulating Security Payload (ESP), transport and tunnel mode, the Internet Key Exchange (IKE) protocol to negotiate security associations, the Message Digest 5 (MD5) and Secure Hashing Algorithm 1 (SHA1) hashing algorithms, and the Data Encryption Standard (DES) and 3DES encryption algorithms. IPsec in Windows is integrated with the Active Directory® directory service. IPsec policies can be assigned through Group Policy configuration of Active Directory domains and organizational units. This allows the IPsec policy to be assigned at the domain, site, or organizational unit level, simplifying IPsec deployment. For more information about IPsec support in Windows Server 2003, see the IPsec page. For more information about IPsec support in Windows 2000, see the IPsec for Windows 2000 page. For fast answers to common questions, see Internet Protocol Security: Frequently Asked Questions

3Q. What support does Windows provide for Internet Protocol version 6 (IPv6)?

IPv6 is provided and fully supported for Windows XP with Service Pack 1, Windows XP with Service Pack 2, and Windows Server 2003. For fast answers to common questions, see Frequently Asked Questions About the IPv6 Protocol for Windows XP or Frequently Asked Questions About the IPv6 Protocol for the Windows Server 2003 Family. For detailed information about IPv6 support in Windows, see the Internet Protocol Version 6 page.

4Q. What support does Windows provide for IEEE 802.11 wireless LAN (WLAN) networking?

Windows XP and Windows Server 2003 provide extensive support for IEEE 802.11 WLAN networking including IEEE 802.1X authentication, Wi-Fi Protected Access (WPA), and automated configuration. For fast answers to common questions, see Frequently Asked Questions About Wireless LAN Support in Windows. For more detailed information about wireless support in Windows including deployment instructions for both enterprises and home networks, see the Wireless Networking page.

5Q. Does Windows Server 2003 or Windows 2000 Server include a Remote Authentication Dial-In User Service (RADIUS) server?

Yes. The RADIUS server supplied with Windows Server 2003 and Windows 2000 Server, known as the Internet Authentication Service (IAS), is available as an optional networking component installed from Add/Remove Programs in Control Panel. Windows Server 2003 IAS also provides RADIUS proxy functionality. For fast answers to common questions, see Internet Authentication Service Frequently Asked Questions. For more information about IAS in Windows Server 2003, see the Internet Authentication Service page. For more information about IAS in Windows 2000 Server, see the Internet Authentication Service for Windows 2000 Server page.

6Q. Does Windows Server 2003 or Windows 2000 Server include a Domain Name System (DNS) server?

Yes. The DNS server supplied with Windows Server 2003 or Windows 2000 Server is available as an optional networking component installed from Add/Remove Programs in Control Panel. For more information about DNS in Windows 2000 and Windows Server 2003, see the Domain Name System (DNS) Center page.

7Q. Does Windows Server 2003 or Windows 2000 Server include a Dynamic Host Configuration Protocol (DHCP) server?

Yes. The DHCP server supplied with Windows Server 2003 and Windows 2000 Server is available as an optional networking component installed from Add/Remove Programs in Control Panel. For quick answers to commonly asked questions, see Dynamic Host Configuration Protocol: Frequently Asked Questions. For more information about DHCP in Windows Server 2003 and Windows 2000, see the Dynamic Host Configuration Protocol.

8Q. Does Windows Server 2003 or Windows 2000 Server include a Windows Internet Name Service (WINS) server?

Yes. The WINS server supplied with Windows Server 2003 or Windows 2000 Server is available as an optional networking component installed from Add/Remove Programs in Control Panel. For more information about WINS in Windows 2000, see the Windows 2000 Server Windows Internet Naming Service (WINS) Overview.

9Q. Where can I get more information about networking and communications support in Windows Server 2003 and Windows 2000?

For Windows Server 2003, see Networking and Access Technologies. For Windows 2000, see Windows 2000 Communications and Networking Services and How it Works in Windows 2000.

10Q. What support does Windows provide for small office/home office (SOHO) networking?

Windows XP includes extensive built-in support for SOHO networks with features that allow you to easily configure a wired or wireless network, share files and printers, and connect your computer or SOHO network to the Internet. For more information, see the Home and Small Office Networking with Windows XP page.

11Q. Where can I get information on “diskless booting”?

“Diskless booting” means that the FreeBSD box is booted over a network, and reads the necessary files from a server instead of its hard disk. For full details, please read the Handbook entry on diskless booting

12Q. Can a FreeBSD box be used as a dedicated network router?

Yes. Please see the Handbook entry on advanced networking, specifically the section on routing and gateways.

13Q. Can I connect my Windows® box to the Internet via FreeBSD?

Typically, people who ask this question have two PCs at home, one with FreeBSD and one with some version of Windows the idea is to use the FreeBSD box to connect to the Internet and then be able to access the Internet from the Windows box through the FreeBSD box. This is really just a special case of the previous question and works perfectly well.
If you are using dialup to connect to the Internet user-mode ppp(8) contains a -nat option. If you run ppp(8) with the -nat option, set gateway_enable to YES in /etc/rc.conf, and configure your Windows machine correctly, this should work fine. For more information, please see the ppp(8) manual page or the Handbook entry on user PPP.
If you are using kernel-mode PPP or have an Ethernet connection to the Internet, you need to use natd(8). Please look at the natd section of the Handbook for a tutorial.

14Q. Does FreeBSD support SLIP and PPP?

Yes. See the manual pages for slattach(8), sliplogin(8), ppp(8), and pppd(8). ppp(8) and pppd(8) provide support for both incoming and outgoing connections, while sliplogin(8) deals exclusively with incoming connections, and slattach(8) deals exclusively with outgoing connections.
For more information on how to use these, please see the Handbook chapter on PPP and SLIP.
If you only have access to the Internet through a “shell account”, you may want to have a look at the net/slirp package. It can provide you with (limited) access to services such as ftp and http direct from your local machine.

15Q. Does FreeBSD support NAT or Masquerading?

Yes. If you want to use NAT over a user PPP connection, please see the Handbook entry on user PPP. If you want to use NAT over some other sort of network connection, please look at the natd section of the Handbook.