Why can't I access my Kerio no longer?


So… all of a sudden I cannot access Kerio from the browser at 10.10.1.1, which is how I usually access it.
Hmmm.
Let me check if Kerio is on - indeed it is.
Hold on, it’s got written IP: 192.168.1.1 on the display and normally it is shown IP: 10.10.1.1.
How did that happen?
I did have experts from a renowned AVIT company onboard this afternoon spending majority of time in my office unsupervised with all the critical IT equipment in the unlocked racks pushing firmware update to WLC and playing with VLANs setup in Kerio and core switch but surely it has nothing to do with it…?
Btw, my computer is wired in, wi-fi is off.
First thing that crosses my mind - I think that IP: 192.168.1.1 is shown on a brand new (or factory reset) Kerios so it makes me think, god forbid, it somehow got reset to factory defaults or its config somehow changed.
How to check this if I cannot access Kerio from my computer?
Hmmm...
Luckily, when I joined the boat, I took a note of the Kerio’s port configuration, saw that port 13 was configured for access at 192.168.1.1, wouldn’t you believe it.
I set my laptop to 192.168.1.55, plug it in Kerio’s port 13, enter https://192.168.1.1:4081/admin in the browser and actually got to a login page.
Cool, I’m in.
I check the Advanced Options and see that Administration is accessible at 192.168.1.1 and not at 10.10.1.1 as I was expecting…


Let’s check the config of the only 2 other ports that are connected on Kerio – INTERNET (which is connected to the Peplink router) and port 5 which is connected to the core switch.

So 10.10.1.1 is Kerio’s IP address on port 5, which is connected to the core switch.
Let’s ping 10.10.1.1 from my wired computer. Unsuccessful. Ok.
Let’s do tracert to 10.10.1.1. No success, request timed out.
Now, when times were good, I recorded tracert to 8.8.8.8 (google.com) and this is what it looked like this:


Next day, I pasted what I have just written above to ChatGPT (20eur version, not the free one haha) and asked him to critique my troubleshooting:
What you did well
1. Physically inspected Kerio instead of relying solely on remote troubleshooting.
2. Documented port configurations in advance, which allowed you to access Kerio through port 13.
3. Found an alternative management path when normal access failed.
4. Checked Kerio's interface configuration to verify its actual IP addresses.
5. Used ping and traceroute to investigate connectivity.
6. Compared current traceroute with a known-good baseline rather than interpreting results in isolation.
7. Noticed unusual UK network hops, which eventually led you to suspect the VPN.
8. Tested the VPN hypothesis by disabling it and confirming access was restored.
9. Continued investigating the display mystery even after resolving the main problem.
10. Performed a controlled experiment by disconnecting and reconnecting port 13, establishing a repeatable relationship between link state and displayed IP.
What you did wrong
1. Jumped to the factory-reset hypothesis too early. A displayed IP address alone was insufficient evidence.
2. Anchored on the visiting technicians because they had recently worked on the network, without evidence they caused the issue.
3. Didn't first establish the scope of the failure. Was Kerio inaccessible to everyone or only to your computer?
4. Didn't check your own computer's VPN status early enough. This was a quick, high-value check.
5. Didn't inspect the Windows routing table using route print -4, which could have exposed the VPN routing issue.
6. Interpreted unsuccessful ping and traceroute tests too broadly. They don't necessarily prove the destination is inaccessible.
7. Didn't test the actual service directly using Test-NetConnection 10.10.1.1 -Port 4081.
8. Used the changed internet traceroute as evidence without fully accounting for VPN routing and hidden hops.
9. Initially treated two independent observations as one problem: browser access failure and changing LCD address.
10. Performed more invasive troubleshooting before simpler checks. Directly connecting to the firewall was useful, but checking the workstation first would have been more efficient.
Biggest lessons
- Define the failure precisely before troubleshooting.
- Check the simplest explanations first.
- Separate observations from assumptions.
- Don't confuse correlation with causation.
- Design tests that distinguish competing hypotheses.
- Change one variable at a time.
- Confirm the root cause rather than stopping when things work again.
There you go, some good things and some gaps in my diagnostic abilities. Always something to learn.


So after a default gateway in my 10.10.101.0 network, next hop is Kerio at 10.10.1.1.
Let’s look at current tracert 8.8.8.8.


So my computer can still go online despite not being able to reach Kerio. Ha!
I don’t see any hops for Kerio or Peplink. How is my computer able to go online? Wi-fi is off.
And why is there a .uk in some hops? Is this suggesting a UK IP address?
Hold on, hold on, hold on……………..
Is my VPN on?
Omg.
Of course it is! Routed to UK! Dumbass!
I switched on VPN few hours ago on my computer, forgot to switch it off and voila… I created myself a beautiful little problem…
VPN off and Kerio access confirmed!
But hold on.
There is still an open question of why does the Kerio show IP:192.168.1.1 on its display when I am very certain it normally shows IP:10.10.1.1?
Now I know my memory isn’t great, to say the least, and it is a viable option I somehow imagined 10.10.1.1 when 192.168.1.1 was there all along.
Being happy with having restored access to Kerio, I decided to fight this battle tomorrow morning and then I unplug my laptop from port 13 and… IP on the Kerio display changes to 10.10.1.1! What?
Plug back laptop and it changes to 192.168.1.1!
Damn! I didn’t look for the explanation of this behaviour and was just happy to figure out why I couldn’t access Kerio through my computer and why Kerio’s display changed IP addresses.
Next morning, I thought I bit about his problem again and I thought I should check IP address for the Administration inside Advanced Options tab – remember how it was 192.168.1.1 when I had laptop plugged in. Well, it went back to 10.10.1.1.
So it seems that the IP address for the Administration inside Advanced Options and the IP address on the Kerio display change depending on the interface used to log into Kerio... I guess.
Cool!