View Single Post
  #11  
Old November 1st 17, 02:07 AM posted to alt.comp.os.windows-10
harry newton
external usenet poster
 
Posts: 283
Default How do I unscrew up the routing table?

He who is harry newton said on Wed, 1 Nov 2017 01:03:35 +0000 (UTC):

This is a *great* command to see the *relationship* between the IP address
and the interface adapter!


In an "admin" shell, I ran:
netsh.exe int ip reset

Resetting Global, OK!
Resetting Interface, OK!
Resetting Unicast Address, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting Route, OK!
Resetting , failed.
Access is denied.

Resetting , OK!
Restart the computer to complete this action.

shutdown /r


When it rebooted, I ran the route print again:

route print
route print

================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 169.254.176.96 266
169.254.0.0 255.255.0.0 On-link 169.254.178.56 276
169.254.176.96 255.255.255.255 On-link 169.254.176.96 266
169.254.178.56 255.255.255.255 On-link 169.254.178.56 276
169.254.255.255 255.255.255.255 On-link 169.254.176.96 266
169.254.255.255 255.255.255.255 On-link 169.254.178.56 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 169.254.176.96 266
224.0.0.0 240.0.0.0 On-link 169.254.178.56 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 169.254.176.96 266
255.255.255.255 255.255.255.255 On-link 169.254.178.56 276
================================================== =========================
Persistent Routes:
None

netsh int ip show route


Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
No System 256 127.0.0.0/8 1 Loopback Pseudo-Interface 1
No System 256 127.0.0.1/32 1 Loopback Pseudo-Interface 1
No System 256 127.255.255.255/32 1 Loopback Pseudo-Interface 1
No System 256 169.254.0.0/16 8 VirtualBox Host-Only Network
No System 256 169.254.0.0/16 11 Local Area Connection
No System 256 169.254.176.96/32 8 VirtualBox Host-Only Network
No System 256 169.254.178.56/32 11 Local Area Connection
No System 256 169.254.255.255/32 8 VirtualBox Host-Only Network
No System 256 169.254.255.255/32 11 Local Area Connection
No System 256 224.0.0.0/4 1 Loopback Pseudo-Interface 1
No System 256 224.0.0.0/4 8 VirtualBox Host-Only Network
No System 256 224.0.0.0/4 10 Ethernet
No System 256 224.0.0.0/4 11 Local Area Connection
No System 256 255.255.255.255/32 1 Loopback Pseudo-Interface 1
No System 256 255.255.255.255/32 8 VirtualBox Host-Only Network
No System 256 255.255.255.255/32 10 Ethernet
No System 256 255.255.255.255/32 11 Local Area Connection

So I guess all *that* stuff is normal.

Of course, until and unless I set my desktop to the same 10.0.50.x subnet as my
"modem" (actgually it's a transceiver), I wasn't on the net.

But I guess this solves the problem of resetting the desktop back to normal.
Thanks.
Ads