VPN - Bypass local addresses?

[jamesie]

Hi,

 

The VPN I think is very good in many respects but when connected I am unable to access local addresses i.e router config page (192.168.50.1 / asusrouter.com, printer server 192.168.0.205, tplinkwifi.net / 192.168.0.1). Printing also only works when adding the printer driver/software/proprietary manufacturers software to split tunnel. Using Windows printer driver you have no chance.

 

Adding to ignored websites does not work and if I enter said IP (192.168.0.1) it resorts to 0.0.0.1??? Only way to connect to local is to disconnect the VPN.

 

 

Is there any other way to bypass local addresses? This should be an option surely.

[Flood and Flood's wife]

Hello @jamesie, 

Welcome back!  

Good topic & so was (your) fix for @SknarfCannot print to Wi-Fi connected printer while Kaspersky Plus is running?

IF Kaspersky team engage here (which we hope they do), they may suggest logging it with support - the options & process are as follows: 

1. On the support page, fill in an Email or Chat, then select Feedback, I have a Suggestion, or Feedback, I have a Complaint template - provide a detailed history & explanation/reasons for the request. Support may communicate with you & discuss the proposal. 

• All requests go thru the relevant team/s, not all requests are successful & even successful requests may take a long time (can be years?) to be implemented. 

Thank you?
Flood?+?

[jamesie]

Thanks @Flood and Flood's wifewill do.

Cheers

[jamesie]

[Igor Kurzin]

Hi @jamesie, 

We are aware of this situation with access to local resources, improvements are expected in future versions of VPN.

[Jeep16]

Hi @Igor Kurzin.

I am having this issue and would like to know if it has been resolved.

I have tried to submit this issue to support a few times.
When the VPN is connected, I cannot print. I have added the local network as trusted and allowed the ports per Kaspersky's instructions.
If I disconnect the VPN, printing works.
Also the IP of the printer (or other local devices) in the browser only works if I disconnect the VPN.
Is there a solution? Is there a log that will show what is happening?

[Flood and Flood's wife]

On 5/7/2025 at 2:27 AM, Jeep16 said:

Hi @Igor Kurzin.

I am having this issue and would like to know if it has been resolved.

I have tried to submit this issue to support a few times.
When the VPN is connected, I cannot print. I have added the local network as trusted and allowed the ports per Kaspersky's instructions.
If I disconnect the VPN, printing works.
Also the IP of the printer (or other local devices) in the browser only works if I disconnect the VPN.
Is there a solution? Is there a log that will show what is happening?

Hello @Jeep16, 

Welcome!

1. Please post one or more of the Incident request numbers that have been generated for the submissions? 
2. Has the printer been added to: %SystemRoot%\system32\drivers\etc\host file.

Thank you🙏
Flood🐳+🐋

[Jeep16]

I have never received a reply or incident request, but have gone through the support submission; maybe I am missing something? I just submitted again but no auto response.

I have not added the printer to the hosts file. I am using the IP so I don't think it would matter?

 

[Flood and Flood's wife]

1 hour ago, Jeep16 said:

I have never received a reply or incident request, but have gone through the support submission; maybe I am missing something? I just submitted again but no auto response.

I have not added the printer to the hosts file. I am using the IP so I don't think it would matter?

Hello @Jeep16, 

Thank you for the information!

• IF there's been no incident-request-number(s) generated & OR received via email, then the logging of incident-requests has not worked. The  incident-request-number is generated when the request is submitted - it will show on (your) computer-screen - second image. 
• Go to: https://support.kaspersky.com/b2c/global#contacts - select Email - fill in the template - with detailed history /  information; the *completed* template should look like the first image; answer the ReCaptcha & the acknowledge the Privacy statement, then select Submit
  Spoiler

  

  

   

   

• As far as we understand printer-name & OR IP can be used & this is the instruction: 

  "If user add printer address to the hosts file, OS will determine proper IP address without querying local DNS server that is blocked while VPN is on."

• Try *both* - one may work? 

1. Which region are (you) in? 

Thank you🙏
Flood🐳+🐋

Edited May 21, 2025 by Flood and Flood's wife
the *completed* template should look like the first image

[Jeep16]

Thank you for your response.

I have been able to submit a support issue in the past.  I tried it again today to capture the screen after I click submit:

I am in Canada.

Adding the IP and a name to the hosts file did not resolve the issue.

[Flood and Flood's wife]

13 hours ago, Jeep16 said:

Thank you for your response.

I have been able to submit a support issue in the past.  I tried it again today to capture the screen after I click submit: I am in Canada.

Adding the IP and a name to the hosts file did not resolve the issue.

Hello @Jeep16, 

Thank you for your response, so no support requests have been submitted for "VPN - Bypass local addresses?" issue. 

• Do not use the US support link, due to the *US Government ban* Kaspersky no longer has a US based customer-service-desk or any operations out of the US, read: Guide on Kaspersky software availability in the United States,

1. -> use the GLOBAL support link we provided in our first reply: https://support.kaspersky.com/b2c/global#contacts & select Email. 
2. Please post back the Incident reference number? 

Thank you🙏
Flood🐳+🐋

Edited May 22, 2025 by Flood and Flood's wife
-> use the GLOBAL support link we provided in our first reply: https://support.kaspersky.com/b2c/global#contacts & select Email; Please post back the Incident reference number? 

[Jeep16]

Thanks - I was able to submit this way (I was using the VPN to the US).

Your incident number is: INC000017551421 

[Jeep16]

This is the reply I got from support:

Quote

Please be aware that when the VPN is active, it creates a separate network, which typically makes local devices like printers inaccessible via your usual local network address (192.168...). This is standard behavior for most VPNs.

A simple solution for printing is to temporarily disable the VPN while you need to print.

But I have to disagree - this is not how 'most VPNs' work; it might be how Kaspersky's VPN works. This is unfortunate; I had hoped, from Igor's comments above, that the issue was resolved.

I believe this is still an issue that should be resolved by Kaspersky.

[Flood and Flood's wife]

1 hour ago, Jeep16 said:

This is the reply I got from support:

But I have to disagree - this is not how 'most VPNs' work; it might be how Kaspersky's VPN works. This is unfortunate; I had hoped, from Igor's comments above, that the issue was resolved.

4. I believe this is still an issue that should be resolved by Kaspersky.

Hello @Jeep16, 

Thank you for the update!

• We're think there may be some concern about data-leakage. 

1. Have support explained why the split-tunnel / using the hosts file & the prt-ip - is *not* working? 
2. Have other VPN solutions *actually* been tested, please provide results?
3. How is the printer connected to the computer?  

Thank you🙏
Flood🐳+🐋

Edited May 23, 2025 by Flood and Flood's wife
Have support explained why the split-tunnel / using the hosts file & the prt-ip - is *not* working? 

[Jeep16]

I got a further reply that:

Quote

We've just received a reply from our Escalation Team with the latest update.

The printer should be available when accessed by IP.

Please collect data for analysis

I sent wireshark and VPN logs that are now with the developers.

BTW the printer is on my local, wired network with my computer.

[Jeep16]

FYI - still working with developers, but we did find that my issue is related to the fact that I have spilt tunneling enabled.

[Jeep16]

Almost a year later, so I asked for an update: "Regarding the issue with Split Tunneling, this is still being analyzed by our technical team. We will update your incident as soon as we have more information."