View original (French)

Firewall alert: LAubervilliers

Solved
ak1sherkan Posted messages 20 Status Member -  
ak1sherkan Posted messages 20 Status Member -
Hello,
I come here to check your responses regarding a subject that is making me uncomfortable.
A provider for whom I have provided a VPN connection indicates that their personal firewall is signaling the following message:

incoming connection alert.
Remote point: LAubervilliers-151-12-103.w193.252.abo.wanadoo followed by the IP address of my network.
protocol 47.

What is this LAubervilliers...

Who should I ask for an explanation? It makes me a bit nervous!!!

Thank you in advance for your responses
Configuration: Windows XP Internet Explorer 7.0

3 answers

  1.
    arth Posted messages 84 Registration date   Status Contributor Last intervention   1 296
     
    Hello,

    This phrase appears when you perform an nslookup of an internet IP address: LAubervilliers-151-12-103.w193.252.abo.wanadoo

    So this means that if this is your address, you are connected to the telephone exchange in Aubervilliers.

    For example, I who live near the city of Clermont-Ferrand, if I do an nslookup of my address, it turns out AClermont-xxxxxxxxxx, which means that I am attached to the Clermont-Ferrand exchange.

    --

    The wolf, solitary and mysterious.
    1
    1. ak1sherkan Posted messages 20 Status Member 1
       
      Sure, and thank you for your intervention
      what you say reassures me.
      But I haven't launched an nslookup command on one hand and neither has the VPN user on the other hand.
      So by what miracle (...I'm exaggerating) is this alert triggered?
      I want to remind you that the client firewall sees this as a connection attempt, and therefore it triggers the alert.

      I do nothing, the user does nothing (besides using the VPN), so there's something I'm missing!!!
      And it makes me paranoid!!!
      Any idea on the origin of the triggering, Ladies and Gentlemen?

      Thank you for your intervention!!!

      Best regards
      0
  2. arth Posted messages 84 Registration date   Status Contributor Last intervention   1 296
     
    It is undoubtedly his firewall that automatically performed the nslookup.
    --

    The wolf, solitary and mysterious.
    0
  3. ak1sherkan Posted messages 20 Status Member 1
     
    Well, I imagine that's possible.
    So there's no reason to be alarmed. But I'm still going to look into it.
    And thank you
    Arth
    0