|
|
 |
|
Questions
TheGreenBow IPSec VPN Client software
VPN Overview
 |
What is a VPN? |
 |
A virtual private network (VPN) is a way to use a public telecommunication infrastructure,
such as the Internet, to provide remote offices or individual users with secure access to
their organization's network. In the past, companies would have rented expensive systems of leased lines to build
their VPN only they could use. A VPN provides the same capabilities at a much lower cost.
A VPN works by using the Internet while maintaining privacy through security procedures and
tunneling protocols such as the Layer Two Tunneling Protocol (L2TP) or IPSec. In effect, private data,
being encrypted at the sending end and decrypted at the receiving end, is sent through a "tunnel" that
cannot be "entered" by any other data.
|
Why IPSec is strong? |
|
Definition: IPSec (Internet Protocol Security) provides security services at the IP layer
by enabling a system to select required security protocols, determine the algorithm(s)
to use for the service(s), and put in place any cryptographic keys required to provide
the requested services. The IPsec architecture is described in the RFC-2401 (www.ietf.org RFC-2401).
IPSec has been selected to be embedded in IPv6. IPSec is strong because it was designed to be
strong and replace some older methods like PPTP.
Today IPSec is the most secure way to access the corporate network from the Internet, here are some elements why:
- Strong encryption mechanisms like Encapsulated Security Payload (ESP) using DES, 3DES, AES with long key length (i.e. 128, 192, 256)
- Strong authentication of parties identity with the use of X-Auth and Certificate with long key length (i.e 1536, 2048)
- Use of Internet Key Exchange (IKE) and ISAKMP to automatically exchange keys and mutual authentication.
- Protection against denial of service attacks. The IPSec protocols use a sliding window. Packets are numbered and only accepted if they fit the window.
- Use of USB Stick, USB Token in conjunction with IPSec Client software to protect identity/authentication information and VPN configurations (i.e. a TheGreenBow specific feature).
|
What is NAT Traversal and do you support it? |
|
Definition: Network Address Translation (NAT) is designed to decrease IT manager frustration for
scarce public IP addresses. A NAT device takes a packet’s originating private IP address,
translates that address into a public IP address, before sending the packet across the Internet
to its destination. NAT devices use an internal table to keep track of translated addresses but
unfortunately manipulate the packet’s original IP header, impacting IPSec ability to function.
IETF (Internet Engineering Task Force) group worked out a solution called NAT Traversal
(NAT-T RFC-3193). NAT Traversal is now widely implemented in routers and appliances.
TheGreenBow IPSec VPN Client supports NAT-T drafts 1, 2 and 3 (include udp encapsulation).
|
Tunnel versus Transport Modes? |
|
The differences between Transport mode and Tunnel mode can be defined (www.ietf.org RFC-2401) thought
the following network configurations:
- Tunnel Mode is most commonly used whenever either end of a security association is a
security gateway or both ends of a security association are security gateways, the security gateway
acting as a proxy for the hosts behind it. Tunnel mode encrypts both payload and the whole header (UDP/TCP and IP).
- Transport Mode is used where traffic is destined for a security gateway and the security
gateway is acting as a host e.g. SNMP commands. Transport Mode encrypts only the data portion and
leaves the IP header untouched.
TheGreenBow IPSec VPN Client supports both modes.
|
Pre-shared key versus Certificates? |
|
Computer authentication by IPSec is performed by using preshared keys or computer certificates.
A pre-shared key identifies one party during Authentication Phase. Per definition, "Pre-shared"
means you have to share it with another party before you can establish a secure VPN tunnel.
The strongest method of authentication is the use of a PKI and certificates. However, smaller organizations
cannot afford the implementation of a PKI system and a well managed preshared key method can be easier and
just as powerful.
TheGreenBow IPSec VPN Client supports both modes.
|
IPSec versus SSL? |
|
Please see our IPSec versus SSL page where we compare both technologies.
|
Can we use IPSec to secure our WiFi network? |
|
Please see our IPSec versus WiFi page where we look at WEP, 802.11i and we compare technologies.
|
What is DPD? |
|
DPD or "Dead Peer Detection" is an Internet Key Exchange (IKE) extension (i.e. RFC3706)
for detecting a dead IKE peer. This mechanism is used by the Redundant Gateway feature.
TheGreenBow IPSec VPN Client software
 |
