DAT update from a VPN

[Ccharb]

Hello there,

Due to the situation in France, a lot of ppl are using teleworking.

A ticket is open on Mcafee Support :  4-20828384811 (with Mscript.log for more details)

Since they are connected to the VPN, client instead of pointing on the right super agent to dowload DAT update, they are checking every super agent until they find the good one. Each agent makes 3 request, with IP, name server, and FQDN server name.

Today, it takes 4 hour for a client to get the DAT update if they stay connected to the VPN.

Do you have a solution to reduce this time once they are connected to the VPN ?

Thanks your for help.

[Stefan80]

Hello!

Does the Routing of the VPN fit?

Is the client able to reach te repository?

Ist a Firewall active? I mean you need Port TCP 8081 to.

What kind of update tasks do you prepare for the Group.

[Ccharb]

Hey,

There is a firewall indeed, I dont have more detail because this is our Client infrastructure.

I asked to create a VLAN with VPN subnet with a super agent into it, but they cant.

I want to know if we can reduce the number of attemp from a client to reach a super agent.

In MSscript.log, a client ask 3 times the super agent with name/FQDN/IP.

Thanks for help.

[Stefan80]

Well the easiest way for VPN Clients is to create update tasks after startup and some fix times.

To reach the superagents, the routing in the VPN must of course work.