Windows 10: Windows 10 - Cannot access/ping private IP range (LAN)

Hi,


I have an issue which started only recently.

I can access the internet fine, able to connect to sites, ping google DNS etc.

What I cannot do is access any of my local devices in my LAN.


When attempting to connect to my router from my browser (I have tried all browsers) I get an error, Chrome error states "Your access is blocked, firewall or antivirus software may have blocked the connection".

When I attempt to ping the router I get General Failure error as per below.

ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.


I have many other devices in my LAN such as NAS, Citrix Xen server which is all not accessible only from this one machine, so this is not a router related issue (I have also attempted to reboot the router) and can confirm other devices like my phone can access my router.


I have tried a multitude of commands to reset my network adaptors and TCP/IP, flushing my DNS and restarting Winsock, but all to no avail.

I have also tried both WiFi and USB to ethernet adapter and have the same results, tried disabling my firewall also.

It appears there is some sort of corruption that is blacklisting any private IP range as I have tried devices in both the 192.168.x.x and 10.1.1.x subnet.


I am running Windows 10 Home on a Dell XPS 9550 and wondering if anybody else has this issue or has had this issue and what can be done to resolve. None of the automated network troubleshooting tools work for this issue and so far Google has provided me only the commands to reset TCP/IP and Winsock, which all have not worked.


Regards

Zol.

:)

 

Asus RT-AC88U problem with public ip starting with 10.xxx.xxx.xxx

10.x subnets are quite common. Everyone seems to think that 10.x or 172.x subnets or anything other than 192.168.x.x. = public IP when there's actually 3 private IP ranges in use on IPv4 protocol.

Most enterprises actually use the 10.x.x.x

I use all 3 for each VLAN to make it easy to tell which VLAN a device is on.

• 10.0.0.0/8 IP addresses: 10.0.0.0 -- 10.255.255.255.
• 172.16.0.0/12 IP addresses: 172.16.0.0 -- 172.31.255.255.
• 192.168.0.0/16 IP addresses: 192.168.0.0 – 192.168.255.255.

 

suddenly cannot ping outside lan

Hi Peter,

Did you make any changes to the computer prior to the issue?

I appreciate the efforts which you took to get the issue fixed.

Method 1: Update Network Adapter.

Follow the steps to update the Network Adapter drivers:

• Press Windows key + X key and click
  Device Manager.
• Expand the Network Adapter.
• Right-click on the Network Adapter and click on
  Properties.
• Go to Driver tab and select Update.
• Restart the computer and check.

Method 2: Reset TCP/IP.

Please follow the steps below:

1. On the Search bar type “cmd” and click
ctrl + shift + Enter to open the Elevated Command Prompt.

a. To Reset WINSOCK entries, type netsh winsock reset catalog and click Enter.

b. To Reset IPv4 TCP/IP stack, type netsh int ipv4 reset reset.log
and click Enter
c. To Reset IPv6 TCP/IP stack, type netsh int ipv6 reset reset.log
and click Enter.

Please revert if you face any issues with pinging address outside the LAN.

Thank you.

 

Assigning Static IP Address Range in a Router

yep, pretty much all.

for point #2 if you are having difficulty binding static IP in the router, it is ok to set static IP in the camera instead - just make sure you take a note on which IP is which camera so that you wouldnt put the wrong IP in the port forwarding.

am not sure what you meant. you don't need ddns to access the camera locally (from inside your LAN) *Confused