Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Faster Than a Speeding VPN--Super Remote Access With Neoteris IVE: Page 3 of 4

Instant Virtual Extranet Partner-Access 1000 2.1, starts at $29,995. Neoteris, (650) 605-4800.
www.neoteris.com

SSH and telnet are Webified, too. Enter a host name, and a black-and-white terminal pops up that lets you remotely connect to machines without requiring SSH to be opened to the world on the firewall. These sessions are proxied by the IVE and encapsulated in the SSL session. You cannot copy or paste text in the terminal, nor change the font size or color of text.

Your Own Apps

Although the ability to access Webified services is useful, organizations typically deploy VPNs in to use custom applications. The IVE lets you use your own applications for e-mail and most TCP-socket-based programs. In fact, for e-mail the IVE acts as a mail server. If you have an SSL-capable mail client, you can set your e-mail program to use the IVE as the SMTP server; it also supports SSL-encrypted POP and IMAP mail. You don't have to log into the IVE to use e-mail proxying. The IVE retrieves the mail or forwards it to the back-end servers. I configured my Mac Mail program to use IMAP, pointed it to the IVE and was able to send and retrieve mail through the IVE to an Exchange server behind the firewall. The IVE also supports Lotus Notes and Exchange MAPI messages.

Neoteris claims that almost any TCP program can work with the IVE, but it does not support UDP (User Datagram Protocol) or DNS tunneling. Users can't create listening ports on the fly, so the forwarded ports and addresses must be preconfigured by the administrator.

Port-forwarding works similar to SSH tunneling. To connect with the Microsoft Terminal Services client, I set up a configuration in the IVE to forward traffic on Port 3389 (the default Terminal Services port) to my Windows 2000 box. I then logged into the IVE on my remote client machine. A Java applet loaded and set up a few listening ports on the client machine. Then I told the Terminal Services client to connect to 127.0.0.1 on Port t 3389. Traffic was forwarded automatically, and I was connected to the Windows 2000 box. This worked flawlessly. I then set up port-forwarding to two different computers. Because Terminal Services ran on the same port on each machine, the IVE automatically selected an alternate local open port on the client.