Wondered if anybody has ever managed to get an X-Kryptor VPN encryption
device working before? Can't find any information on the net about
this device, except a few reviews that briefly mention its name.
It comes with extremely poor documentation that is almost completely
useless. As a test I'm trying to setup a very basic network just to try
and get something working.
I am doing the following:
LAN A interface configured with IP 192.168.0.10
LAN B interface configured with IP 192.168.0.10
Laptop connected directed to LAN B interface using a cross-over cable
and configured with IP address 192.168.0.5 and default gateway
LAN A interface on the X-Kryptor is connected to a network on the
192.168.0.x range comprising WinNT domain controller, WINS server, DNS
According to X-Kryptor documentation it is fine to have the same IP
address on both interfaces as the device is not a router of any kind.
Also because apparently anything that goes in one interface on the
X-Kryptor just gets encrypted or decrypted and sent out the other
We have configured the client software with a range of
220.127.116.11-254.254.254.254 and specified that traffic to these
destinations gets routed to the X-Kryptor (192.168.0.10). Apparently by
specifying this entire range the client is effectively in 'Full
Lock-down' mode. This should that any request from the laptop is sent
to the X-Kryptor.
I can successfully make a connection to the Web Administration page on
the X-Kryptor via it's LAN B interface. The X-Kryptor shows this secure
connection exists on the the LCD display on the front of the device.
So the problem: Nothing else works! Can't connect, ping or get any
response from anything the other side of the X-Kryptor box. All things
that the X-Kryptor representatives said you should be able to do.
Has anybody even heard of the device before? There are very few
references to it on the Internet at all, and the ones I found are
people suggesting use of the box. But none of them have actually used
The first question i have to ask is have you injected the firmware and client with any key material ?
You wont be able to connect via LANB to LANA unless both the XK Firmware (I take it your using an XK 25 or 100?) and the client software is injected with key material. Also, you wont be able to connect to anything from LANA to LANB i.e connect to the internet. These devices normally act in a "Back to Back" configuration to secure access IN TO your private LAN. All traffic is encrypted from lan B outgoing.
Concering the Lockdown of the client, you specified that your "LOW" range is 18.104.22.168 and your "HIGH" range is 254.254.254.254. To be in complete lockdown mode you would specify the following ranges for LOW and HIGH:-
Low = 0.0.0.1
High = 255.255.255.254
You then need to specify a gateway (This is usually the Public/NAT'd address of the XK)
If you have more than one Xkryptor you can specify diffrent lan ranges to go to multiple XK gateways.
You have a public xk address of 22.214.171.124 (purely for example purposes) and you have private LAN behind this of 192.168.10/24,
you also have another site , say for DR. The Private lan you use at this site = 192.168.30/24 with a public XK address of 126.96.36.199
you need to configure the client as follows:
LOW = 192.168.10.1
HIGH = 192.168.10.254
Gateway = 188.8.131.52
LOW = 192.168.30.1
HIGH = 192.168.30.254
Gateway = 184.108.40.206
You can see if the tunnels have been created by going into the diagnostics page of the XK gateway device
January 18, 2009 6:41:53 PM
Q) Has anyone ever got one working yet? A) Somewhere in the region of 750,000 people are working via X-K. However, it is not meant to be installed by users. It is a task for specialist technicians from the X-K support team. The Technical Admin Course is a 2 day course alone. Even this is not meant to prepare the layman for the myriad of network variations into which the systems can be linked to. Contact BMTL on 01462 482333 and they will get you up and running!