Jump to content

Does Immunet Free Block The Vpn Connections?


Recommended Posts

Dear Support!

 

I used Windows2003 server. Someone suggested the immunet because it's working in this kind of OS.

I installed it then, it was ok.

 

Today I tried to use my existing Windows VPN connection to access resources.

But the connection failed (error 800).

 

After I uninstalled Immunet and restarted the server, the VPN worked well.

 

Then I installed Immunet again, restarted the server, and VPN isn't working again.

 

Can I disable the VPN blocking somehow in Immunet Free?

 

Thanks for your any help!

 

Regards: dd

Link to comment
Share on other sites

Hi dd,

 

I have seen VPN issues with a specific client before, can you tell me what VPN client you are using?

 

-Jose

 

I'm talking about the default Windows VPN (PPTP) connection.

 

 

 

ritchie58 said:

======================================================================

Hi dd, I moved your topic from the General section to the Support (Issues/Defects)section as that's a better place for it in relation to the stated topic. Plus a Support person is more likely to read it in this section.

 

Have you tried to turn off "Monitor Network Connections" in Settings to see if that helps your VPN issue?

 

 

I didn't find any option in the free version.

 

Where I can find it?

Link to comment
Share on other sites

Hi dd, to see if this setting is causing the problems click on the Immunet System Tray icon to launch the GUI. Then click on the Settings tab on the right hand side of the GUI under Product. Monitor Network Connections is the last setting under the General Settings tab. Try turning that off to see if that corrects the issue. I think it's worth a try if this setting exists (see below).

 

If you're using a version other than the English language version you may be using an older build that still supports your native language but does not have this setting as it's a fairly recent addition to Immunet. To find out what version you currently have you can mouse over "About" in the lower right hand side of the GUI. That will tell you with a little pop up window. I'm currently using the 3.0.13.9411 version which I believe is the newest build. Since translations for newer builds has been woefully lacking for some reason it's always best to use the English Language version when ever possible. That way you get the latest build with all the newest additions & bug fixes included.

 

Best wishes, Ritchie...

Link to comment
Share on other sites

Dear Ritchie!

 

 

Hi dd, to see if this setting is causing the problems click on the Immunet System Tray icon to launch the GUI. Then click on the Settings tab on the right hand side of the GUI under Product. Monitor Network Connections is the last setting under the General Settings tab. Try turning that off to see if that corrects the issue. I think it's worth a try if this setting exists (see below).

 

Firstly: thank you!

 

I'm very-very sorry, but I didn't find any option you talked about it.

I can see only "Exclusions". This is the last option in general settings

http://postimg.org/image/yxz6feywd/

 

Would you like to post an image about your option, please?

May I did the mistake.

 

Special thanks: dd

Link to comment
Share on other sites

Hi dd,

 

Looking at this, can you send an SDT -either here, or to support@immunet.com?(If you haven't sent one for this? Lots of SDT in the forums recently)

 

Please add the forum topic/your name/'For Jose' or something to the subject line to identify it. (Thinking about creating a standard name for these...)

 

Got some people who will be looking into this for the next few days, see if we can figure it out.

 

-Jose

Link to comment
Share on other sites

  • 2 weeks later...

Hi dd,

 

Looking at this, can you send an SDT -either here, or to support@immunet.com?(If you haven't sent one for this? Lots of SDT in the forums recently)

 

Please add the forum topic/your name/'For Jose' or something to the subject line to identify it. (Thinking about creating a standard name for these...)

 

Got some people who will be looking into this for the next few days, see if we can figure it out.

 

-Jose

 

Dear Jose!

 

I sent the SDT. Did you have an idea about the problem?

 

Now I use online eset scanner, because I'm tired of uninstalling the program before the using of VPN, and installing it later...

 

Yours sincerely: dd

Link to comment
Share on other sites

Dear Jose!

 

Yes, you are right.

I have found them in wrong folder... :-(

 

I checked it, and the beta is good for us. :-)

 

Thank you for your great help! ;-)

You're a kind man!

 

Regards: dd

 

 

Hi dd,

 

I sent you a couple of emails back, maybe they went straight to a spam folder or something?

 

Let me know if you can see them (and if you want me to send you messages in the forums instead).

 

-Jose

Link to comment
Share on other sites

Hi!

 

Yes, it is working. Special thank for you!

 

I have only one problem: the big log file size.

Can I limit the file size somehow?

Because it's only 40GB sized virtual machine, and I need every GB on it to hold data.

 

Thanks: dd

 

Hi dd,

 

So that Immunet version worked for you OK if I understand correctly?

 

That's good to hear :D

 

-Jose

Link to comment
Share on other sites

Hi dd,

 

Unfortunately, the beta comes with debug logging enabled. Your options are:

 

a) Clean the log file periodically (instructions below)

B) Install the previous version and wait until next release.

 

The regular Immunet has error-logging only enabled, which is significantly smaller than debug logging.

 

Erasing the log file:

You can go into a command line window (with administrator privileges) and type 'net stop immunetprotect'

Go into the Immunet program files folder, find the log file, and simply erase it.

Re-enable Immunet by typing 'net start immunetprotect'

Link to comment
Share on other sites

  • 4 months later...

Sorry to report another issue with the Free/Community version and MS VPN Dial-Ins on XPSP3 (which btw I will be changing soon!)

 

Any tips on how to work around this problem?

 

My solution was: I installed the beta test, set this option there. Then I removed the beta, and I installed the Free version. Then it's working fine. :-)

Link to comment
Share on other sites

  • 3 weeks later...
  • 2 months later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...