To install TheGreenBow IPSec VPN Client on Windows 7:
- Right click on 'TheGreenBow_VPN_Client.exe' before install and select 'Properties'
- In the properties window, select 'Compatibility' tab
- Check 'Run this program in compatibility mode for:' and select 'Windows Vista'
- Click 'Ok'
|
|
Which Windows versions are supported? |
|
- Windows 2000 (Workstation)
- Windows XP 32-bit. WinXP all service packs, including SP2
- Windows Server 2003 32-bit
- Windows Server 2008 32-bit
- Windows Server 2008 64-bit
- Windows Vista 32/64-bit
- Windows 7 32-bit
- Windows 7 64-bit
|
 |
 Releases which support old Windows versions:
|
Which languages are supported? |
|
TheGreenBow IPSec VPN Client is now available in many languages (e.g. English, French, German, Portuguese, Spanish, ...). Check our supported languages list, increasing daily, to find your language.
The language can be selected during software installation of the IPSec VPN Client.
|
How to localize the IPSec VPN Client? |
|
Do you want to have TheGreenBow IPSec VPN Client in your own language? Go to IPSec VPN Client localization, download and translate in your own language the IPSec VPN Client strings file.
The localization process is very simple and the translation in your language will be available on our next release.
|
Which are the compatible Gateways? |
|
TheGreenBow IPSec VPN Client is compatible with all IPSec routers compliant to the existing standards (IKE & IPsec). Check our Certified VPN Products list, increasing daily, to find your VPN gateway.
If the equipment you are looking for is not contained in this list, please contact our tech support and we will work with you to certify it. We will need configuration file, log file from "Console" window and a screenshot of the router configuration page.
|
How to connect the IPSec VPN Client to Linksys VPN router? |
|
We've made available for download VPN Configuration Guides for most of the gateways we support on our web site support section, and there are some on Linksys. VPN Configuration Guides are either written by our partners or by our engineering team.
We do support Linksys RV082 and Linksys BEFVP41. You might want to look at our answer about Linksys WRV54G.
|
How to setup TheGreenBow IPSec VPN Client using Cisco? |
|
We've made available for download VPN Configuration Guides for most of the gateways we support on our web site, and there are some on Cisco. VPN Configuration Guides are either written by our partners or by our engineering team.
We do support Cisco gateways like Cisco PIX501, Cisco ASA 5510, Cisco PIX 506-E, Cisco 871, Cisco 1721.
|
Do you support NAT Traversal? |
|
Yes. We do support NAT Traversal Draft 1 (enhanced), Draft 2 and 3 (full implementation). IP address emulation.
- Including NAT_OA support
- Including NAT keepalive
- Including NAT-T aggressive mode
|
Does TheGreenBow IPSec VPN Client support DNS/WINS discovering? |
|
Yes, the IPSec VPN Client does support le "Mode-Config". "Mode-Config" is an Internet Key Exchange
(IKE) extension that enables the IPSec VPN gateway to provide LAN configuration such as DNS/WINS
server addresses to the remote user's machine (i.e. IPSec VPN Client). In case "Mode-Config" is
not supported by remote gateway, DNS and WINS server IP addresses of the remote LAN can be defined
into the IPsec VPN Client, to help users to resolve intranet addressing.
|
Is TheGreenBow IPSec VPN Client compatible with Linksys WRV54G? |
|
TheGreenBow IPSec VPN Client is fully certified with Linksys WRV54G firmware 2.37 and later. Please download Linksys WRV54G VPN Configuration Guide.
The Linksys WRV54G firmware 2.25.2 does not accept IPSec connexions from any IPSec VPN Clients with dynamic IP addresses. However, there is a workaround. You need to set up IPSec VPN Client's IP address in the Linksys configuration.
Linksys has released a newer firmware since then. You might want to test it: click here
TheGreenBow IPSec VPN Client is fully certified with Linksys RV082 and Linksys BEFVP41 (see also Certified VPN Products list or download VPN Configuration Guides).
|
Which port is needed by TheGreenBow IPSec VPN Client? |
|
UDP port 500 and UDP port 4500 must be open and ESP protocol (protocol number 50) must be allowed.
See also other FAQs:
How to setup VPN connections and VPN ports for users in hotels or hotspots?
Unable to open a VPN tunnel under Vista, problem with Vista Firewall?
Can IKE Port be modified?
|
Is it possible to use TheGreenBow IPSec VPN Client through Microsoft ISA Server 2000 and 2004? |
|
According from Microsoft support, in most cases, IPSec VPN traffic does not pass through ISA Server 2000.
For more details about ISA server 2004, read Q838379 in Microsoft Knowledge Base
|
What must be filled in Phase 2 field "VPN client address"? |
|
This field is the virtual IP address that the IPSec VPN client will have inside the remote subnet. With most of VPN gateways, this address must not belong to the remote network subnet.
For example, if you use a VPN gateway with a subnet 192.168.0.0/255.255.255.0, you should use in "VPN Client address" a value like 192.168.100.1 or 10.10.10.1.
Take the case you choose an IP address non-used in the subnet like 192.168.0.200. When the IPSec VPN Client is sending a TCP or an UDP packet to a target remote computer 192.168.0.x, this target will send inside its subnet an ARP request in order to get IPSec VPN Client MAC address and reply directly to it. But, this request cannot receive any answer because the client is not physically present inside the subnet. So, initial packets from the client will not be answered.
If your VPN gateway can answer this ARP request for the IPSec VPN Client, you can fill "VPN Client address" field with an IP address belonging to remote subnet.
You might want to download our IPSec VPN Client User Guide.
|
Is it possible to hide the graphical user interface i.e. "silent" mode? |
|
It is possible to run the standard IPSec VPN Client setup in "silent" mode. You need to download
the whole procedure described is this document: VPN Deployment Guide
|
Is TheGreenBow IPSec VPN Client compatible with Linksys WRVS4400N or WRV200? |
|
Yes, TheGreenBow IPSec VPN Client is fully certified with Cisco Linksys WRVS4400N, Cisco Linksys WRV200 as well as Cisco Linksys RV082 and BEFVP41
(see also Certified VPN Gateway list or download VPN Configuration Guides).
|
Can a Redundant Gateway be defined? |
|
Yes. It is possible to define a Redundant Gateway in the IPSec VPN Client. Redundant Gateway can offer
to remote users a highly reliable secure connection to the corporate network. The Redundant Gateway
feature allows TheGreenBow IPSec VPN Client to open an IPSec tunnel with an alternate gateway in case
the primary gateway is down or not responding. Remote gateway failure is detected by "Dead Peer
Detection" function.
|
Can IKE Port be modified? |
|
Yes. A specific IKE Port can be set. To do so, go to global 'Parameters' in the Configuration Panel and enter the right port into the 'IKE Port' field and 'NAT-T port' fields.
See also other FAQs:
How to setup VPN connections and VPN ports for users in hotels or hotspots?
Unable to open a VPN tunnel under Vista, problem with Vista Firewall?
|
What are TgbStarter.exe and TgbIke.exe? |
|
TgbStarter.exe and TgbIke.exe are components of TheGreenBow IPSec VPN Client.
- TgbStarter.exe is the software daemon component (ran as a service)
- TgbIke.exe is the IPSec/IKE run-time of the software.
|
The Software Activation doesn't succeed. |
|
When I try to activate the software, it doesn't succeed (I got an error message).
You can find a complete help guide about the activation on our Online Software Activation Help Guide.
You can also get your software activated at anytime, by following the procedure described on our Manual Software activation.
|
What is the VPN Configuration for test? |
|
A test (or demo) VPN Configuration is VPN configuration designed by TheGreenBow Techsupport team to connect
to our online IPSec VPN gateways and servers. Those are always live and you can use it to test your
network environement at any time. The test VPN Configuration is embedded into the IPSec VPN Client.
Check out online help or download the test VPN Configuration file below.
|
Can I get temporary license numbers that I can use during my tests? |
|
Yes, license can last several weeks. For further details, contact our sales department.
|
|
How to launch my CRM app automatically when IPSec tunnel to my corporate intranet opens? |
|
It is possible. Go to Configuration Panel>Phase2 and click on scripts. In the Script window,
you can select the application you want to start before or after a tunnel opens or closes.
|
|
Does IPSec VPN Client Software support two-way authentication keys and Tokens? |
|
Yes. TheGreenBow supports several two-factor and two-way authentication Tokens to store users, personal credentials, such as private keys, passwords and digital certificates. Please see the Certified Token List.
|
How to connect to a remote Windows Domain by using the 'Enable before Windows logon' feature? |
|
To make it work, please proceed through the following steps:
- Go to 'P2 advanced', select 'Enable before Windows logon'. Then click 'Ok' and 'Save&Apply'.
- Next time, you are on the logon windows, a tiny windows will appear and will allow you to open this VPN tunnel. Several VPN Connections can be established before Windows logon.
Now, please be aware that, due to the specificity of this functionality, it can only work with an IPSec VPN Client software that
has been already activated. As long as the IPSec VPN Client software remains in trial mode, it will start only after the user
clicked on 'Evaluate', and thus, after Windows logon of course. As a consequence, this is the only feature which cannot be tested
with a demo version.
|
|
How to setup VPN connections and VPN ports for users in hotels or hotspots? |
|
For more information on the negotiation of NAT Traversal in IKE see IETF RFC 3948 (UDP Encapsulation of IPsec Packets), IETF RFC 3947 (Negotiation of NAT-Traversal in the IKE) or draft "draft-ietf-ipsec-nat-t-ike-08". Also see the TCP and UDP ports list.
Here are the negotiation Phases in VPN connection and their default VPN Ports when TheGreenBow IPSec VPN Client software is behind any router:
| Phase |
Default Port |
Where to modify the ports? |
| Phase1 negotiation |
UDP Port 500 |
Go to 'Config Panel'
> 'Parameters'
> 'IKE Port' |
|
| Phase2 negotiation |
UDP Port 4500 |
Go to 'Config Panel'
> 'Parameters'
> 'NAT-T Port' |
| Traffic after IPSec/IKE negotiation |
Stays on last port defined |
|
In some hotels, hotspots or airports, the UDP port 500 and 4500 for outgoing traffic might be prohibited, preventing any outgoing VPN Connections to your corporate network. So it is necessary to configure IKE and NAT-T ports accordingly.
Here is an example of alternative VPN Port in Configuration Panel (i.e. remember this only affects UDP protocol):
| IKE Port |
NAT-T Port |
| 80 |
443 |
If you decide to use non default VPN Ports (i.e. UDP 500 & UDP 4500), the destination router (i.e. at the edge of your corporate network) must be configured to reroute the incoming traffic associated with the new selected VPN ports onto the default UDP 500 & UDP 4500 so that they properly routed to the IPSec service. Here is the diagram for example above, knowing that some router models do not provide the capability to reroute ports within itself and two routers might be needed:
Here is a Linux Firewall configuration file when your VPN router does not provide the capability to reroute ports within itself and you want to add a front-end firewall:
|
|
Is it possible to use Certificates from the Windows Certificate Store where our PKI software put user Certificates? |
|
Yes. When setting up a new VPN Tunnel,
- Go to 'Phase1' > 'Certificate Management...'
- All Certificates in the Windows Certificate Store (Personal Store) should appear here.
- Select the Certificate you need, click 'Ok', click 'Save & Apply'.
You might want to download our IPSec VPN Client software User Guide.
|
|
Is SHA-2 supported? Which Hash Algorithms are supported? |
|
Yes. SHA-1 and SHA-2 254-bit are supported. MD5 is also supported. See full list in the datasheet.
|
|
How to see VPN Connections? |
|
There are several ways to see opened VPN connections:
- Right click on the VPN Client software systray icon. Green lights mean VPN tunnels are open.
- Single click on the VPN Client software systray icon to open Configuration Panel. Tap Ctrl+Enter to go to Connection Panel, back and forth.
- Once the Configuration Panel pops up, click on 'Connections' button.
|
|
How to force all internet traffic in VPN tunnel? |
|
It is possible to force all internet traffic in VPN tunnel. Doing so, all internet traffic is routed from the remote gateway instead of the remote user network, the remote user network IP address is virtually hidden to visited websites as it is replaced with remote gateway IP address. Corporate network may apply some additional traffic scan to increase security.
The VPN Configuration is simple and requires 3 steps:
- Go to 'Configuration Panel' > 'Parameters' > select 'Block non-ciphered connection' to prohibit non-ciphered traffic from being routed to internet directly.
- Go to 'Configuration Panel' > 'Phase2' > select 'Subnet Address' as 'Address Type' and set both 'Remote LAN' and 'Subet Mask' to '0.0.0.0', so that all traffic (to any IP address) will be routed to VPN tunnel. Note that '0.0.0.0' means all traffic including traffic to your local network will be routed through the VPN tunnel.
- On the remote gateway, set the VPN tunnel in the same way as both configuration must be symetrical with local subnet de 0.0.0.0/0.
Note: Some VPN Gateway/Routers may not support this feature (i.e. hub&spoke: '0.0.0.0/0'). If supported, you'll need to create a rule to authorize wan to wan traffic.
Troubleshootings
|
"I have message XXXXX in the console". What does it mean? |
|
We do make available for download a complete guide of messages from TheGreenBow IPSec VPN Client console with explanations and resolving hints. If this document does not help you, send us all the exchanges with RECV and SEND lines. Keep log levels to "0" and click on "Save file".
Log file can be found in C:\Program Files\TheGreenBow\TheGreenBow VPN.
|
No response from the VPN server |
|
If you have the following logs, that means the remote VPN server does not answer to client’s IKE requests.
115317 Default (SA Cnx-P1) SEND phase 1 Main Mode [SA][VID]
115319 Default (SA Cnx-P1) SEND phase 1 Main Mode [SA][VID]
115321 Default (SA Cnx-P1) SEND phase 1 Main Mode [SA][VID]
115323 Default (SA Cnx-P1) SEND phase 1 Main Mode [SA][VID]
Take a look at remote VPN server logs and check if requests from the client are received. If you find no trace, IKE requests must have been dropped somewhere. Check any firewall (including computer Personal Firewall) that can be found between the IPSec VPN client and the VPN server.
|
VPN is up but I can't ping? |
|
When logs look like the ones below, the IPSec VPN tunnel is established. Now you should be able to ping any devices onto your VPN server LAN. TheGreenBow IPSec VPN Client configuration is correct.
121902 Default (SA Cnx-Cnx-P2) SEND phase 2 Quick Mode [SA][KEY][ID][HASH][NONCE]
121905 Default (SA Cnx-Cnx-P2) RECV phase 2 Quick Mode [SA][KEY][ID][HASH][NONCE]
121905 Default (SA Cnx-Cnx-P2) SEND phase 2 Quick Mode [HASH]
If you still cannot ping the remote LAN, here are a few guidelines:
- Check Phase 2 settings : VPN client address and Remote LAN address. Usually, client IP address should not belong to the remote LAN subnet (read also What must be filled in Phase 2 field "VPN client address" ?)
- Once tunnel is up, packets are sent with ESP protocol. This protocol can be blocked by firewall. Check that every device between the client and the VPN server does accept ESP
- Check your VPN server logs. Packets can be dropped by one of its firewall rules.
- Check your ISP support ESP
- If you still cannot ping, follow ICMP traffic on VPN server LAN interface and on LAN computer interface (with Ethereal for example). You will have an indication that encryption works.
- Check the “default gateway” value in VPN Server LAN. A target on your remote LAN can receive pings but does not answer because there is not “Default gateway” settings.
- You cannot access to the computers in the LAN by their name. You must have specified their IP address inside the LAN.
For full trace with explanations and resolving hints, please see our Troubleshooting document.
|
DELL or HP laptops with Broadcom Chipset |
|
TheGreenBow recommends customers using a Broadcom chipset integrated with some Dell or HP laptops to
update driver bcmwl5.sys to the most recent release. This driver causes blue screen intermittently even
if our IPSec VPN client is not installed.
|
Intel Adapter Switching Utility |
|
Intel Adapter Switching Utility causes blue screen when TheGreenBow IPSec VPN Client is installed.
If you have an Intel Pro/Wireless 2100 or 2200, follow these steps in the given order.
- Go to the Start/Control Panel/Add\Remove Programs. Remove the Intel PROset item
- Go to the Start/Control Panel/System.
- Select the hardware tab and press the device manager button.
- In the device manager, click on the plus sign to expand the Network Adapters item.
- Select Intel PRO/Wireless LAN 2200 (or 2100) adapter and right click.
- Select Uninstall from the pop-up menu.
- Restart the computer.
Upon reboot the laptop will re-detect the wireless card and install the drivers for it. It will not
install the Intel PROset drivers. The wireless card should still function, but the added functionality
of the adapter switching will not be available. Windows will then manage the wireless profiles instead
of the Intel PROset utilities.
For more details, see the Intel technical advisory
|
I cannot uninstall IPSec VPN Client software |
|
Problem: I cannot uninstall IPSec VPN Client software, it always asks to first uninstall the previous version.
Solution: You can use our tool
to clean the remaining components of IPSec VPN Client software.
|
How reporting bug when IKE Daemon crashes? |
|
You can follow the process given in this page: Reporting Bugs.
|
Issues with TheGreenBow drivers on Windows Vista |
|
We strongly recommend users on Windows Vista to upgrade their network adapter drivers with Windows Update. This action can prevent
from driver crashes in some network configurations. Also, Windows Vista bug fix pack KB938194 should be installed. More details and
download are available on http://support.microsoft.com/?kbid=938194.
|
Unable to open a VPN tunnel under Vista, problem with Vista Firewall? |
|
Once TheGreenBow VPN Client installed on Vista, it might be impossible to open a VPN tunnel. The opening of the VPN tunnel remains
blocked with the following IPSec messages (use the IPSec VPN Client console):
115317 Default (SA Cnx-P1) SEND phase 1 Main Mode [SA][VID]
115319 Default (SA Cnx-P1) SEND phase 1 Main Mode [SA][VID]
This can happen on Windows Vista because the Vista Firewall can forbid IPSec communications.
TheGreenBow VPN IPSec 4.2 (and further): The software automatically creates new rules into the Windows Vista Firewall during software installation so that IPSec VPN traffic is enabled (see "windows firewall" in the User Guide).
Note: In Windows Seven (Wind 7), your profile 'Private' and 'Domain' in existing Windows Firewall rules for TheGreenBow VPN Client might not be set accordingly. Please check in Windows Firewall rules and make sure your profile 'Private' and 'Domain' are selected (see step 6 below).
TheGreenBow VPN IPSec 4.1: To allow IPSec communications (or verify that they are authorized or restricted), please proceed as follows:
- Step 1: Go to 'Windows Start' button and enter "Windows Firewall with Advanced Security" in Search field. Alternatively, enter 'cmd' and in the command line window enter 'wf'.
|
|
Open "Windows Firewall with Advanced Security".
|
- Step 2: Select in the left menu "Inbound Rules", then in the right column "New Rule...".
|
|
Select in the left menu "Inbound Rules", then in the right column "New Rule...".
|
- Step 3: Select "Port" and then click on "Next".
|
|
Select "Port" and then click on "Next".
|
- Step 4: Select "UDP" and the "Specific local ports," then enter two values 500 and 4500 separated by comma (i.e. "500,4500").
Click on "Next".
|
|
Select "UDP" and the "Specific local ports," then enter two values 500 and 4500 separated by comma (i.e. "500,4500").
Click on "Next".
|
- Step 5: Verify that "Allow the connection" bullet is selected.
Click on "Next".
|
|
Verify that "Allow the connection" bullet is selected. Click on "Next".
|
- Step 6: Make sure this rule applies to all Profiles. Click on "Next".
|
|
Make sure this rule applies to all Profiles. Click on "Next".
|
- Step 7: Assign a name to this new rule. Click on "Finish".
|
|
Assign a name to this new rule. Click on "Finish".
|
- Step 8: The new rule is created.
|
|
|
- Step 9: Select in the left column "Outbound Rules" and in the right column "New Rule...", and configure exactly the same rule (i.e. UDP ports 500 and 4500, VPN Outbound).
|
|
Select in the left column "Outbound Rules" and in the right column "New Rule...", and configure exactly the same rule (i.e. UDP ports 500 and 4500, VPN Outbound).
|
|
There are several ways to see opened VPN connections:
