Remote Connectivity

1
Remote Connectivity

• Local vs Remote
• Links
• Protocols
• Tips

2
Local vs Remote

• Centralized information and functions
• LAN dedicated connection
• Static and localized
• Connection via a variable connection
• Remote client connecting with server
• Remote from the LAN
• Phone lines or other

3
Links

• PSTN (POTS)
• V.x Standards
• ISDN
• ADSL
• Cable

4
Public Switched Telephone System

• Telephony
• Digital - Analog Digital
• CPU/rj11/modem PSTN Modem/rj11/CPU
• CPS vs Baud vs bits per second vs bits per baud
• V.x standards (CCITT)
• V.22 1200 bps
• V.22bis 2400 bps
• V.32 9600 bps
• V.32bis 14400 bps
• V.34 28800 bps
• V.90 57600 bps
• V.42 Error Checking
• V.42bis Data Compression
• MNP5 Error Checking Data Compression

5
ISDN

• Digital Network except for local loops
• ISDN service to home about 3 miles of central
  office
• Bearer channels 64K each voice data
• Data channel setup info
• BRI 2BD 128K throughput
• PRI 24BD 1.544 throughput (T1)
• NIC/rj45/network

6
Asymmetric Digital Subscriber Line

• Download speed gt upload
• ISP compatibility with DSL
• NIC/rj45/ADSL modem/rj11/Network
• Speeds close to 10BaseT

7
Cable

• Neighborhood bandwidth 10 28 Mbps
• Divided by of simultaneous users.
• Cpu/NIC/rj45/cablemodem/coax

8
Protocols (data-link) for PSTN

• SLIP (serial line interface protocol)
• First modem / Internet interface
• Only IP with static IP address
• DNU
• PPP (point to point protocol)
• IPX Netbeui support
• DHCP
• UTO
• PPTP (point to point tunneling protocol)
• Can also be used without PSTN IP tunneling
• Remote login to LAN server
• Session encryption

9
Tips

• Remote Access Server (RAS)
• Like front end
• Dial Up Networking (Win)
• Use PPP

10
VPN troubleshooting Windows 2000
Virtual Private Networking.

• If your tunnel clients cannot connect to the
  tunnel server, check for the following potential
  problems
• The VPN ports (PPTP and/or L2TP) are not enabled
  for incoming requests.
• The server is running out of VPN ports.
• The server does not have enough IP addresses to
  hand out to incoming clients. These can come from
  the static pool or DHCP.
• The needed protocols (IPX or NetBEUI) are not
  enabled for incoming tunnels.
• The needed tunneling protocol is not supported.
  If your tunnel server runs only L2TP and the
  clients are using PPTP, the connection will fail.
  
• The properties of the remote access policy are
  preventing clients from connecting. Remember that
  if you use RADIUS authentication, the remote
  access policy must be configured on the IAS
  server.
• The user account privileges are not allowing the
  user to connect (if you are not using the remote
  access policy).
• The clients cannot be authenticated. This occurs
  when the authentication procedure cannot access
  either Active Directory or the RADIUS server.
  Make sure the server(s) are added to the RAS and
  IAS Server security group.
• For a VPN server that is a member server in a
  mixed-mode or native-mode Windows 2000 domain
  configured for Windows 2000 authentication, the
  RAS and IAS Servers security group exists. If the
  group does not exist, you need to create it, set
  the group type to Security, and set the group
  scope to Domain Local.
• The RAS and IAS Servers security group has Read
  permission to the RAS and IAS Servers Access
  object. The computer account of the VPN server
  must be a member of the RAS and IAS Servers
  security group. If you add or remove the VPN
  server computer from the RAS and IAS Servers
  security group, the change does not take effect
  immediately. The fastest way to put the change
  into effect is to restart the VPN server
  computer.
• The Everyone group is added to the Pre-Windows
  2000 Compatible Access group. This needs to be
  verified if the tunnel server is running Windows
  NT 4.0 in a Windows 2000 mixed-mode domain.
• The clients must have a machine certificate to
  establish a tunnel if the clients are using
  L2TP/IPSec for the tunnels.

11
More VPN

• http//searchwin2000.techtarget.com/tip/1,289483,s
  id1_gci549188,00.html
• To configure a VPN server, your computer must
  have at least two interfaces. To setup a Windows
  2000 server for VPNs, use the following
  procedure
• Open Routing and Remote Access console in the
  Administrative Tools folder
• Right-click the server and then click Configure
  and Enable Routing and Remote Access
• The Routing and Remote Access Server Setup wizard
  starts click Next
• Select Virtual private network VPN server, and
  click Next
• Select or add a remote client protocol and click
  Next
• Specify the Internet connection for the server
  and click Next
• Choose a method to assign IP addresses to the
  clients, either automatically or from a specified
  range of addresses, and click Next
• The next screen gives you an option to either
  configure this server to use a RADIUS server or
  skip this step for now
• Click Finish to complete the Routing and Remote
  Access Server Setup wizard."