Windows 10: Cannot ping LAN IP addresses over wifi but can do it over ethernet

Hi guys

I'm lost. My laptop (win10) is currently connected on wifi through my router to the internet. All working. However, I cant ping, see, connect to my nas or any other device inside my LAN.
Using other devices (iphone, imac, nas), they can all see eachother while using the same wifi.
My conclusion is that something is different from my laptop ethernet setup than it's wifi setup.

A few more notes:
- I'm using VM player to host a virtual machine. I wonder if that may have created some weird VPN between my host and guest OS that stops me from seeing the real LAN. But I dont know how to disable it. I dont have the VM running while I'm having this problem.
- When I go to windows explorer and click on network, it shows the NAME of my lan in the computer section. When I doubleclick on it it says that "Windows cannot access NASNAME"
- computer is part of workgroup but not home group. (I'm trying to PING here as step one, so I shouldnt need this)
- i tried with disabling firewall without success

I tried a few of the netcfg -d and a few netsh things to reset some stuff, but nothing seems to work.

Another few things that I see:
nbtstat -n shows my laptop twice with different numbers between <..>, and workgroup is shown 3 times with different numbers. then there's some smily faces with MSBROWSE. Again, I'm not sure that I even need netbios to get the ping to work.

In short: Where do I start troubleshooting if I can ping Google successfully but I cant ping any other device (except router) in my LAN?

:)

 

No Internet with Static IP address

Howdy,

On one of our Windows 10 systems, we lose internet if we assign the system a static IP address.

When this happens, that system can still browse our LAN, and other systems on the LAN can browse that system.

Oddly, that system with its new Static IP address, cannot ping the router (though obviously, it is connecting to other systems on our LAN
through the router.) The attempted pings just time out.

I'm baffled, and would pleased to get any help on this.

Many thanks,

 

suddenly cannot ping outside lan

After a restart, a Win10 laptop can still browse the web, and ftp, and other lan devices can ping this laptop, but in a cmd window ...

(i) pinging addresses outside the lan always times out

(ii) ipconfig /all shows ethernet and wifi "Media disconnected"

In a cmd window as administrator I tried ...

netsh winsock reset (required a restart, had no effect)

netsh int ip reset (Resetting Interface, OK!, Resetting , failed.)

ipconfig /release (No operation can be performed on Local Area Connection* 2 while it has its media disconnected.)

ipconfig /renew (ditto)

ipconfig /flushdns (no effect)

I need ping.

How do I fix this!?

(PS please fix your forum message editor's linefeed handling!)

 

I have a similar issue, on a fresh install. This worked fine when i upgraded windows 8.1 to 10 months ago but after a h/drive replacement 3 days ago and fresh install of wind10 the problem started.
FTP and ping work fine on on Ethernet but not on wifi.
I have reinstalled drivers and a load of other stuff and even tried a usb wifi adaptor (self installs) with the same result. I cannot ping my router Or any other local machines) but works fine for websites (like this forum) on wifi.

Have a look at this help topic, (i have tried them all and got nowhere)

Fix network connection issues - Windows Help

 

Hey man

Thanks for the pointers. Nice to see a page from MS where they give some tips. Mine is working now, I dont really know what solved it.

Here's my larger home network

ROUTER->NAS (ethernet)

ROUTER->LAPTOP (wifi). Not being able to connect to nas, or even ping it.

Then I tried from my bedroom wifi:

ROUTER->netgear switch->homeplug->....homeplug WIFI>laptop.
From this point my laptop CAN see the NAS (even though its further removed in the network). Then when I joined the ROUTER wifi again, it could continue to see the NAS .
Btw, my router wifi SSID is the same as my bedroom homeplug wifi AP. I wonder if win10 got confused.
Anyway it's working now.