Speaker: Jeremy Charles

Imagine that an employee's workstation at your company needs to communicate with a server on another company's network. The server is sensitive and is not exposed to the Internet. The traffic must be encrypted as it passes between your site and the remote site. Your employee must simultaneously access the remote server along with various resources on your own corporate network and the Internet. This has an obvious solution, right?

Sorry, I forgot to mention that the remote server has the same IP address as your employee's workstation. The remote site is unable to NAT the server or change its address. The application that your employee needs to use doesn't understand the concept of "log in to this other server, and then SSH to the real target." Do you have a different solution in mind now?

By the way, you actually have over 2000 employees who need this sort of connectivity to over 3600 servers at various remote sites. They are not techies, so forget about having them port forward their way in. Now what do you do?

6:30 PM - Free pizza, soda, and coffee provided by TDS Telecom.

7:00 PM - Presentation and/or discussion