SOLVED Problem with Windows 10 + VDSL + dialup

[kiuhnm]

Hello,

I've just upgraded windows 7 to windows 10 (v. 10.0.10586).

I have a VDSL (FTTCab) modem/router which supports a feature called "automatic connection". Basically, when I activate that feature, I'm always connected to the internet.

When I was on windows 7, I disabled that feature and then I connected to the internet through a PPPOE dial up connection (rasdial). This way I could disconnect from the internet very easily and, more importantly, I got a new dynamic IP whenever I reconnected.

(I know I can disconnect with "ipconfig /release" now, but I can't change the IP because "net stop dhcp" doesn't work (with admin permissions).)

I tried to do the same on Windows 10, but it doesn't work. Oddly enough, I can ping by IP address but not by name. And yet DNSs are reachable because I can ping them.

Before connecting through dial up I get this:

C:\Users\Kiuhnm>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 192.168.1.1: Destination host unreachable.
Reply from 192.168.1.1: Destination host unreachable.
Reply from 192.168.1.1: Destination host unreachable.
Reply from 192.168.1.1: Destination host unreachable.

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

After connecting through dial up:

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=28ms TTL=44
Reply from 8.8.8.8: bytes=32 time=28ms TTL=44
Reply from 8.8.8.8: bytes=32 time=28ms TTL=44
Reply from 8.8.8.8: bytes=32 time=28ms TTL=44

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 28ms, Average = 28ms

But look at what happens when I try with names:

Pinging microsoft.com [198.18.1.22] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 198.18.1.22:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Kiuhnm>ping google.com

Pinging google.com [198.18.1.29] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 198.18.1.29:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

The IP addresses are completely wrong!

It's clear it's making IPs up because if I enter a random name such as "dfiojdfjhi", it resolves it as another address in the range 198.18.1.X.

Here's the output (edited) of ipconfig /all:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : [...]
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : [...]

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : [...]
   Description . . . . . . . . . . . : [...]
   Physical Address. . . . . . . . . : [...]
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : [...]
   IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : sabato 23 luglio 2016 02:31:32
   Lease Expires . . . . . . . . . . : sabato 23 luglio 2016 08:31:31
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : [...]
   DHCPv6 Client DUID. . . . . . . . : [...]
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

PPP adapter Broadband Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadband Connection
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : [...](Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . : 0.0.0.0
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                       8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Disabled

edit: I forgot to tell you that I have Avira and Comodo Firewall. I tried disabling them but not uninstalling them.
edit2: I uninstalled Comodo: didn't work.

 

[kiuhnm]

Solved. The problem is that the router itself is used as DNS server, but when the router is not "always connected" it doesn't work. The addresses 198.18.1.X are spoofed addressed returned when DNS resolution fails.

While in Win7 one needs to modify the DNSs of the PPP adapter, in Win10 (at least in my case) one needs to modify the DNSs of the Local Area Connection and this solves the problem.